+1 on this Gavin. Re. actual label names, how about a name followed by an (explanation) of the difficulty level:
Don't Know Newcomer (Easy) - Everyone can do this level Committer (Medium) - This is for regular contributors/committers. Where the vast majority of issues would fall. Expert (Hard) or Guru or ChrisMattmann or whatever everyone likes for "hard" - Used sparingly when an issue requires expert component knowledge We could default the field to "Don't Know" so every issue always has some level? I like the CouchDB approach but I feel they have too many options. Easy Easy - Medium Medium - Hard Really Really Hard (Their Guru level) So, when something is "Medium," which category does it fall into? I think the most important part of this system is identifying the difficulty for newcomers. The other levels are just nice to have in my opinion. That being said, I think simpler is better here. What do you guys think? -- Joyce On Sun, May 19, 2013 at 8:30 AM, Rajith Siriwardana < [email protected]> wrote: > +1 for having a label for issues that new users can help to resolve. > > > On Sun, May 19, 2013 at 8:51 PM, Mattmann, Chris A (398J) < > [email protected]> wrote: > > > Thanks Gav. +1 to using a controlled value field to make the labels > > meaningful. > > > > Let's see what others think but I am for sure +1. > > > > Cheers, > > Chris > > > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > Chris Mattmann, Ph.D. > > Senior Computer Scientist > > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > > Office: 171-266B, Mailstop: 171-246 > > Email: [email protected] > > WWW: http://sunset.usc.edu/~mattmann/ > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > Adjunct Assistant Professor, Computer Science Department > > University of Southern California, Los Angeles, CA 90089 USA > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > > > > > > > > > > > > > -----Original Message----- > > From: Gavin McDonald <[email protected]> > > Organization: 16 degrees complete web solutions > > Reply-To: "[email protected]" <[email protected]>, > > "[email protected]" <[email protected]> > > Date: Sunday, May 19, 2013 3:37 AM > > To: "[email protected]" <[email protected]> > > Subject: RE: JIRA label for new users > > > > > > > > > > >> -----Original Message----- > > >> From: Mattmann, Chris A (398J) [mailto:[email protected]] > > >> Sent: Friday, 17 May 2013 1:37 AM > > >> To: [email protected] > > >> Cc: [email protected] > > >> Subject: Re: JIRA label for new users > > >> > > >> Great idea, please implement on OODT too! (cc to dev@oodt for peeps) > :) > > > > > >We can start to use labels now for jira tickets, we just need an agreed > > >and > > >documented set > > >of labels. Why? Too many labels and we run the risk of there being too > > >many > > >and they sort of > > >Lose the impact and meaning. So a few well-chosen labels for attention > > >grabbing is needed. > > > > > >Every Jira ticket has a Labels section so this is available now. > > > > > >However, my main point of this mail, is that we can add custom fields to > > >our > > >issues. Some projects > > >have done such a thing, some, like the couchdb project, have > implemented a > > >drop down field in > > >their jiras so that anyone at a glance can determine if the ticket is > > >newcomer, contributor, committer, > > >hardcore project guru or Greg Stein level. (OK so I made that last > level > > >up, but really, the choice of drop down > > >field name is ours to decide) > > > > > >Pop on over to the couchdb jira and take a look. > > > > > >I am happy to implement this in the OODT Jira if you agree it a good > > >idea. > > > > > >I'm a big +1 ftr > > > > > >Gav... > > > > > >> > > >> Cheers, > > >> Chris > > >> > > >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > >> ++++++++ > > >> Chris Mattmann, Ph.D. > > >> Senior Computer Scientist > > >> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > > >> Office: 171-266B, Mailstop: 171-246 > > >> Email: [email protected] > > >> WWW: http://sunset.usc.edu/~mattmann/ > > >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > >> ++++++++ > > >> Adjunct Assistant Professor, Computer Science Department University of > > >> Southern California, Los Angeles, CA 90089 USA > > >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > >> ++++++++ > > >> > > >> > > >> > > >> > > >> > > >> > > >> -----Original Message----- > > >> From: Michael Joyce <[email protected]> > > >> Reply-To: "[email protected]" > > >> <[email protected]> > > >> Date: Wednesday, May 15, 2013 8:34 PM > > >> To: dev <[email protected]> > > >> Subject: JIRA label for new users > > >> > > >> >I sent this link around to a few people via twitter but I figured it > > >> >warranted being sent here as well! > > >> > > > >> >http://nikcodes.com/2013/05/10/new-contributor-jump-in/ > > >> > > > >> >TLDR: Every OSS project should have a label for issues that new users > > >> >could help resolve. Basically a "this is simple enough that a new > user > > >> >could figure it out and contribute back to the project" tag. > > >> > > > >> >This shouldn't be a tag for features/issues that the core team > doesn't > > >> >want to deal with. Mostly it should be for fairly simple auxiliary > > >> >issues that won't take forever to debug/implement but that the core > > >> >team doesn't necessarily have time to deal with. > > >> > > > >> >I think this is a great idea. When I first started on OODT this would > > >> >have been the coolest thing ever. I think it would be great to have a > > >> >section devoted to "getting started" on the website that mentions > this > > >>as > > >> well. > > >> >Then it would be really easy for new developers to jump in and help. > I > > >> >would be more than happy to help get this up and running as well. > > >> > > > >> >Thoughts? Terrible/great idea? Ideas for a label name? > > >> > > > >> >-- Joyce > > > > > > > > > > >
