I like this approach since we can put the discussion of conceptual issues in jira, gathering comments on it, as we would on an email chain.. Once a decision is being reached in the jira issue, we can boil the points down to a wiki page. Then link back to the original conceptual jira tickets with the implementation jira tickets. We can also use the roadmap jira functionality to point conceptual components to future target releases.
One thing I would like to add is that while the volume of our email lists really makes performing these kinds of discussions very difficult, we are trained to check out email frequently...and without some automated reminder atrophy of the jira ticket might again happen. Perhaps we can wire up an email reminder system to the jira tickets that are under active review... jesse On 1/3/06, Jason van Zyl <[EMAIL PROTECTED]> wrote: > > Hi, > > Of late I think many issues are coming up on the lists and we're not > dealing with resolving them effectively because, as is natural, people > have different priorities or are generally just thinking about different > things that may be interesting or pressing. > > The three things of late I can think of is the development process > thread, the integration testing thread, and a discussion of best > practices which fell by the way side a month ago. So I intentionally > picked up Brett's start at codifying the dev process so that at least > two of us are on the same page and try and use that momentum to draw > other people into the discussion. I talked to a couple of subversion > developers (thanks to Garrett Rooney and Paul Querna), read Pragmatic > Version Control, talked to Jesse and Brett and found what useful links I > could find. I put it all together here: > > http://docs.codehaus.org/display/MAVEN/Development+Process > > After this I think we should deal with the integration test issues, and > then I'd like to work through the best practices listed in the wiki: > > > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=10500&sorter/order=DESC&sorter/field=priority&resolution=-1&component=11896 > > I'm not sure what would work best in terms of keeping the threads of > thought visible when they pass out of the current thread on the mailing > list but here's my idea based on notions in David Allen's "Getting > Things Done" which is a fairly practical way of working through a series > of issues. It basically boils down to collecting all issues that are > important, putting those notions somewhere safe and then prioritizing > them so they can be worked on. This is a little different where it's not > an individual but a group of people but we can use JIRA to collect the > issues and maybe the devs can vote to try and give some priority to the > list. > > Once the priority is set then as a group we work through the issues and > try to work through them one to three issues at a time and stick with > them until we have a resolution. What I would like is a way for anyone > interested to be able to pick up immediately and help. I'm all open to > ideas but I don't think we're dealing effectively with our own issues > because we have no locus to work because the email list is too hard to > keep track of for a lot of people. > > Maybe something other then JIRA would work but we need to collect, store > safely, prioritize the short list of issues and anyone who wants to see > where we are in resolving those issues should be able to see in a few > minutes where we are. I think it would be easy enough to setup a JIRA > project and try it. If it doesn't work then we'll look for something > else. I know this type of setup definitely helps me for issues tracked > at the Maven TLP level: > > http://jira.codehaus.org/browse/MPA > > Any thoughts? > > At any rate I think the short list now is: > > 1. Dev process > 2. Integration Testing > 3. Prioritize best practices and start picking them off > > Of course anyone is free to modify this list before a decision is made > on priority. Just trying to get the ball rolling, and hopefully keep it > rolling. > > -- > > jvz. > > Jason van Zyl > jason at maven.org > http://maven.apache.org > > Three people can keep a secret provided two of them are dead. > > -- Unknown > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- jesse mcconnell jesseDOTmcconnellATgmailDOTcom
