> -----Original Message----- > From: Jesse McConnell [mailto:[EMAIL PROTECTED] > Sent: mardi 3 janvier 2006 21:04 > To: Maven Developers List > Subject: Re: working on and prioritizing dev issues > > > > > > > > > > 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. > > > > I do agree with all this but I think we still need the list to discuss > > things. JIRA is not good for discussions. Once we agree about a > > strategy/Stuff to do then jira is the best place, I agree. > > > 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 :)
But all the things that we need to work on are mostly on JIRA already. We simply need to decide on priorities, right? I agree that user votes is a good way. We could ask for users to vote on issues, wait for 2-3 days and take the first 10 issues that come up. Once this is finished do it again? -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
