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
pear:rfc:pear2_policy [2009/09/06 17:51] – group all policy details together ashnazgpear: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" 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 ====
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://pear.php.net/pepr/|PEPr Proposal system]] 
-  * A concept, or proof-of-concept to http://svn.php.net/repository/PEAR2/sandbox+  * A concept or proof-of-concept to the [[http://svn.php.net/viewvc/pear2/sandbox/|PEAR2 sandbox in SVN]]
  
-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://pear.php.net/support/lists.php|pear-dev mailing list]] stating the intention to begin development 
-  * Request a new package be created on the pear.php.net website+  * Request a new package be created on the [[http://pear.php.net/packages.php|pear.php.net]] website
   * 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.  The vote is conducted through PEPr.  Unsuccessful packages may request a second review after fixing issues noted by the collective.   * Once the review is complete, the package developers may request an official vote by the collective on whether the package is ready.  The vote is conducted through PEPr.  Unsuccessful packages may request a second review after fixing issues noted by the collective.
-  * Successful packages may then move their development directly from http://svn.php.net/repository/PEAR2/alpha into http://svn.php.net/repository/PEAR2 using svn move+  * Successful packages may then move their development directly from the [[http://svn.php.net/viewvc/pear2/sandbox/|PEAR2 sandbox]] into [[http://svn.php.net/viewvc/pear2/|PEAR2 itself]] using "svn move"
  
 ==== Packages listed in the channel ==== ==== Packages listed in the channel ====
pear/rfc/pear2_policy.1252259462.txt.gz · Last modified: 2017/09/22 13:28 (external edit)

Page Tools