Jason van Zyl wrote: > It's not supplanting the mailing list, it's providing a clear location > for the actions taken by the project.
I totally agree with the need to track stuff properly as I am generally the one chasing things up, my point was just ot give John a chance to finish what he's started. How do you see this working - create an issue before sending any ideas to the list? Seems like unnecessary overhead to me, but given we generally agree it probably isn't much different. I just think things take shape on the list first, then you file an issue when you've decided what you want to do. The person starting the thread follows it up. If nobody cares enough to do that, let it die. I have a system for dealing with mail, and I like using the mailing list. I'm sure I'm not alone. I skip over JIRA stuff much more quickly and its a whole lot slower to operate with while in the discussion phase. I do not want to use JIRA for discussion. As long as we're just tracking and its easy, I'm all for it. For the purposes you are talking about, like a/c creation, it sounds great. You might also look into the (STATUS) mails that other projects get from a certain file - maybe we can easily maintain a little list in SVN that can be used for these issues if it is more convenient. Just tossing out ideas - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
