Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:41612 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 48501 invoked from network); 1 Nov 2008 13:36:03 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Nov 2008 13:36:03 -0000 Authentication-Results: pb1.pair.com header.from=mike@rile.ca; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=mike@rile.ca; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain rile.ca from 216.221.81.25 cause and error) X-PHP-List-Original-Sender: mike@rile.ca X-Host-Fingerprint: 216.221.81.25 smtp.cogeco.net HP-UX 11.00-11.11 Received: from [216.221.81.25] ([216.221.81.25:58976] helo=fep1.cogeco.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 8F/41-40320-24B5C094 for ; Sat, 01 Nov 2008 08:36:03 -0500 Received: from mrobinson (d36-124-221.home1.cgocable.net [24.36.124.221]) by fep1.cogeco.net (Postfix) with ESMTP id 2B0281C3B; Sat, 1 Nov 2008 09:35:59 -0400 (EDT) To: "'Rasmus Lerdorf'" , "'Lukas Kahwe Smith'" Cc: "'PHP Development'" References: <2077BA98-A58A-4EBD-8088-413654E878BC@pooteeweet.org> <490B5CC5.8040808@lerdorf.com> In-Reply-To: <490B5CC5.8040808@lerdorf.com> Date: Sat, 1 Nov 2008 09:35:54 -0400 Message-ID: <000701c93c26$c4007d40$4c0177c0$@ca> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ack7jz7+Xkccab2XRbyexUgQcmQ7GQAknWFQ Content-Language: en-us Subject: RE: [PHP-DEV] keeping traffic on this list manageable From: mike@rile.ca ("Mike R") Rasmus Lerdorf wrote: > A simpler approach might be to just make the mailing list software > enforce a 1 email per 24-hour day per user. It would require a bit > more upfront work to munge the software, but wouldn't require any ongoing > effort. Moderation can get messy since it isn't simply spam we or > off-topic messages we are trying to control here, it is the volume, > quality and timeliness of on-topic messages. I'm not sure moderation > is the answer to that. We need a behavioural change here. IMHO,I don't think this approach would work, but moderation isn't the answer. PHP has far too vibrant a community to fall victim to this type of alienation. In the dozen+ years I've been subscribed I've never found the list so unmanageable as to warrant moderation of any kind. My eyeballs and the delete key are still pretty good BS filters. 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. Mike Robinson