Differences

This shows you the differences between two versions of the page.

--- pear:rfc:pear2_policy [2009/09/06 15:36] – update svn paths for new php svn server gauthierm
+++ pear:rfc:pear2_policy [2009/09/06 17:57] – define Collectives ashnazg
@@ Line 33: / Line 33: @@
 This document contains the general policies for how coding and collaboration works in PEAR2.
-===== General policy rules =====
 ===== 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 =====
-<del>These policies will expire on March 1, 2008, and must be reviewed and renewed by the PEAR Group in
+==== Collectives ====
-order to continue</del>
+A collective is a grouping of similar packages, such that the "local governing" of similar packages is managed by developers with similarly focused package expertise.  The responsibilities of a given collective are outlined in the [[http://pear.php.net/manual/en/constitution.text.php|Constitution (Section V)]].
 ==== Commit access to the repository ====
@@ Line 93: / Line 95: @@
 ==== Packages listed in the channel ====
-Only packages with a status of beta or stable are added to the public channel
+All packages will be listed in the public channel. Packages will be managed using the stability and paranoia options as described in the [[pear:rfc:pear2_versioning_standard_revision|versioning RFC]].