Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41615
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 88.198.8.16 cause and error)
Cc: "'Rasmus Lerdorf'" <rasmus@lerdorf.com>,
 "'PHP Development'" <internals@lists.php.net>
Message-ID: <CF667C38-A98A-48CD-8D3B-21C9BBA480C8@pooteeweet.org>
To: "Mike R" <mike@rile.ca>
In-Reply-To: <000701c93c26$c4007d40$4c0177c0$@ca>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Sat, 1 Nov 2008 18:20:26 +0100
References: <2077BA98-A58A-4EBD-8088-413654E878BC@pooteeweet.org> <490B5CC5.8040808@lerdorf.com> <000701c93c26$c4007d40$4c0177c0$@ca>
Subject: Re: [PHP-DEV] keeping traffic on this list manageable
From: mls@pooteeweet.org (Lukas Kahwe Smith)


On 01.11.2008, at 14:35, Mike R wrote:

> Behavioral change is exactly what is needed. The simplest way to  
> achieve
> that is education and buy-in. A good start would be to document the  
> desired
> behavior, in an isolated php-dev subscription page, in the form of a  
> _brief_
> terms of use, and have new subscribers acknowledge and agree to it.  
> There
> could also be a cooling off period, where new subscribers are read- 
> only for
> the first NN days - that'll let tempers and hair-triggers cool off.  
> The
> core team is populated by some of the smartest people on the planet,  
> I'm
> sure some other ideas can be bandied about and implemented to  
> achieve the
> desired goal without resorting to moderation.


We do have something along those lines:
http://www.php.net/reST/php-src/README.MAILINGLIST_RULES

Maybe it needs to be cut down (or just provide the key points at the  
top) and automatically appended to all emails (including the welcome  
email) ..

regards,
Lukas Kahwe Smith
mls@pooteeweet.org