Dennis Kubes 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. > > Would I just choose something that is unscheduled and begin working on > it?
Well ... so far this process was very informal, because there were so few key developers that they more or less knew what needs to be done, and who is doing what. Hadoop follows a much stricter and formalized model, which we could adopt, since it apparently works well there. This should address the issue of notifying others that the work is started on this or that item. Regarding the picking of the work to be done - natural ordering in JIRA should be followed, i.e. issues marked critical are more important than "major", and the ones with a lot of votes are more important than those without any. And of course even if something is not that important, but there's some kind soul who wants to work on it, we shouldn't discourage him. > > What if I see something that I want to work on but it is scheduled to > somebody else? You should always contact that person and coordinate the efforts. That's only polite and sensible. > > 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? I don't have any opinion on this, and I'm not sure how it works with JIRA - are only committers eligible for JIRA accounts? I'm fine with a non-committer developer working on patches, leaving just the final step to one of the committers. > > Should I submit a JIRA and/or notify the list before I start working > on something? What is the common process for this? See above for the process in Hadoop. Speaking for myself, when I start working on something bigger that is not tracked in JIRA yet I usually notify the list. If it's in JIRA I usually add a comment that I'm working on a patch. > > 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? I think that using proper tags in JIRA (which release, which subsystem, environment etc) goes a long way, and of course a patch helps a lot, too. :) > > 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. Thanks for taking this initiative! -- Best regards, Andrzej Bialecki <>< ___. ___ ___ ___ _ _ __________________________________ [__ || __|__/|__||\/| Information Retrieval, Semantic Web ___|||__|| \| || | Embedded Unix, System Integration http://www.sigram.com Contact: info at sigram dot com ------------------------------------------------------------------------- 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
