FWIW, I find one of the best ways to start contributing is by writing unit tests. From the looks of https://analysis.apache.org/dashboard/index/63921, you can see we have pretty poor coverage. It's a great way to learn the code and it is a huge help for the project.
On Oct 25, 2011, at 11:58 PM, web service wrote: > +1. > > On Mon, Oct 24, 2011 at 7:02 PM, Raphael Cendrillon < > [email protected]> wrote: > >> Hi Isabel, >> >> As someone keen to contribute, but still quite new to Mahout, I think this >> is a great idea. >> >> On Oct 24, 2011, at 6:39 PM, Isabel Drost <[email protected]> wrote: >> >>> On 24.10.2011 Grant Ingersoll wrote: >>>> Docs is one obvious one. Also, just keep supplying patches. >>> >>> Speaking of supplying patches: Doing so seems non-trivial for quite some >>> developers. >>> >>> During the Apache Hadoop Hackathon Berlin earlier this year Jakob Homan >> did a >>> very interesting exercise: The Hadoop project seems to have bug reports >> that are >>> trivial to fix (trivial as in typos in documentation, enhanced error >> messages >>> etc.). Jakob used those to introduce developers to the whole patch >> generation >>> and submission process during the Hackathon. >>> >>> Dan (and users of Mahout, in particular those who have not yet submitted >> any >>> patch) - do you think that having some of those bugs around (w/o a >> version >>> number assigned, maybe tagged as "trivial") help you get started with >> being >>> active contributors? How about marking issues the community feels >> manageable for >>> newcomers as "mentor" as proposed in the Getting Started guide of >> community.a.o >>> project: http://community.apache.org/gettingStarted/101.html ? >>> >>> >>> Isabel >>> >> -------------------------------------------- Grant Ingersoll http://www.lucidimagination.com
