PHP Wiki - pear:rfc

pear_package_release_protocol

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2011/04/06 10:59		current
Line 7:		Line 7:

	I'd like a new protocol added to the channels that would indicate if a channel supported remotely pushing releases. This would be in the channel.xml file and would be indicated by something like		I'd like a new protocol added to the channels that would indicate if a channel supported remotely pushing releases. This would be in the channel.xml file and would be indicated by something like
-	<releaseupload>	+
-	<baseurl type="RELEASEUPLOAD1.0">http://pear2.php.net/push</baseurl>	+	<releaseupload>
-	</releaseupload>	+	<baseurl type="RELEASEUPLOAD1.0">http://pear2.php.net/push</baseurl>
		+	</releaseupload>

	Protocol overview:		Protocol overview:
-	1. The client sends a pre-flight request, containing the releasing maintainer's handle and the package name.	+
-	2. The channel issues a one-time ticket for the release.	+	- The client sends a pre-flight request, containing the releasing maintainer's handle and the package name.
-	3. The client then sends the release, ssh encrypted to the server, along with the ticket they were issued.	+	- The channel issues a one-time ticket for the release.
-	4. The server receives the release and checks the ticket, decrypts with the user's public key, and then runs a simplechannelserver release command.	+	- The client then sends the release, ssh encrypted to the server, along with the ticket they were issued.
		+	- The server receives the release and checks the ticket, decrypts with the user's public key, and then runs a simplechannelserver release command.

	Finer points,		Finer points,

pear2_class_naming

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/09/20 19:01		current
Line 3:		Line 3:
	==== Document Information ====		==== Document Information ====
	* Title: PEAR2 Class Naming Conventions		* Title: PEAR2 Class Naming Conventions
-	* Version: 0.2.0	+	* Version: 1.0.0
	* Status: Ratified		* Status: Ratified
	* Type: Informative Document		* Type: Informative Document
Line 9:		Line 9:
	* Last Updated: September 20th, 2009		* Last Updated: September 20th, 2009
	* Passed: September 20th, 2009		* Passed: September 20th, 2009
		+
		+	This RFC has been incorporated into the PEAR2 Standards ([[pear/rfc/pear2_standards]]).

	==== Author(s) Information ====		==== Author(s) Information ====

pear2_exception_policy

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/09/22 20:10		current
Line 181:		Line 181:
	echo ' * Will catch(\bar\Exception) catch a \bar\InvalidArgumentException ???' . PHP_EOL;		echo ' * Will catch(\bar\Exception) catch a \bar\InvalidArgumentException ???' . PHP_EOL;
	$y->badArg();		$y->badArg();
-	} catch (\foo\Exception $e) {	+	} catch (\bar\Exception $e) {
	echo ' * Caught a \bar\Exception ok, so YES... this is unexpected!' . PHP_EOL;		echo ' * Caught a \bar\Exception ok, so YES... this is unexpected!' . PHP_EOL;
	}		}

pear2_naming_standards

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/09/16 22:00		current
Line 4:		Line 4:
	* Title: PEAR2 Package Naming Standard		* Title: PEAR2 Package Naming Standard
	* Version: 0.1.1		* Version: 0.1.1
-	* Status: Draft	+	* Status: Defunct
	* Type: Informative Document		* Type: Informative Document
	* Wiki link: http://wiki.php.net/pear/rfc/PEAR2_Naming_Standards		* Wiki link: http://wiki.php.net/pear/rfc/PEAR2_Naming_Standards
-	* Last updated: September 16th, 2009	+	* Last updated: December 20th, 2009
		+
		+	//This RFC is no longer under consideration, as per the PEAR Group meeting discussion on 12/20/2009.//

	==== Author(s) Information ====		==== Author(s) Information ====

pear2_policy

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/09/06 17:57		current
Line 84:		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 ====

pear2_standards

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2010/01/08 21:11		current
Line 311:		Line 311:
	...		...
	// retrieve data from info.txt		// retrieve data from info.txt
-	$info = file_get_contents(dirname(__FILE__) . '../../../data/pear2.php.net/PEAR2_PackageName/info.txt');	+	$info = file_get_contents(dirname(__FILE__) . '/../../../data/pear2.php.net/PEAR2_PackageName/info.txt');
	?>		?>

pear2_versioning_standard_revision

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/12/29 20:11		current
Line 75:		Line 75:

	This document describes the versioning standards for the PEAR2 repository that will make the		This document describes the versioning standards for the PEAR2 repository that will make the
-	paranoia setting work.	+	paranoia setting work, and defines the version and api numbering process when backwards compatibility is broken.
		+
		+	Breaking backwards compatibility requires changing the major 'A' in the A.P.I version. Once a package has been released as 'stable' the
		+	changing the major 'A' in the A.P.I version requires changing the major version 'X' in the X.Y.Z version in the package version.

	===== Approach & Requirements =====		===== Approach & Requirements =====

rfc_policy

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2026/04/24 05:18	current
Line 1:	Line 1:
	+	====== Summary ======
	+	===== Information =====
	+	==== Document Information ====
	+	* Title: RFC Policy
	+	* Version: 0.1.0
	+	* Status: Draft
	+	* Type: Informative Document
	+	* Wiki link: http://wiki.php.net/pear/rfc/RFC_Policy
	+	* Last updated: June 18th, 2007
	+
	+	==== Author(s) Information ====
	+	* Name: David Coallier
	+	* Name: Gregory Beaver
	+	* Name: Joshua Eichorn
	+	* Email: pear-group@php.net
	+
	+	==== Legal Information ====
	+	* This RFC is under the BSD License
	+
	+	==== Discussion List ====
	+	* Currently only pear-group however, future is http://news.php.net/php.pear.dev
	+
	+	===== Introduction =====
	+	This document is to outline the RFC Policy structures.
	+
	+	===== Summary =====
	+	This is the document to outline the process by which the PEAR Group will fullfil its constitutional duty of Create and vote on actual language for all official PEAR policy that affects more than 1 collective (simple majority approves policy)
	+	This process supersedes previous mechanisms for creating RFCs
	+
	+	===== Approach & Requirements =====
	+	In order to propose an RFC, this document must be followed consistently.
	+
	+	===== Definition =====
	+	* RFC - Request for Comments
	+	* Proposal - An RFC that hasn't been voted on by the PEAR group and accepted
	+	* Sponsor - a PEAR Group member who agrees to coordinate the process of turning an RFC from a proposal to accepted policy.
	+
	+	==== Approval Process ====
	+	* A proposal is sponsored by a PEAR Group member
	+	* The PEAR Group reviews the proposal and accepts it for public review by majority vote
	+	* Notice of the public review should be sent to the pear-dev mailing lists
	+	* The review period should last from 10 to 30 days with the exact time set by the proposal's sponsor
	+	* The proposal's sponsor puts it forward for vote by the PEAR group
	+	* The proposal is approved by simple majority of the PEAR Group as defined in the constitution
	+	* The proposal takes effect and becomes official policy when it is published in the PEAR manual at pear.php.net
	+
	+	==== Publishing ====
	+	All approved proposals will be published to the RFC section in the manual
	+	Information from the proposals should be put directly in appropriate sections of the manual with links to the full RFC provided
	+
	+	==== Document Format ====
	+	The document should be created in plain text, a template is provided
	+
	+	==== Document Outline ====
	+	All proposals should contain the following sections
	+	* Information
	+	* Document Information
	+	* Author Information
	+	* Legal Information
	+	* Discussion List
	+	* Introduction
	+	* Summary
	+	* Approach & Requirements
	+	* Definition
	+	* Security Considerations
	+	* Possible Problems
	+	Please see: http://dev.agoraproduction.com/pear/RFCFormat014.txt
	+
	+	===== Security Considerations =====
	+	None
	+
	+	===== Possible Problems =====
	+	None