Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:33996
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain sci.fi from 63.208.196.178 cause and error)
Reply-To: jani.taskinen@iki.fi
To: Marco Tabini <marcot@tabini.ca>
Cc: internals Mailing List <internals@lists.php.net>
In-Reply-To: <E8CF2E5C-C68E-4E7A-A7FA-0BDACE602721@tabini.ca>
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>
	 <E8CF2E5C-C68E-4E7A-A7FA-0BDACE602721@tabini.ca>
Content-Type: text/plain
Date: Thu, 13 Dec 2007 15:58:37 +0200
Message-ID: <1197554317.27917.15.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Internals read-only (was: Re: [PHP-DEV] namespace
	improvements to be committed very soon - final review)
From: jani.taskinen@sci.fi (Jani Taskinen)

On Thu, 2007-12-13 at 08:55 -0500, Marco Tabini wrote:
> I am just a lurker, so take this with the due grain of salt, but  
> simply making internals@ read-only is just going to drive people to  
> contact the core team members directly (thus likely *increasing* your  
> blood pressure :-)). I think you need to provide people with some way  
> of interacting without unleashing chaos on the development process;  
> php-general, IMHO, is not the place for that kind of discussion,  
> because people there are mostly looking for assistance with the use of  
> PHP, rather than attempting to influence the development process.

IMNSHO contacting core members directly is the only way to really make
them interested AND to actually notice the idea. At least with the list
being what it's like right now. :)

--Jani