On Sep 13, 2007, at 12:52 AM, Pierre wrote:
On 9/13/07, Hartmut Holzgraefe <[EMAIL PROTECTED]> wrote:
Pierre wrote:
Hi Stan,
Take #2
Why "pollute" the pecl repository with tons of doc files when we
have
a dedicated place for them?
to have things self-contained all-in-one-place?
Having a couple of examples and text files to explain the basics is a
good thing but not the docbook stuff. If anyone and his mother begins
to choose what is best for "him" and simply ignore the common
practice, I wonder why we bother with CS and other rules.
It is a maintenance nightmare to maintain php-doc in there. Then if
the goal is to bundle these extensions in php, the docs should follow
our standards and should be maintained in php-doc (just like almost
all PECL extensions).
People commit documentation to the phpdoc module and not within the
pecl source. There is a mechanism in the current build system that
checks pecl sources for documentation, but the doc team does not use
it nor do we plan to in the new build system. Having it all together
easily allows fellow doc team members to update it, and allows for
better peer review. Both routes have their advantages but we should
have only one and today that route is a single repository for all
documentation... pecl or otherwise.
If there is a karma issue here then please speak up as we could
easily give each pecl maintainer karma to the appropriate location in
phpdoc. Currently this is done upon request.
Regards,
Philip
