pear:rfc:pear2_policy
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
pear:rfc:pear2_policy [2009/09/06 17:51] – group all policy details together ashnazg | pear:rfc:pear2_policy [2017/09/22 13:28] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 33: | Line 33: | ||
This document contains the general policies for how coding and collaboration works in PEAR2. | This document contains the general policies for how coding and collaboration works in PEAR2. | ||
- | ===== General policy rules ===== | + | |
Line 42: | Line 42: | ||
===== Policies ===== | ===== Policies ===== | ||
+ | |||
+ | ==== Collectives ==== | ||
+ | |||
+ | A collective is a grouping of similar packages, such that the "local governing" | ||
==== Commit access to the repository ==== | ==== Commit access to the repository ==== | ||
Line 80: | Line 84: | ||
====Package acceptance into PEAR2==== | ====Package acceptance into PEAR2==== | ||
Packages can be proposed either as | Packages can be proposed either as | ||
- | * A completed, or relatively complete package to Pepr | + | * A completed or relatively complete package to the [[http:// |
- | * A concept, or proof-of-concept to http:// | + | * A concept or proof-of-concept to the [[http:// |
- | For proof-of-concept packages they should | + | For proof-of-concept packages, they should |
- | * Post a public notice to the pear-dev mailing list stating the intention to begin development | + | * Post a public notice to the [[http:// |
- | * Request a new package be created on the pear.php.net website | + | * Request a new package be created on the [[http:// |
* Undergo a review by the collective (as defined in the previous section) when ready to move from alpha to beta stability | * Undergo a review by the collective (as defined in the previous section) when ready to move from alpha to beta stability | ||
* Once the review is complete, the package developers may request an official vote by the collective on whether the package is ready. | * Once the review is complete, the package developers may request an official vote by the collective on whether the package is ready. | ||
- | * Successful packages may then move their development directly from http:// | + | * Successful packages may then move their development directly from the [[http:// |
==== Packages listed in the channel ==== | ==== Packages listed in the channel ==== |
pear/rfc/pear2_policy.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1