On Thu, Aug 5, 2010 at 12:37 PM, Hannes Magnusson <hannes.magnus...@gmail.com> wrote:
>> We knew that when we accepted this extension and I have no problem >> with continuing to publish the mongo documentation. Or to be more >> clear, I see no reason to change anything in our policy right now. > > I have a big problem with it. This has been the policy for years. > > In the end, its the doc teams call (hence the CC). No it is not the current policy. It is the policy for the documentation (to be in php-doc's repo) but not for the code. It was never a requirement, not even the usage of a VCS is requirement. >>> We have no control whatsoever over anything, and therefore cannot even >>> pay attention to new features to document. We simply cannot have docs >>> for extensions not maintain in our infrastructure. >> >> If you want to force every pecl's project to use svn.php.net and >> pecl's bug trackers, then please make a proposal. > > I don't want to enforce it. But to get the docs in the PHP manual > certain rules have to be followed, and this is one of them. I don't see what's the code has to do with the code. As long as the doc is in php-doc, what or where is the problem? >> I don't have a problem either with projects using both pecl and >> external trackers (makes sense for daemon clients as some bugs may >> move from server to client). Howevere I do understand your feeling >> while looking at xdebug (but still has no issue). > > Using external bug tracker for the extension and then our tracker for > doc issues doesn't make sense. > The doc team simply cannot follow random bug trackers. And does not have to. Reporting bugs to pecl.php.net's tracker works just fine and developers follow them. Cheers, -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org
