Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41601
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.146.179 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=Dx8OpvPovY7q1X1VTok+gaH+oH8CeBuSGh4wCqo1o0k7OzeRWOMxVM0LhwzQ0KFb+3
         ZE0iT84ozBc8BXkJk1YSjhGfqKV6vjRy8VHlWm0ZkZCqMIjzD+f3z5CiJlvLXvG22DUQ
         CEXPQesZni2LPej9eMnOZ1lNRyi3CYNUzQPXA=
Message-ID: <7f3ed2c30810311313i48390eaat279d88fe291b9f16@mail.gmail.com>
Date: Fri, 31 Oct 2008 21:13:07 +0100
To: "Rasmus Lerdorf" <rasmus@lerdorf.com>
Cc: "Lukas Kahwe Smith" <mls@pooteeweet.org>, 
	"PHP Development" <internals@lists.php.net>
In-Reply-To: <490B639A.8050905@lerdorf.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <2077BA98-A58A-4EBD-8088-413654E878BC@pooteeweet.org>
	 <490B5CC5.8040808@lerdorf.com>
	 <7f3ed2c30810311252x7c4f1cb9ydd41a273f4089311@mail.gmail.com>
	 <490B639A.8050905@lerdorf.com>
Subject: Re: [PHP-DEV] keeping traffic on this list manageable
From: hannes.magnusson@gmail.com ("Hannes Magnusson")

On Fri, Oct 31, 2008 at 20:59, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:
> 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.

I have more faith in our devs then that. And I doubt you would
unsubscribe, you care to much (and one of the few devs I've seen to
reply to posts on php-general@ and then pear-dev@ the next day..).
Most of us do. You would probably filter those posts into a different
reading priority, but you would still browse through it.

I expect bunch of silent listeners to unsubscribe from internals@ and
subscribe to internals-core@ and I can even see some devs only
subscribed to internals-core@ but I have no doubt that over 51% would
stay stay subscribed to internals@ and would forward interesting
discussions to internals-core@.

-Hannes