Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [recommenders-dev] Code Recommenders joins the annual release train

Thanks Marcel,

Yes, I'll use your technology stack for the new backend. I plan to
finish it by the end of January (on internship until ~Jan. 6th, so
time is tight until then).

Client-side, I think local snippet caching is the only major, critical
change that needs to be made for Juno.

Awesome to be on the release train :)

Doug




On Thu, Dec 1, 2011 at 9:54 PM, Marcel Bruch <bruch@xxxxxxxxxxxxxxxxxx> wrote:
> Hi Doug,
>
> On 01.12.2011, at 20:40, Doug Wightman wrote:
>
>> I'd love to participate.
>
> Awesome!
>
>> I will rebuidt the backend of SnipMatch for
>> this.
>
> Great. The common backend infrastructure we use for code search, stacktrace search, call models, and extdoc is Apache CouchDB + Apache Lucene + JAX-RS. It would be great if you could use these technologies. Then we can keep a common technology stack for all projects and support development or help fixing issues that arise.
>
>> Zi won't have time to lead the client development for SnipMatch
>
> Zi, from your point of view: does it make sense to start a committer election? Do you have time to participate as committer (entirely honest) - or is a contributor status better suited? With Git the latter should feel almost the same - except that a committer (e.g. Doug) has to integrate your contributions then. Please let me know. You did a good job on Snipmatch so far. I'm open for any status.
>
>> - is someone else willing to help out on that front?
>
> Regarding support for Snipmatch UI. Juno release will be in June. Starting from December there is one (and a half) student at TU Darmstadt working on a snippet editor based on Xtext to improve the "create/edit snippet dialog". Devarun will work on mining code snippets which (hopefully) get integrated into Snipmatch.
>
> What plans do you have? Where is improvement needed? We can add "help wanted" tasks to bugzilla and promote it as soon as the first version of Snipmatch is out. If there is a clear vision what needs to be changed and how, I'm confident that we and others can contribute.
>
> As a side note:
> I guess excellent documentation of the current design + feature wish list + good webpage is key for that kind of help. The guys around Mylyn are pretty good here. We are in the move to document our designs for extdoc and other tools to facilitate that kind of contributions (you may have noticed the docbook announcement mail a few days ago). Maybe this would be a good thing for Snipmatch too?
>
> Best,
> Marcel
>
> _______________________________________________
> recommenders-dev mailing list
> recommenders-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/recommenders-dev


Back to the top