Re: Internals read-only (was: Re: [PHP-DEV] namespace improvements to be committed very soon - final review)
| From: | Marco Tabini | Date: | Thu, 13 Dec 2007 13:55:25 +0000 |
| Subject: | Re: Internals read-only (was: Re: [PHP-DEV] namespace improvements to be committed very soon - final review) | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-33995@lists.php.net to get a copy of this message | ||
On 13-Dec-07, at 8:08 AM, Jani Taskinen wrote:
On Thu, 2007-12-13 at 10:00 +0100, Derick Rethans 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. Mt.To to get back to the point of the noise on the lists - it's getting out of hand, and I am afraid that if we don't solve this any time soon, the lists will be useless for any sort of decent discussion and promoting even more secret cults.There's already public list, it's called "php-general". So just unsubscribe all people from this list and subscribe all @php.net addies only.