Hi all

The PHP documentation used to be known to be fckingeyh kickass awesome
documentations, but since PHP 5 we have been struggling with keeping
up with all the new features and extensions that have been
implemented.

I would like to place an open call for contributions, of noone
objects, as of tomorrow (July 6th).
Attached is an NEWS entry I will be committing tomorrow morning - but
I would really appreciate if an native-English speaker could read over
it.

Any and all suggestions for improvements would be very appreciated!

-Hannes
<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom";>
  <title>Thin documentations?</title>
  <id>http://www.php.net/archive/2009.php#id2009-07-05-1</id>
  <published>2009-07-05T01:40:12+02:00</published>
  <updated>2009-07-05T01:40:12+02:00</updated>
  <category term="frontpage" label="PHP.net frontpage news"/>
  <link href="http://www.php.net/index.php#id2009-07-05-1"; rel="alternate" type="text/html"/>
  <link href="http://www.php.net/archive/2009.php#id2009-07-05-1"; rel="via" type="text/html"/>
  <content type="xhtml">
    <div xmlns="http://www.w3.org/1999/xhtml";>
     <p>Since the conception of PHP it has been known for having kicking-ass awesome documentations.</p>
     <p>The language is well known for having _the_ <strong>best</strong> documentation.</p>
     <p>In recent years people may have noticed that the documentation of new features are not exactly "sufficient" anymore, and lack in-detail explainations and "what-if"s.</p>
     <p>As of now we are placing an open call of colunteers to help the project to get up-to-speed with the massive changings the language has undergone in the recent years and catch up with all the new features the language has to offer</p>
     <p>Obivously any and all contribution is well appricated to the project and getting CVS account and karma is very simple task.</p>
     <p>If you are interested in helping out please contact the documentation team at <a href="mailto:phpdoc@lists.php.net">phpd...@lists.php.net</a></p>
    </div>
  </content>
</entry>

Reply via email to