On Thu, 13 Dec 2007, Gregory Beaver wrote:
We don't need moderation, we don't need read-only. We need people to
follow a simple common-sense checklist.
It's either that nobody saw this mail, or chose to ignore it. Obviously,
nothing changed and I'm getting sick and tired of all this crap on
On 10-Jan-08, at 10:33 AM, Derick Rethans wrote:
On Thu, 13 Dec 2007, Gregory Beaver wrote:
We don't need moderation, we don't need read-only. We need people to
follow a simple common-sense checklist.
It's either that nobody saw this mail, or chose to ignore it.
Obviously,
nothing
On 10.01.2008 18:33, Derick Rethans wrote:
On Thu, 13 Dec 2007, Gregory Beaver wrote:
We don't need moderation, we don't need read-only. We need people to
follow a simple common-sense checklist.
It's either that nobody saw this mail, or chose to ignore it. Obviously,
nothing changed and
On 10-Jan-08, at 10:58 AM, Lukas Kahwe Smith wrote:
I know that PHP has so far stayed clear of processes and I am fine
with keeping it this way. But I really think that some of these
flames should best be taken off list into some work group that
provides summaries at semi regular
On Jan 10, 2008, at 4:51 PM, Ilia Alshanetsky wrote:
On 10-Jan-08, at 10:33 AM, Derick Rethans wrote:
On Thu, 13 Dec 2007, Gregory Beaver wrote:
We don't need moderation, we don't need read-only. We need people
to
follow a simple common-sense checklist.
It's either that nobody saw
On Jan 10, 2008, at 4:55 PM, Antony Dovgal wrote:
On 10.01.2008 18:33, Derick Rethans wrote:
On Thu, 13 Dec 2007, Gregory Beaver wrote:
We don't need moderation, we don't need read-only. We need people
to
follow a simple common-sense checklist.
It's either that nobody saw this mail, or
Marco Tabini wrote:
On 10-Jan-08, at 10:58 AM, Lukas Kahwe Smith wrote:
I know that PHP has so far stayed clear of processes and I am fine
with keeping it this way. But I really think that some of these flames
should best be taken off list into some work group that provides
summaries at
On Thu, Jan 10, 2008 at 04:14:46PM -0600, Gregory Beaver wrote:
At the very least, some kind of centralized RFC tracker (like PEAR's
PEPr for package proposals) would be a potential way to track features
that would introduce slightly more work (another thing to maintain at
php.net for web
At the very least, some kind of centralized RFC tracker (like PEAR's
PEPr for package proposals) would be a potential way to track features
Maybe just for the start create a wiki or something that people could
put their RFCs to and edit them, and then hopefully somebody would step
up to
Hi,
We don't need moderation, we don't need read-only. We need people to
follow a simple common-sense checklist. Before sending a message to
php-internals, ask these questions of yourself:
1) am I angry? yes = do not send your message, do not pass go, do not
collect $200. Wait until tomorrow.
10 matches
Mail list logo
