This is a list of books currently on my To Read shelf... literally. I do not suggest or anti-suggest any of them at this time as I haven't read them yet.
Current Efforts:
Blue Parabola, LLC
HubAustin
web2Project
PHP'ers:
Cal Evans
Eli White
Elizabeth Naramore
Joe LeBlanc
Matthew Turland
Matthew Weier O'Phinney
Planet PHP
Tony Bibbs
Business/mISV:
Bob Walsh
Eric Sink
Joel Spolsky
Micah Baldwin
Paul Graham
Past Projects:
CodeSnipers
HOBY
Judicial Watch
mobile FoxNews.com
NRTW
Great Tools I use:
Drupal
GitHub
NetBeans for PHP
phpUnit
Subversion
Zend Framework
This is not the home of dotProject or web2project. It is the home of CaseySoftware, LLC. Any dotProject support questions should be referred to their support forums.
Something happened at php|tek 2009. Okay, lots of stuff happened. I mean something big happened at php|tek 2009. A group representing a number of different frameworks got together and agreed to... well, they agreed to talk. What came out was the PHP Standards Group.
There are three things that struck me about the group.
First, it is led by some amazingly smart people. I've met just about everyone in the group and they're people who genuinely want to do things better.
Second, it's dealing with a problem we've all fought with... Coding Standards. Everyone hates appreciates loves coding standards. Sure, they make lots of sense until you actually have to do them and then everyone gets just a little annoyed.
Finally, there's how they're dealing with membership into the core group. Here's a snippet from Cal Evan's notes of the first meeting:
If you want to get involved, petition for membership. I'll have to warn you though that I think all of us are in agreement that too many cooks spoil the broth. I hope that the wisdom of the first meeting prevails and the bar for membership is set high. Just disagreeing with the standards we set isn't enough to warrant membership. (again, IMO)
I considered applying. I know many of the guys - I got half of them on video at php|tek 2009 - and I could probably make a strong case for inclusion in the group. I've been a strong advocate of CodeSniffer in the Subversion process for years, a regular and vocal organizer in the PHP community, and often get credit for asking good questions and warming people up to good ideas. All of that said, I considered their goals and asked myself four questions:
Would it be a good addition to my resume? Of course. There are few things that would better demonstrate a deep understanding of coding practices and a dedication to solid principles. But all of that said, what value could I provide?
Do I have a unique point of view to share? Probably not. The group has four major frameworks represented along with PEAR and the general community. There are numerous points of views and perspectives that I think everyone will be argued over enough to make my hair bleed.
Do I have unique experience or clout to bring to the group? Nope. I tend to use the tools and build custom things on top of them. I'm a consumer of these projects, not a contributor.
Is there a mechanism to voice concerns and ask questions? Yes, all of these guys are regular conference go'ers - I've seen most of them at 2+ in the last year - and they have a publicly available mailing list.
And after those four and a bit of flaming on the list, another question became relevant:
And the biggest question... Are they being elitist?
Yes, out of necessity.
No matter how chaotic or crazy the Open Source community appears, at the core of any project, you see something a little bit different. In almost every single case, you have a small group of people who helped create or currently drive the project making the final decisions on things. We even have a phrase to describe it: "Benevolent Dictator for Life." Even more interesting, the people observing and studying us have a phrase to describe it: "the onion model".
Either way, you end up with a core group of people who absorb information from the other layers and community and at some point - as leaders - have to make a decision. It doesn't mean they're not part of the community or dislike or anything of the sort... it simply means that you can't please all of the people all of the time.
Regardless, I'm going to watch what they're doing... not only to have an idea what things are being considered, but also to learn from a great group of people. I look forward to seeing what they'll come up with in the coming months and even years.
Personally, I trust this group and know they have and will continue to apply some serious thought to the development concerns and differences and come up with ideas that mostly work for the most people. And even if no one else follows the standards, the fact that all these groups do is powerful.
Good luck, gentlemen.
* Comic copyright David Farley, used without permission but permission was sought.
So glad to see this
I have felt like the PHP community has been missing this for a while, and I, like you, know or know of most of the people on that list and trust that they can make the best decisions for the benefit of the community. In every PHP class I teach, the first thing I get on my soapbox about is coding standards. I'm pretty sure I couldn't bring a unique perspective to the group, so I won't petition to join. But I will follow the progress closely, and hope that their process will remain transparent so those of us who are consumers will have the ability to ask questions.
Workflow?
The issue most of us have with the group is that there is no way of contributing to it and they explicitly[1] do not want peer review.
That kind of workflow just doesn't work for php.net projects. php.net is an OSS[2] project, for better, for worse; for richer, for poorer; in sickness and in health.
I also find it amazing that the group has the ego to flat out ignore Gregs feedback - he is *the* guy I would consult when creating a CS for namespaces.
I would really love a "namespace naming convention coding standard", and it would be fantastic if the various frameworks adopted it - but you cannot create such CS without peer review.
-Hannes
[1] http://news.php.net/php.standards/15
[2] http://news.php.net/php.standards/29
Peer Review & Feedback
One of my key points above was a mechanism for the public (non-core) group to voice concerns and ask questions and the existance of a public mailing list.
If any of those change - and you suggest that the peer review never existed - then you're right in that it doesn't fit.
If those do exist - the mailing list stays open and the peer review is resolved/figured out - then it seems like that should resolve many of the issues.
That group has now moved on
That group has now moved on to a (as far as I know) private Google Group.
That should summarize their intentions quite well.
The reason for all this fuzz is due to a poor naming of the mailinglist and awkward phrasing in the initial mail.
The whole purpose of that group was to be "The Interoperability Working Group" (thanks Cal).. CS is just a part of that, and since there is no published finalized version of such spec the group started there.
Had the mailinglist been called interop-wg@lists.php.net things would probably have turned out differently.
-Hannes
Closed List
I am unfortunate the way it went with the private list.
In my initial post, I identified one of the important things as being a way to "voice concerns and ask questions". While I think a set of interoperability standards and agreements are required, a closed list does and will continue to put them on the defensive where half the discussion will be related to why it's closed as opposed to the technical viability/validity of the decisions made.
Hopefully when the time comes for a public release, they'll have a good plan for accepting feedback and incorporating selected logical portions of it.
The mission
Hey Keith, this is a great write-up, but our goals go beyond just coding standards, and into actually defining some common ground for how applications/libraries/frameworks should be structured. Check out this post by Travis, who went to the trouble of rounding us all up, I think it pretty much sums it up for everyone: http://www.travisswicegood.com/index.php/2009/06/02/my-goals-for-the-php-standards-group
Post new comment