Re: [Call For Votes] PHP::Fork
| From: | Xavier Noguer | Date: | Sat, 08 Nov 2003 15:06:57 +0000 |
| Subject: | Re: [Call For Votes] PHP::Fork | ||
| References: | 1 2 3 4 5 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-23359@lists.php.net to get a copy of this message | ||
George Schlossnagle <george@omniti.com> escribió
>
> On Nov 8, 2003, at 9:40 AM, Xavier Noguer wrote:
>
> > Martin Jansen <mj@php.net> escribió
> >
> >> (http://pear.php.net/manual/en/developers.contributing.php)
> >>
> >> It is pretty funny to see how much developers have actually read the
> >> "Developers Guide" ...
> >
> > I've read that guide. I just don't seem to be able to take it
> > seriously when
> > it lists requirements that have never, as far as I know, been voted by
> > the
> > pear group or the developer community at large, such as regressions
> > tests
> > (http://cvs.php.net/diff.php/peardoc/en/guide/developers/
> > contributing.xml?r1=1.8&r2=1.9&ty=h)
> >
> > Would you be so kind to point me to the pear group document or public
> > discussion in which this requirement was approved?
>
> This was discussed at the PEAR group meeting in Amsterdam this past
> spring. It was webcast and had open participation through irc.
From http://pear.php.net/news/meeting-2003-summary.php
:
<quote>
A QA team will be formed. It will make sure that quality standards are met.
Those standards have yet to be defined more precisely; they should be
measurable. They include the following minimum requirements: inline PHPDoc
comments, proper summary of the package purpose and a detailed usage example.
Further quality criterias are more documentation, user and developer unit
tests (using any of PHPUnit or phpt), API stability etc.
</quote>
As I understand it, a minimum criteria should be required for all package
proposals. But "non minimum" criteria should not be required. Am I wrong on
this?
Xavier
http://www.xavier-noguer.com/