On 1/17/06, Patrick Lightbody <[EMAIL PROTECTED]> wrote: > I definitely understand where you are coming from, and I hope you can see > where I'm > coming from. Often when people have different work behaviors, the best bet is > to provide > more options. This can be done by somehow allowing individuals to opt out of > those > generated emails. I hope we can do something about this.
I think an important point is that these emails are being generated by people. People are making the wiki changes, and people are creating the issue tickets, and people are making the subversion commits. Each and every one of those emails contains original input from a real person that deserves the attention of the dev list. The issue trackers posts are marked "DO NOT REPLY", because we want to keep the discussion under the comments for each issue. So, to reply, you follow the link to the ticket. But, by posting the status changes to the ticket, we are all being kept abreast of what is happening on a ticket, whether we click thru or not. We don't have to schedule time to review the issue tracker, the issue tracker comes to us in real time. Case in point: Right now, Roller is being incubated, and we don't have JIRA posting to the dev list yet. I created and posted a ticket over the weekend. But, no one noticed until I made a second post to dev@ mentioning the ticket. Volunteers should not have to make a redundant post to the mailing list when JIRA can do it automatically. For a number of reasons, including legal ones, we do want all the input and discussions, whether they take place on the wiki or the issue tracker or anywhere else, to end up on a mailbox on an ASF server. Now, we could create a wiki@ mailing list and an issue@ mailing list, to match the commit@ list, but now when people opt-in, they have to opt into five lists instead of three. If we add a Roller blog to the mix, then there would be six. Right now, the ASF norm is three lists: That's what we create when projects come through the Incubator.If we want more than that (and I'm not sure that we do), I'd be happy to bring it up on the internal ASF members list, to get input from other ASF communities. Perhaps someone else here has already discussed having more lists at length, or even tried more lists. IMHO, it sounds like Jive is not up to the task of managing an ASF-style dev list. Any decent mailreader can filter mails into whatever folders we find convenient, creating the personal equivalent of five or six separate lists, if that's what someone wants. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
