pear:rfc:pear2_policy

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
pear:rfc:pear2_policy [2009/09/06 17:39] – Draft 0.3.0 reviewed and renewed by 2009 PEAR Group ashnazgpear: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. This document contains the general policies for how coding and collaboration works in PEAR2.
  
-===== General policy rules =====+
  
  
Line 40: Line 40:
 These policies will expire on August 15, 2010, and must be reviewed and renewed by the next PEAR Group in order to continue. These policies will expire on August 15, 2010, and must be reviewed and renewed by the next PEAR Group in order to continue.
  
 +
 +===== Policies =====
 +
 +==== Collectives ====
 +
 +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 ==== ==== Commit access to the repository ====
pear/rfc/pear2_policy.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1

Page Tools