PHP is a collective mind. Any dictatorship would mean a degradation for it.
If you don't like how it's managed, there is an easy path:
- Earn authority.
- Propose a change.
- Implement it.
- Maintain it.
Start with 1.
Why is earning authority a step in this process? This just seems like
yet another barrier to entry.
"You know enough C and you understand how to implement the feature,
but I've not seen your name around here so get stuffed."
That doesn't seem like a helpful attitude.
As for the comments about the FIG made by others, I agree with Larry
in that we're doing a pretty good job at trying to build on the
example set forward by internals. Self moderation and workflow are two
important factors to the group, and I don't feel like this 4 point
list is the sort of workflow anyone should be trying to follow or
enforce.
http://www.unicom.com/pw/faq/sco-xenix.faq
"blast from the past"...
Rajneesh N. Shetty
Tel : (+61)468371858
From: Philip Sturgeon [pjsturgeon@gmail.com]
Sent: Thursday, 12 September 2013 2:43 PM
To: internals@lists.php.net
Subject: Re: [PHP-DEV] Wake up
PHP is a collective mind. Any dictatorship would mean a degradation for it.
If you don't like how it's managed, there is an easy path:
- Earn authority.
- Propose a change.
- Implement it.
- Maintain it.
Start with 1.
Why is earning authority a step in this process? This just seems like
yet another barrier to entry.
"You know enough C and you understand how to implement the feature,
but I've not seen your name around here so get stuffed."
That doesn't seem like a helpful attitude.
As for the comments about the FIG made by others, I agree with Larry
in that we're doing a pretty good job at trying to build on the
example set forward by internals. Self moderation and workflow are two
important factors to the group, and I don't feel like this 4 point
list is the sort of workflow anyone should be trying to follow or
enforce.
As for the comments about the FIG made by others, I agree with Larry
in that we're doing a pretty good job at trying to build on the
example set forward by internals. Self moderation and workflow are two
important factors to the group, and I don't feel like this 4 point
list is the sort of workflow anyone should be trying to follow or
enforce.
I'm not sure I'm getting what you're trying to say here:
If it only is about the workflow in FIG, ok, maybe that should be looked
at and put out more descriptively on this list instead of people telling
to go read something somewhere.
If it is about what FIG does, then I disagree - because while I love
what FIG has been come up with (in terms of contents partly and of it
being done at all fully) - I think it has no place in internals and is
very well off as a seperate entity. Like I find a coding standard set by
the language developers kind of nuts. (Go pun not intended, because in
Go it has been there from the public beta version, not introduced like
15 years after inception. Same with Python, afaik it was a PEP that was
basically accepted by the community at large)
Greetings,
Florian