Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:34009
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain caedmon.net from 64.15.79.181 cause and error)
Cc: "Andrew Rose" <rose.andrew@gmail.com>,
 "internals Mailing List" <internals@lists.php.net>
Message-ID: <DD865154-7619-4583-95FA-F1EE10D6A677@caedmon.net>
To: "Daniel Brown" <parasane@gmail.com>
In-Reply-To: <ab5568160712130709sfd9a7eeof7de89875fa24960@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v915)
Date: Thu, 13 Dec 2007 10:19:18 -0500
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: sean@caedmon.net (Sean Coates)

>    2.) Probably a better idea, just click that DELETE button on any
> emails you don't feel like reading or responding to.  I find that, in
> a case study performed by myself just now, it takes me about a
> half-second to achieve success with this method.

Against my better judgement, I'm jumping into this thread...

The problem with simply deleting mail you don't want to see is the  
same as "just delete the spam you get"; it's one of signal-to-noise,  
and the delete button worked until you get to that magical threshold  
where it seems like all you're getting is junk and accidentally delete  
the good stuff.

Take this thread for example. I find it very interesting as there are  
many problems with PHP development as it currently stands (social  
problems), and I've been working on coming up with a solution for just- 
short of a year now (as many of the core members will attest, as I've  
had offline, face-to-face conversations with them about this).

However, because Jani's original post was buried in the middle of YET  
ANOTHER ridiculous debate on the "best" namespace operator, I actually  
had to go back to my trash and dig out the original mail after seeing  
Greg's reply and quoted text. I would never have seen it because I got  
trigger happy because almost all of this thread was absolute junk.

I don't yet have a solution, not would I try to force it upon anyone,  
but I do hope to propose one in the coming months. One that does  
involve making internals read-only for non @php.net holders, but also  
provides a clean and reasonable path for non-contributors to  
contribute, and somehow weeds out the gimme-gimme freeloaders (note:  
yes, there are non-@php.net holders that are not freeloaders).

S