Re: Is there a discussion-only list

On Sat, Jan 8, 2011 at 18:40, Daniel Brown <danbrown@php.net> wrote: > On Sat, Jan 8, 2011 at 12:25, Paul Dragoonis <dragoonis@php.net> wrote: >> >> wiki accounts, karma requests, svn commits are really only directed at >> people who are involved in the development of php stuff. >> for the rest its general discussion we could have php-webmaster to >> continue with the discussions and take the system messages off to a >> new mailing list such as php-notifications or something like that. >> >> The percentage of people interested in the commits.etc is going to be >> much less than the people interested in discussions so only a small >> amount of people involved in development would need to signup for the >> new list. >> >> Usually what happens is when you see a commit, you reply to it and >> start a conversation about it. I think if you want to start a >> discussion about a commit but if that turns into a debate with more >> than 2 people it should move to php-webmaster to get more peoples >> opinions on it. >> >> Just my thoughts on the above points raised. > >    I agree with separating the discussions and system messages, but > want to see it done differently than suggested so far.  Historically, > we've always used the webmaster@ and php-webmaster@ addresses (and the > correlating list) for system messages (CVS/SVN commits, site bug > reports, event and calendar submissions, et cetera), as well as a > first point of contact for anything related to the php.net website. > I'd not only like to see it stay that way, but also revert the change > for events, so that they'll be emailed in real-time like they always > had been (but that's not entirely relevant to this discussion). > >    In order to really keep this separate, what about the creation of > a list specifically related to the tasks at hand, such as ui@ or > site-ui@?  There are a variety of pragmatic options, I just don't > believe that shifting things entirely and rededicating this list is > one of them.  That, and, it's a hell of a lot less work to move new > discussions to a new list and just have everyone subscribe there. I really do not see the need for a specific discussion list which will after January/February get one, maybe 2, emails a year. I recommend that these <10 new subscribers create filters to deal with mails they don't care about :) An specific commit list for /repository/web/* (minus peclweb) would however make sense imo. And if the 'system messages' are supposed to be kicked off too.. I ph33r we get into the same situation as with the manual notes; ignored. -Hannes