Thanks to everyone for the input. I know some of these questions are obvious but I wanted to take it from the lowest possible level.
Part of the document is already posted to the wiki here. http://wiki.apache.org/nutch/Becoming_A_Nutch_Developer It seems like I am getting a section done each night so everything should be done it a couple of days. Dennis Kubes Chris Mattmann wrote: > Hi Dennis, > > > On 1/21/07 11:47 AM, "Dennis Kubes" <[EMAIL PROTECTED]> wrote: > >> All, >> >> I am working on a "How to Become a Nutch Developer" document for the >> wiki and I need some input. >> >> I need an overview of how the process for JIRA works? If I am a >> developer new to Nutch and just starting to look at the JIRA and I want >> to start working on some piece of functionality or to help with bug >> fixes where would I look. > > JIRA provides a lot of search facilities: it's actually kind of nice. The > starting point for browsing bugs and other types of issues is: > > http://issues.apache.org/jira/browse/NUTCH > > (in general, for all Apache projects that use JIRA, you'll find that their > issue tracking system boils down to: > > http://issues.apache.org/jira/browse/<APACHE_PROJ_JIRA_ID> > ) > > From there, you can access canned filters for open issues like: > Blocker > Critical > Major > Minor > Trivial > > For more detailed search capabilities, click on the "Find Issues" button at > the top breadcrumb bar. Search capabilities there include the ability to > look for issues by developer, status, issue type, and to combine such fields > using AND, and OR. Additionally, you can issue a free text query across all > issues by using the free text box there. > >> Would I just choose something that is unscheduled and begin working on it? > > That's a good starting point: additionally, high priority issues marked as > "Blockers", "Critical" and "Major" are always good because the sooner we > (the committers) get a patch for those, the sooner we'll be testing it for > inclusion into the sources. > >> What if I see something that I want to work on but it is scheduled to >> somebody else? > > Walk five paces opposite your opponent: turn, then sho...err, wait. Nah, you > don't have to do that. ;) Just speak up on the mailing list, and volunteer > your support. One of the people listed in the group "nutch-developers" in > JIRA (e.g., the committers) can reassign the issue to you so long as the > other gent it was assigned to doesn't mind... > >> Are items only scheduled to committers or can they be scheduled to >> developers as well? If they can be scheduled to regular developers how >> does someone get their name on the list to be scheduled items? > > Items can be scheduled to folks listed in the nutch-developers group within > JIRA. Most of these folks are the committers, however, not all of them are. > I'm not entirely sure how folks get into that group (maybe Doug?), however, > that's the real criteria for having a JIRA issue officially assigned to you. > However, that doesn't mean that you can't work on things in lieu of that. If > there's an issue that you'd like to contribute to, please, prepare a patch, > attach it to JIRA, and then speak up on the mailing list. Chances are, with > the recent busy schedules of the committers (including myself) besides Sami, > and Andrzej, the committers don't have time to prepare patches for the issue > assigned to them. If you contribute a great patch, the committer will pick > it up, test it, apply it, and you'll get the same effect as if the issue > were directly assigned to you. >> Should I submit a JIRA and/or notify the list before I start working on >> something? What is the common process for this? > > Yup, that's pretty much it. Voice your desire to work on a particular task > on the nutch-dev list. Many of the developers on that list have been around > for a while now, and they know what's been discussed, and implemented > before. >> When I submit a JIRA is there anything else I need to do either in the >> JIRA system or with the mailing lists, committers, etc? > > Nope: the nutch-dev list is automatically notified by all JIRA issue > submissions, and the committers (and rest of the folks) will pick up on this > and act accordingly. > >> Getting this information together in one place will go a long way toward >> helping others to start contributing more and more. Thanks for all your >> input. > > No probs, glad to be of service :-) > > Cheers, > Chris > >> Dennis Kubes > > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Nutch-developers mailing list Nutch-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nutch-developers
