Aside from renaming the php-dev list, we should remove the 'PHP and Zend
[snip]
Sounds good.
Then another item that might be considered if it is not already done, allowing posts only from those that have cvs access. A second conditional list of allowed posters can be added that are people who do not have cvs access, but we want to allow to post. Otherwise, the list can be readable by all. A post rejected message could tell them to try a different email list, but if they really feel the email is for the dev list, send it to [EMAIL PROTECTED] and
This however sounds too restrictive to me. I'm convinced that the main php development list should stay as open as possible. The issue of a few misdirected emails should not serve as an excuse for closing down the main development list. We should not become an ivory tower.
it will be reviewed by someone when they get the time.
This manual review effectively implies censorship which is undesirable in an open environment. I doubt it would serve the PHP community in any way.
- Sascha
Well, it is just an idea, but my desire is not to implement censorship or to make the list closed, but rather to 'protect the purpose and use' of the list. I rather think that the first item I sent is the only one that is realy needed, and that it would solve 90% of any existing problems.
But for the sake of writing...here's another idea.
So how about a first post response system, similar to the subscription response. That first post would not actually be posted to the email list, but rather an email would be sent back to the poster stating the purpose of the email list, and what kind of materials are expected on the list. If the post does not match this criteria, please send it to on of the other lists, otherwise respond to this email and your original message will go out.
Shane
-- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
