pear:rfc:pear2_policy
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
pear:rfc:pear2_policy [2009/09/06 15:25] – Update pear2 policy doc add myself as sponsor, move Josh to past authors saltybeagle | pear:rfc:pear2_policy [2009/09/06 18:17] – update link targets ashnazg | ||
---|---|---|---|
Line 11: | Line 11: | ||
* Name: Brett Bieber | * Name: Brett Bieber | ||
* Email: saltybeagle@php.net | * Email: saltybeagle@php.net | ||
+ | * Name: Michael Gauthier | ||
+ | * Email: mike@silverorange.com | ||
==== Past Author(s) Information ==== | ==== Past Author(s) Information ==== | ||
Line 31: | 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 ===== | + | |
===== Expiration ===== | ===== Expiration ===== | ||
- | These policies will expire on December 1, 2008, and must be reviewed and renewed by the PEAR Group in | + | These policies will expire on August 15, 2010, and must be reviewed and renewed by the next PEAR Group in order to continue. |
- | order to continue | + | |
+ | |||
+ | ===== Policies ===== | ||
- | < | + | ==== Collectives ==== |
- | order to continue</ | + | |
+ | A collective is a grouping of similar packages, such that the "local governing" | ||
==== Commit access to the repository ==== | ==== Commit access to the repository ==== | ||
Line 68: | Line 72: | ||
==== Stale packages ==== | ==== Stale packages ==== | ||
- | Any package that is alpha (in svn.pear.php.net/ | + | The PEAR Group reserves the right to delete inactive proposals and packages. |
==== What beta status means ==== | ==== What beta status means ==== | ||
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 svn.pear.php.net/PEAR2/sandbox | + | * A concept or proof-of-concept to the [[http://svn.php.net/ |
- | 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 svn.pear.php.net/PEAR2/alpha into svn.pear.php.net/ | + | * Successful packages may then move their development directly from the [[http://svn.php.net/ |
==== Packages listed in the channel ==== | ==== Packages listed in the channel ==== | ||
- | Only packages | + | |
+ | All packages | ||
pear/rfc/pear2_policy.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1