RE: [PEAR-DEV] Re: [PEAR] RE: [PEAR-DEV] PEAR Group: Package Proposal Handling Rules
| From: | Lukas Smith | Date: | Fri, 05 Sep 2003 05:19:38 +0000 |
| Subject: | RE: [PEAR-DEV] Re: [PEAR] RE: [PEAR-DEV] PEAR Group: Package Proposal Handling Rules | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-21091@lists.php.net to get a copy of this message | ||
> From: Jon Parise [mailto:jon@php.net]
> Sent: Friday, September 05, 2003 5:44 AM
>
> On Thu, Sep 04, 2003 at 01:55:59PM -0300, Rocha wrote:
>
> > The point is:
> > 1) Make clear that only active developers with a PEAR account can
vote.
> > 2) active MEMBERS of a community are not the same as active
DEVELOPERS
> in a community.
> > To help people using PEAR, write articles on magazines about PEAR,
tell
> people about the
> > usefulness of PEAR isn't about developing, but in my view that makes
the
> guy part of the
> > community, and a active part of the community, dont you think?
Either
> being a developer or not.
>
> The general feeling is that active developers are better equipped to
> review proposed code and implementation details. Because proposing a
> package really comes down to proposing an engineered piece of source
> code, the developers should have the power to determine its
acceptance.
>
> The process is not intended to exclude members of the non-developing
> members of the PEAR community. Such members play an important role in
> terms of advocacy, user support and general discussion. It is hoped
> that the voting developers were also serve as advocates for this
> segment of the community, as well.
Jon his point is not in the regulation itself but in the wording we
used.
He prefers if we would say developers and not active members, as he
feels you can be an active member without being a developer.
Regards,
Lukas