Re: [recommenders-dev] Snipmatch GSOC was: How to start with Recommender

[Marcel Bruch <bruch@xxxxxxxxxxxxxxxxxx>]

Hi Cheng, Hi Doug,

regarding server-side backend:
We use Apache CouchDB as database and JAX-RS as RESTful server-interface for client communication. However, I just wonder whether using GIT repositories as backend would be sufficient or even better than CouchDB in our case. It can be synced easily between clients and server, support for many potential sources is straight-forward, and with JGit and EGit we have quite usable front-ends and APIs to work with. I'd just add the Lucene search index on top of the file system resources. Best of it (for the moment): we can start immediately w/o waiting too long for the server-side.

What do you think? Since it's merely a file-based approach with slim syncing capabilities we don't spent too much time on it if it proves not usable. But at least Github has proven that using GIT as snippet repositories works (at least they say GISTs are single git repositories).


Chen,
yes, please go for the proposal with the points you mentioned. Project mentor should be Doug, I'll be second mentor.

Doug,
you have to sign in as Mentor on the GSOC page and send Wayne an email that he confirms you are Eclipse Committer and eligible to be a Mentor for Eclipse GSOCs.

Regarding search-engine:
I'll be glad to write the search interface. We just need to agree on a snippet storage format. 
(my favorite for the moment is plain text with some mark-up)

Marcel

On 20.02.2012, at 04:03, chen cheng wrote:

> Hi Doug,
> 
> Yeah, In my initial idea, server side search engine and client side engine should be implemented the same, at least have similar search result.
> 
> Also, i am happy to work for the server side if i have enough time, but one question. I am not very sure about your solution, you mean we develop a brand new Java based server? Or we still use the current PHP server, but implement search algorithm in Java (May even use Lucence etc in the future), PHP code invoke Java search result ?
> 
> I guess you mean solution two, right ?
> 
> Here is my plan about improving SnipMatch client side:
> 
> 1. Implement all the design in my last post, create new Eclipse preference, local storage, improve GUI etc for SnipMatch. Leaving data interface for search engine (use a simple string compare algorithm at beginning, then improve the search engine in the future).
> 
> 2. Wait for the backend of Doug's job, implement search engine both for client side and server side. After i finished client side work, i can work with Doug together for the Java based search engine both for client side and server side. In fact, i am thinking there may be other search engines in Recommenders' other module such as Code Complete feature, is it possible for us to use some existing search engine ? Marcel, need your answer here :-)  
> 
> Doug & Marcel, is it OK about this plan ? If everything is prepared, i will write a detailed project proposal for this SnipMatch's merging and improving job, and start coding soon. And as a GSoC project, i need a project mentor, so i am just waiting for your favored here :-D  
> 
>