My thoughts: - I agree with Vincent that JIRA is no good for discussions.
- I agree with Jesse that the mailing list is still the most natural medium (people can discuss in their own time, catch up, and get automatic notification of new comments) - I agree with Jason that they are getting lost So, we should combine our technologies: - discussion starts on [EMAIL PROTECTED] - poster decides it requires further discussion (most likely the original poster, possibly at same time as posting). Adds the issue to JIRA, under MNG (or relevant project, eg CONTINUUM, or MPA if it is the dev process), component = design where necessary, target version where appropriate (eg a Maven 2.1 design discussion) - when discussion reaches a suitable point (may start this way), a proposal is put on the wiki - discussion is regularly used to update the wiki page. - if discussion goes in circles and no agreement is being reached because its hard to communicate given the time lag on email, a breakout on IRC is arranged, logged, summarised and posted to the list, with the wiki updated. Further discussion may ensue. The creation of a JIRA item and the relevant wiki page requires that an issue needs a champion. This should be the original poster, but others can agree to do that, and anyone can update the wiki or JIRA if they feel that is appropriate. The champion does not have to be a committer - anyone can propose and follow through on design discussions. - Brett Jason van Zyl 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. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
