Hi Marvin, > We have a wiki page up that covers the mechanics of contributing: > http://wiki.apache.org/lucy/HowToContribute
Excellent. I'll checkout the code and start reading on monday! > Most people choose what they want to work on based on what they need or what > interests them. Since you don't mention wanting to work on a particular > problem, there are a some general C tasks we could use help on and that don't > require a lot of prior knowledge about the code base; I'll describe one of > those. To be honest, I've no knowledge on how Lucene core is implemented. But I'm pretty confident when coding in C (portabilty, clarity, refactoring ...). More over I've strong background on algorithms and algorithms optimization. > A lot of Lucy code was originally written for C89. We have since changed our > C dialect to "the overlap of C99 and C++". > allowing us to use a number of idioms which result in cleaner, more readable > code. One of these is the > declaration of loop variables within a "for" construct: > > Index: core/Lucy/Object/VArray.c > =================================================================== > --- core/Lucy/Object/VArray.c (revision 956160) > +++ core/Lucy/Object/VArray.c (working copy) > @@ -55,8 +55,7 @@ > VA_dump(VArray *self) > { > VArray *dump = VA_new(self->size); > - uint32_t i, max; > - for (i = 0, max = self->size; i < max; i++) { > + for (uint32_t i = 0, max = self->size; i < max; i++) { > Obj *elem = VA_Fetch(self, i); > if (elem) { VA_Store(dump, i, Obj_Dump(elem)); } > } > > A good place to start would be that file, VArray.c. > Thanks for inquiring, OK, I see. Is it possible to ask questions about design choices of Lucy (how indexes are built, algorithms behind the scene...) in this mailing list as I'm missing this Information Retrieval skills? Regards ---------------------- voidptr...@gmail.com