Wow, seems like there is a lot of push back on this topic. All I ask Please respect that Jason and I (as well as the WebWork community) come from a very well-established open source community and have a lot of alternative experience in this area. We both have different perspectives, but this merger is more than dumping code in the Struts codebase. It is working with the teams too.
To Ted's specific points: * I am very well aware the emails are a direct result of a peron's action. To my original point: I don't care. I personally review the wiki and bug tracker at a different time than when I check email. * Jive Forums certainly can filter the email, and I may turn that on, but then I've bypassed the team rather than working with them. I don't like that approach at all. To Sean's points: * I am not proposing that we get rid of email lists. I am only suggesting that there be ways to opt out of certain lists/types of mail. Why is offering more options such a problem? I fail to see how everything being list-based leads to the conclusion that "The result is a single archive that is publicly searchable and contains all relevant decisions (no matter how trivial) in one place." Why can't there be multiple archives that can all be searched at once? We provide that with WebWork by allowing users to search the WebWork _category_, which includes the Dev, User, and CVS lists. To James: * I fully support that you work that way and am not suggesting your workflow change at all. I 100% support complete email-based communication. I only ask that some users such as myself be able to opt out. So, I'd like to propose something. Ted said: > 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. I offer two suggestions, either is perfectly fine with me. Any other suggestions that provide more alternatives are also of course welcome: 1) Why not create a simple web-based form to manage all the lists. By default, all 5, 6, or 7 lists are checked when the user clicks the "subscribe" button, but each list can be independently subscribed and unsubscribed. You can even set the Reply-To header for some of the lists (bugs, wiki, etc) to point back to the dev@ list. and/or 2) Using a Forums-based approach and different mailing lists for each type of content (wiki@, dev@, bug@, etc), create a single Struts category with several sub-forms that sync to the lists. Now users can search the Struts category and get a unified archive. Thoughts? I understand that this does involve some work, and for those of you who are quite happy with how things are now, it may seem like a waste of time. As such, I'm more than willing to do the actual work for any proposed solution. Patrick --------------------------------------------------------------------- Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=14616&messageID=29027#29027 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
