Agreed. I think apache is a preferable home. The major change to Luke in providing a Luke core api is the need to be remotable i.e. Use of an interface and serializable data objects used for args. Gwt rpc should take care of the marshalling and I've used similar frameworks for applet clients.
Like Andrzej I have limited time to work on this though. :( ---------------------------------------- On 12 Jul 2010, at 08:54, Andrzej Bialecki <[email protected]> wrote: > On 2010-07-12 09:14, John Wang wrote: >> share FE with luke is defn a good idea. >> >> any thoughts on putting webluke up on goog code or github? > > Guys, if you want to move forward with webluke, I think it's better to do > this under Lucene contrib. The reason is that if there's a substantial > development done outside Apache then it will need a code grant, and also it's > more difficult for other Lucene committers to participate in the outside > development and to bring its results back to ASF. > > I'm perfectly willing to donate all Luke's code to ASF, as I've said many > times in the past, if there's any chance of someone stepping in and removing > the Thinlet dependency. I'm also willing to work together as a Lucene > committer on an abstracted Luke core, if not on the GWT front-end (I don't > know GWT and I have too little time to learn it now). > > -- > Best regards, > Andrzej Bialecki <>< > ___. ___ ___ ___ _ _ __________________________________ > [__ || __|__/|__||\/| Information Retrieval, Semantic Web > ___|||__|| \| || | Embedded Unix, System Integration > http://www.sigram.com Contact: info at sigram dot com > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
