Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41599
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lerdorf.com from 204.11.219.139 cause and error)
Message-ID: <490B639A.8050905@lerdorf.com>
Date: Fri, 31 Oct 2008 12:59:22 -0700
User-Agent: Thunderbird/3.0a2pre (Macintosh; 2008071516)
MIME-Version: 1.0
To: Hannes Magnusson <hannes.magnusson@gmail.com>
CC: Lukas Kahwe Smith <mls@pooteeweet.org>,
        PHP Development <internals@lists.php.net>
References: <2077BA98-A58A-4EBD-8088-413654E878BC@pooteeweet.org>	 <490B5CC5.8040808@lerdorf.com> <7f3ed2c30810311252x7c4f1cb9ydd41a273f4089311@mail.gmail.com>
In-Reply-To: <7f3ed2c30810311252x7c4f1cb9ydd41a273f4089311@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] keeping traffic on this list manageable
From: rasmus@lerdorf.com (Rasmus Lerdorf)

Hannes Magnusson wrote:
> Behavioural change is desperately needed, and I think developers
> should lead by example.
> One way to to that is to add a new internal-core@ mailinglist which is
> read-only to the world, and writeable by people with appropriate
> karma.
>
> That list would be dedicated for _development_ discussion (including
> implementation, patches, "edge-case voting" and such things) and would
> include posts like are going on between greg, stas and dmitry, and
> posts which are going on between release managers and individual
> developers. This way we keep _everything_ in the open and maintain a
> "high quality" on-topic discussions.
>
> "external" patches and "general" discussions would still be on the
> internals@ list, as it would be the main discussion list. However,
> those who simply do not have the time to read over the entire thing
> have a specific low-traffic list which they can easily follow.

This is the same as just making internals@ read-only.  Once we have an 
internals-core, many core people will just unsubscribe from the 
internals list.  I know I probably would.  And once the core developers 
no longer read it, it becomes php-general2 and it ends up excluding 
people from the development process.

-Rasmus