Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:34006
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.132.243 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:in-reply-to:mime-version:content-type:references;
        b=l/n5WhWQKSH8XhL/RN8GpGHs/EXwYnC88UgDi0aFxQl0FvyZFSdIQwGZv0g/d3xFo+JvpAyvleDbbG8/MWX4Cfa9mBu04WXvTs4yoR9r+UkcF2UjBSQh9sInzmdfjqaHXOrS0dLUwBkit+K+LBQPhh4uFqtO0+Yv+vg/QrPn4as=
Message-ID: <6ec19ec70712130717w79dcf1aei377066d5c8539fbe@mail.gmail.com>
Date: Thu, 13 Dec 2007 10:17:29 -0500
To: internals@lists.php.net
In-Reply-To: <ab5568160712130709sfd9a7eeof7de89875fa24960@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_29010_17144804.1197559049097"
References: <475F1984.603@chiaraquartet.net>
	 <1197450581.27917.2.camel@localhost.localdomain>
	 <4760227D.9050404@zend.com>
	 <alpine.DEB.0.98.0712130952470.27826@kossu.ez.no>
	 <1197551283.27917.9.camel@localhost.localdomain>
	 <47613538.1060308@wikimedia.org>
	 <1197553571.27917.12.camel@localhost.localdomain>
	 <47613EEE.5090305@richgray.com>
	 <f90bafdd0712130656me9f1daah928f064a54bcaa76@mail.gmail.com>
	 <ab5568160712130709sfd9a7eeof7de89875fa24960@mail.gmail.com>
Subject: Re: [PHP-DEV] Internals read-only
From: preinheimer@gmail.com ("Paul Reinheimer")

------=_Part_29010_17144804.1197559049097
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi

This is a subject I have discussed with several parties over the past year,
and I meet the fact that someone has finally suggested it publicly with
simultaneous relief and concern.


I see this move as having two primary effects, first to reduce the signal to
noise ratio on this list, which will hopefully improve the list for those
who use it to communicate on the future of the language, and those of use
who primarily read it to be kept in the loop (like myself). I think this
increase in efficacy would be good for those of you either working, or
volunteering your time to improve the language used by millions. The second
effect would be to make it harder for new people to join the team.
Regardless of the alternatives available (some discussion list rarely
touched by the core team, bug reports, blindly emailing people you've never
met before on the core team, etc) I think we can admit that this would
present an additional barrier to entry for people wishing to get involved in
the language.

I could be mistaken, but it looks to me as though the core team is
shrinking, both in head count and in hours spent coding. People move on to
new jobs, priorities change, etc. this is inevitable and I harbour no ill
will (in fact you all have my thanks for your time). Making the list read
only can help increase the efficiency of those still around, but how will
new blood enter the fold?

While I feel it is necessary to protect the time of the people improving the
language, I don't think this is a step you can take until a path for joining
this exclusive list is made clear, otherwise in a few years there might not
be a core team left.


Paul Reinheimer
(preinheimer@php.net)

------=_Part_29010_17144804.1197559049097--