Newsgroups: php.doc,php.internals
Path: news.php.net
Xref: news.php.net php.doc:969384459 php.internals:67797
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error)
To: Christian Stoller <stoller@leonex.de>
Cc: "internals@lists.php.net" <internals@lists.php.net>, phpdoc
 <phpdoc@lists.php.net>
In-Reply-To: <4ED7146272E04A47B986ED49E771E347BB4DF6F231@Ikarus.ameusgmbh.intern>
References:
	 <4ED7146272E04A47B986ED49E771E347BB4DF6F231@Ikarus.ameusgmbh.intern>
Content-Type: text/plain; charset="UTF-8"
Date: Tue, 25 Jun 2013 11:10:49 +0200
Message-ID: <1372151449.2389.27.camel@guybrush>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Moving PHP documentation to Git repository
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

On Tue, 2013-06-25 at 08:46 +0200, Christian Stoller wrote:
> Hi internals.
> 
> What do you think about moving the PHP documentation to a Git
> repository, mirrored on Github? Doing this would make it possible for
> everybody to extend the documentation easily by creating pull
> requests.

Basically that is good. To the best of my knowledge the issue though, is
not will but time. Migrating the docs is not just converting the repo,
like with PECL repos but changing the supporting infrastructure. For
instance there are tools which help to identify outdated translations
and the mentioned editor which all have to be adopted. If you want to
help there the docs group certainly would welcome it.

That aside: resources is also the issue with the online editor. We have
too few people working on docs, so in the end it doesn't make much
difference if they don't have time to review edit.php.net or github.
(while reviewing on edit.php.net has the benefit that it can directly
validate the docbook, github can't)

johannes
  (who is one of the bad people not really actively helping with docs)