PHP 5 Beta 3

And - maybe Zend can help here - to enforce the
communication
of php5 and it's features (i.e. pay some good people to write an
extra-column on
zend-website, php-website and wellknow php-portals around the world,
introducing
STEP BY STEP and CONTINUOUSLY the new php5-features, ...).

I'm co admin for a large php community, If someone can start throwing me emails for bug fixes/changes (whatever the changes may be, doesn't have to be /ext changes, send me extension work as well.) I'll definately start writing articles covering them. Getting the community ready for php5 is extremely important, and probably needs a little more attention than most people have time to give ( most of you need to code, not write documentation :) ). I would suggest starting a mailing list or some such for the admins of php community websites, where you guys can write up small explanations and lists of your changes that make it to cvs.

I will get something started if you like, the weight of having each of the
developers do something on top of the standard docs would be a little
excessive. But I agree it would be nice to have a 'What to expect from PHP5'
article out there. Or perhaps a series of of articles on the most important
features?

If anyone sends me a list of changes, send it to either this address ( lateralus@nutextonline.com ) or shadowed@asleep.net. Anything sent to me will be added to changes submitted by others and the array will be peiced together for articles at www.phpfreaks.com.

As for Zend specific changes, I would probably want to write up articles for that separately, (andi :) ), as they would be more important.

I'll be starting out hacking around in core soon, and hopefully will be ready to help bug fix sooner than later. A community for core hackers has been started at the phpfreaks forums, as well as an accompanying irc channel. ( irc.freenode.net, #php.devel ), it would probably help get things moving as far as development goes to get a lot of the developers together so they can discuss matters closely. (ps: </end huge shameless plug>) Another thing to help would be better documentation on certain aspects of hacking core ( even though, as said before, most people should be coding, and not writing documentation :p ).