There is a lot of code in /contrib which needs proper documentation, refactoring and clean-up. For refactoring you can have a quick look at /analyzers/smartcn. Clean-up and documentation is needed in /contrib/spartial which still suffers from lots of legacy comments and certainly legacy code. I guess somebody else mentioned it already - test-cases are always appreciated. I haven't looked at spartial for a couple of weeks but i haven't seen a lot of test cases so far.
Maybe the contribs are a good place to start from. simon On Thu, Aug 13, 2009 at 9:09 AM, Amin Mohammed-Coleman<ami...@gmail.com> wrote: > Thanks for your replies. I have checked out trunk and have started looking > at what I can do. Any more suggestions as usual always welcome. > > Thanks all! > > Amin > > On Wed, Aug 12, 2009 at 10:28 PM, Chris Hostetter > <hossman_luc...@fucit.org>wrote: > >> >> : that you use. Also, we are nearing 2.9 release, so it would >> : be great to have as many eyeballs as possible on that. There is a lot of >> new >> : goodness coming in 2.9, so it will be particularly important to get good >> : feedback, as this will help set the stage >> >> ...even for people that might be really unfamiliar with the Lucene >> internals, skimming the CHANGES.txt and then looking at the corrisponding >> javadocs to find any missing/confusing javadocs would be really helpful. >> >> And of course: we can always use more test cases. >> >> >> >> -Hoss >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org >> For additional commands, e-mail: java-user-h...@lucene.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
