The question, however, has always been "how useful is this feature really and does it bring more harm than good?". It's not that easy to answer since there are so many notes submitted by a wide range of users and some will likely go unnoticed while others seem to get undue attention due to their positioning near the top of the user-notes section of a particularly trafficked page.

The poster proposes a few things that could help make them a bit more effective (and useful overall) including voting on the note contents, flagging potential issues and sorting the notes based on popularity/age. He's put together a proof of concept as seen here with some of the new features.

Opinions from commentors range widly:

• "The layout's nice. But those colors are downright disgusting."
• "To be honest, the new version is 100x better."
• "It's definitely way better than the old design but still not exactly great is it?.."
• "Much more profressional. Welcome to the 21st century PHP.net."

Have an opinion on the new layout? voice it here!

The PHP development team would like to announce the immediate availability of PHP 5.3.3. This release focuses on improving the stability and security of the PHP 5.3.x branch with over 100 bug fixes, some of which are security related. All users are encouraged to upgrade to this release. [...] The PHP development team would like to announce the immediate availability of PHP 5.2.14. This release focuses on improving the stability of the PHP 5.2.x branch with over 60 bug fixes, some of which are security related.

The announcements list some of the major security enhancements and fixes in both new versions as well as a few new features like updates to the PCRE libraries and more.

Note: this PHP 5.2.14 release marks the end of active support for the PHP 5.2.x branch. It is encouraged that you upgrade to PHP 5.3 by following the steps in this migration guide.

In addition to [a local copy of your source] being faster to develop, it lets you work without needing to be connected to the Internet. But what about the tools you use while developing? If you're a PHP developer then the manual at php.net is an invaluable tool. It only make sense to have it available for when you're not online.

His example follows the official mirroring part of the PHP.net website and uses a slightly modified rsync command to fetch the manual information from the php.net site and drops it in a location locally. He throws in an Apache configuration too for a simple VirtualHost to get it up and running.

You may recall PHP Groups being created over a year ago for the purpose of networking together the leaders and organizers of PHP user groups around the world. I've been very bad about keeping things moving on this front, but I want to pick things back up and get us talking again.

If you'd like to subscribe to the list, send an email to ug-admins-subscribe [at] lists.php.net. If you don't want to subscribe but still want to keep track of what's happening, point your news reader to news://news.php.net/ug.admins.

The Windows installers and archives were missing the XSL and IMAP extensions.

These updated packages can be downloaded from the Downloads page on PHP.net as usual (with each updated package having a note indicating the change).

• PHP Optimizer by Samuel Graham Kelly IV, mentored by Derick Rethans
• gsoc:2008 - XDebug by Chung-Yang Lee, mentored by David Coallier
• PHP Bindings for Cairo by Akshat Gupta, mentored by Anant Narayanan
• Implement Unicode into PHP 6 by Henrique do Nascimento Angelo, mentored by Scott MacVicar

You can check out more information on the projects (including links to their individual pages) on this page of the Google Code website.

How do we appropriately credit the kind souls who seemingly work anonymously within the php.net CVS repository? Not sure, but here are about 8 reasons why you should write for the official PHP manual.

Among the items on his list (longer than eight reasons) are things like "You'll own a cool @php.net email address", "You'll gain experience using DocBook and the related tools to create documentation", "You'll make new friends" and "You'll help make something better, something you use. It's good to use things that get better, right?"

Check out his full post for the rest of his reasons.

Since I moved the 'current releases' info into "a giant" includable array, living in include/version.inc, we can now provide a simple XML feed (or whatever) for you to parse to get the latest release info simpler and more accurately...

What do you think? Is it worth it? What kind of format would you want it in?

He wants your feedback on this last point - would having an XML feed for just the version info be that useful? Or would it just be yet another RSS feed to add to the list to keep up with the new PHP releases?

As many of you know I changed the frontpage of php.net recently by moving conference announcements and call for papers to its own dedicated page in a desperate attempt to regain the control of our frontpage.

The rest of the post discusses the points of "why?", "regain control?", "what gave you the right?" and even links to a patch that puts a "conference teaser" back on the page (near the top).