Re: PHP Standards and Best Practices for PHP 5.3+ Frameworks and Libraries

From: Date: Mon, 01 Jun 2009 16:43:40 +0000
Subject: Re: PHP Standards and Best Practices for PHP 5.3+ Frameworks and Libraries
Groups: php.standards 
Request: Send a blank email to standards-+get-24@lists.php.net to get a copy of this message
Call me an anonymous developer, whatever, but I think it's completely ridiculous that a seemingly arbitrary group of people are going to hand down standards from their ivory tower atop their cathedral. Whether you like it or not (and based on the attitude going around in this thread, I'm guessing you don't), the decisions made by this "standards" group are going to be up to peer review and adoptance. Regardless of the quality of the standards proposed in this mailing list, the fact that you're excluding the community at large and our input is reason enough for me to reject your standards and not adopt them. I understand that the PHP internal mailing list is slow in development and things get argued back and forth forever and ever, but is the language any worse for this, or is it better? I'm much inclined to think the latter, as is every other bazaar developed standard, project, language, what-have-you. Closing standards discussion off to the public and randomly telling me, as a PHP developer who seeks to not only contribute back to the community but also to follow where the community leads, that I have to follow a set of standards (that are partially inane and unbelievably restrictive in their naming conventions, but that's another email) because Ye Of The Popular Frameworks Hath Spoken is a total load of bullshit. I don't give two shits if you're Jesus Christ himself, if you're going to propose a set of standards that tens of thousands - if not more - of developers will theoretically be following, you best be goddamn sure that they hold up under scrutiny and peer review. And just because six people voted does not make a standard final; the only thing that's going to make your best practices standardized best practices is if they're adopted. If you want this list to succeed, come down of the high horse and listen to what the community has to say. If this list goes moderated, I, for one, will make it a point not to follow your ridiculous standards and thus will end the contributions I will make to the PHP community forever. A small group of leaders does not a community make, but rather a oligarchy, which is exactly what the language needs right now, a rejection of the community and everything that we do - basically telling us, as community members, that our opinions and thoughts don't matter because we don't swing a huge userbase of people using our frameworks. Just when there are finally viable alternatives to PHP around, lets throw the community in the gutter. Really smooth. In closing, I think that you need to re-open the floor to discussion on what namespacing standards you decided upon and leave this list public indefinitely. I don't know how or why you decided to seize the power of standards' making like so, but I think it's a terrible, terrible decision.

« previous php.standards (#24) next »