On Thu, Aug 5, 2010 at 15:06, Kristina Chodorow <krist...@10gen.com> wrote: > I was asleep for the first 12 hours of this discussion, but I really like > having the mongo extension's documentation in the manual and I hope it can > stay. > > I don't want to see the docs site buckle under its own weight or have the > docs maintainers so overwhelmed that the documentation quality suffers, but > I don't think that they can realistically maintain documentation for all of > the extensions anyway, even with the commits going to one place.
That is totally true - and it is awesome that you have written the English docs - but did you know the docs have been translated to French? The Japanese version is even under development.. And whenever we make template changes, or just want to improve the markup, "you" get those for free. When people submit doc bug reports they expect the doc team to be able to solve it. I am not willing to go hunting around for random support forums and search for the location of the source to verify the report, and fix it. Things need to be under php.net if you want to use the doc infrastructure. You do have "Documentation" link on the PECL package website, which can point to external docs if you don't want it under php.net > One (perhaps) comparable project is CPAN, where all of the developers > maintain their own package's documentation, but it's all hosted on CPAN (so > it can be done and does work). It is only a fraction of the (php) developers that write or put any sort of effort into their docs. As awesome that would be, its simply not how it works. > An alternative, if the doc team just wants easy access to the extension > changes, is that I could do some sort of mirroring so that all of the git > commits are forwarded to SVN. And were are people supposed to report documentation issues? In your bugtracker or bugs.php.net? Where can I find devs to help me solve problems? How to I verify the extension hasn't been abandoned? Is it still experimental? Do we need to bump the version info? It is waaay to much hassle to work with things outside of our domain. If all the things around the extension is external, then your users expect to find the manual at your site anyway.. -Hannes
