> -----Original Message----- > From: Jason van Zyl [mailto:[EMAIL PROTECTED] > Sent: mardi 3 janvier 2006 21:34 > To: Maven Developers List > Subject: Re: working on and prioritizing dev issues > > Jesse McConnell wrote: > > > Oh, I was thinking that the crux of this email was trying to determine > was > > 'Where should these things be discussed?' Email is the classic > traditional > > place to do it, but discussions have been getting dropped on here and > Jira > > was a proposed solution. Perhaps someone just needs to keep bumping > these > > discussion topics up :) > > The discussion of what to resolve will happen on the list or in irc but > then get populated in JIRA so that what's up for discussion gets > captured. JIRA can ping the list with unresolved issues and as we are > discussing the issues I think someone needs to act as secretary and > capture the salient ideas in the wiki. So for the dev process stuff I > created a document and steward that document to completion. I think the > same would go with the integration tests where this is something that > Vincent is keen to resolve so he can be the secretary for that issue (if > that's ok Vincent).
I'm ok in principle. It's just a question of time and spending enough time to follow it up fast enough so that the momentum is not lost. >So I think the flow becomes > > - everyone pushes issues they want resolved into JIRA > - we prioritize a short list to work on in a particular week (or > whatever), we can use votes or just decide amongst ourselves > > with that short list we: > > - pick the issue at hand > - burst of discussion on the list > - secretary captures the salient points > - offers up the document for review > - go back to discussion/capture/review until complete > - a final document then accompanies the resolution and the issue is closed +1 [snip] -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
