Re: Maintaining PHP 5 documentation
Anna Filina <[email protected]>
| Newsgroups | gmane.comp.php.documentation.general |
|---|---|
| Message-ID | <CAEhKdmv9k-5+J5h7fNbCQ-=uadZsvrYy+P4_oYOoGCDiiGnv=Q@mail.gmail.com> |
Hi team, Zend has agreed to both host the legacy docs and dedicate time to maintaining them. I already put together a site that displays the archives. The docs are available here: https://php-legacy-docs.zend.com/ The archives are on GitHub: https://github.com/zendtech/php-legacy-docs (still needs readme, license and all the gory details). I fixed the style tags in the archives' HTML, so that contributors can preview their changes locally with css. I will be the main point of contact for the legacy docs until I can build a community around them. What kind of cross-linking do we want so that people don't get 404s? I point to current PHP docs if they're available for a particular page. Example 404 on php.net: https://www.php.net/manual/en/ini.sect.safe-mode.php#ini.safe-mode Corresponding legacy link that can be the failover: https://php-legacy-docs.zend.com/manual/php5/en/ini.sect.safe-mode#ini.safe-mode Cheers! Anna Filina On Fri, Dec 4, 2020 at 8:10 PM Larry Garfield <[email protected]> wrote: > On Fri, Dec 4, 2020, at 5:32 PM, Christoph M. Becker wrote: > > On 04.12.2020 at 23:56, G. P. B. wrote: > > > > > As a reminder the PHP documentation is released under the Creative > Commons > > > Attribution 3.0 licence [1] and the tools made to build it are also > open > > > source. > > > So anyone can just republish the archive online or fork the SVN/git > repo > > > from the > > > commit prior to its removal and publish it online at some other > address. > > > > > > So if someone wants to take ownership of that project they are free to > do > > > it and > > > we can possibly sort out some way to link to it from the official docs > with > > > a > > > disclaimer that doc bugs about the legacy docs should be redirect to > that > > > specific team. > > > > > > [1] https://www.php.net/manual/en/cc.license.php > > > > This appears to be a win-win scenario, so I'm fully supportive. > > On the hosting side, we'd be happy to host legacy docs at Platform.sh. > > --Larry Garfield >