bjori doesn't blog

8 reasons why you should *not* write for the php.net manual : You get more page hits by publishing your work on your blog You get a free pass to conferences by converting your work into presentation You get paid to submit your work to magazines & commercial websites You get a "trading card" and considered a star The community will know your name You can flame the documentations without needing to do anything about it You can copy&paste parts from the manual and sell it (see point#3) You can license your work to forbid any commercial use or further improvements :)

Quick note; We released PhD0.1RC1 today \o/ Building the php.net documentations has never been as easy or as fast. Note: You'll need 200M free diskspace (90M for the phpdoc XML sources and 110M for the generated html/php files). Fetching the phpdoc sources: bjori@lindsay:~$ cvs -d:pserver:cvsread@cvs.php.net/repository co phpdoc cvs checkout: Updating phpdoc U phpdoc/.cvsignore U phpdoc/LICENSE U phpdoc/Makefile.in [snip] Configure and test the XML bjori@lindsay:~$ cd phpdoc/ bjori@lindsay:~/phpdoc$ php configure.php configure.php: $Id: configure.php,v 1.7 2007/10/02 12:03:16 bjori Exp $ PHP version: 5.3.0-dev [snip] * No missing ids found All good. All you have to do now is run 'phd /home/bjori/phpdoc' Installing and rendering the php.net documentation bjori@lindsay:~/phpdoc$ cd .. bjori@lindsay:~$ pear install http://doc.php.net/phd/PhD-0.1RC1.tgz downloading PhD-0.1RC1.tgz ... Starting to download PhD-0.1RC1.tgz (19,683 bytes) .......done: 19,683 bytes install ok: channe

Update (February 19th): Thanks to Steph this should look fine in our favorite browser, IE6, now. I committed the conference teaser patch few hours ago, and as usual it only took about an hour for it to go live . I really think its a nice compromise, looks nice there above the news entrys and isn't that intrusive. Anyway. I also committed "latest releases" box on the right, above the "event section". The idea is to list the latest, stable, releases there - and when we are in RC phase then list them in a box below it . The links will be to qa.php.net where a "big fat warning box" will welcome the user and explain what a "release candidate" really is. Release Candidates will now get more exposure and, hopefully, get more testing - benefiting all of us. Speaking of 'latest releases', I've seen lot of code parsing the frontpage , the download page , the php-announce mailing list, heck, even cvs log in order to get the latest r

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. WTF?! came up among conference planners which didn't like the changes at all . Heck, why should they? They lost an important, free, ads on a very popular page on the web. The flip side: they have now their own page free of any distractions and irritations around their advertisements. Regain control? Yes. Conference planers have treated php.net frontpage as their private commercial ground for long enough. It was time for the php.net "staff" to take control of the frontpage back and publish php.net relevant news . This is a community effort, you are no king. Good point. I am no king. But enough is enough. Flooding the frontpage with conference announcements and call for papers had to stop. It was so overwhelming that there was no point for us to post real