PHP Wiki

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');
	?>		?>

2008-12-28

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

2008/12/28 21:48		current
Line 43:		Line 43:
	* http://pear.php.net/bugs/bug.php?id=14772		* http://pear.php.net/bugs/bug.php?id=14772
	* http://pear.php.net/bugs/bug.php?id=12384		* http://pear.php.net/bugs/bug.php?id=12384
-	* Get Services_Akismet2 up and running
	* Services_ExchangeRates [[http://pear.php.net/bugs/search.php?cmd=display&package_name[]=Services_ExchangeRates&status=OpenFeedback&bug_type=Bugs\|needs some love]]!		* Services_ExchangeRates [[http://pear.php.net/bugs/search.php?cmd=display&package_name[]=Services_ExchangeRates&status=OpenFeedback&bug_type=Bugs\|needs some love]]!
	* <del>Parse error</del>, doconnor		* <del>Parse error</del>, doconnor
Line 96:		Line 95:
	* MP3_Playlist - phpcs - doconnor		* MP3_Playlist - phpcs - doconnor
	* Net_IPv6 got into the pear test suite - doconnor		* Net_IPv6 got into the pear test suite - doconnor
		+	* Get Services_Akismet2 up and running - gauthierm and dufuz

2009-01-17

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

2009/01/18 21:54		current
Line 86:		Line 86:
	* Test the new version of pearweb - http://euk1.php.net/		* Test the new version of pearweb - http://euk1.php.net/
	* doconnor made a few patches for trivial issues		* doconnor made a few patches for trivial issues
		+	* Releases don't work :( White screen of death

2008-12-06

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

2008/12/06 15:06		current
Line 38:		Line 38:
	* <del>[[http://pear.php.net/bugs/bug.php?id=14868\|Bug #14868 Validate_AT unit test failures]]</del> - doconnor, contacted Nov 5 and 27th		* <del>[[http://pear.php.net/bugs/bug.php?id=14868\|Bug #14868 Validate_AT unit test failures]]</del> - doconnor, contacted Nov 5 and 27th
	* Followup on [[http://pear.php.net/bugs/search.php?cmd=display&search_for=PHPUnit&php_os=&boolean=0&bug_type=&bug_age=0&bug_updated=0&order_by=ts1&direction=DESC&packagever=&phpver=&limit=30&handle=&assign=&maintain=&showmenu=1&showmenu=1&status=Open PHPUnit patches\|Updating unit tests to PHPUnit3]]		* Followup on [[http://pear.php.net/bugs/search.php?cmd=display&search_for=PHPUnit&php_os=&boolean=0&bug_type=&bug_age=0&bug_updated=0&order_by=ts1&direction=DESC&packagever=&phpver=&limit=30&handle=&assign=&maintain=&showmenu=1&showmenu=1&status=Open PHPUnit patches\|Updating unit tests to PHPUnit3]]
-	* Services_Yadis - maintained? Or can we get [[http://pear.php.net/bugs/search.php?cmd=display&package_name[]=Services_Yadis&status=OpenFeedback&bug_type=Bugs\|these bugs resolved]]?	+	* <del>Services_Yadis - maintained? Or can we get [[http://pear.php.net/bugs/search.php?cmd=display&package_name[]=Services_Yadis&status=OpenFeedback&bug_type=Bugs\|these bugs resolved]]</del>? New release (doconnor)

	==== Specific tasks ====		==== Specific tasks ====

2009-02-07

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

2009/02/09 23:15		current
Line 11:		Line 11:

	===== What are we doing =====		===== What are we doing =====
-	* Triage the <del>[[http://pear.php.net/bugs/search.php?search_for=&boolean=0&limit=50&order_by=id&direction=DESC&cmd=display&status=Open&bug_type=All&php_os=&packagever=&phpver=&assign=&maintain=&author_email=&bug_age=0&bug_updated=0\|latest 50 bugs]]</del>	+	* Triage the <del>[[http://short.ie/latest50pearbugs\|latest 50 bugs]]</del>
	* Write tests, seek feedback, improve the overall quality of reports.		* Write tests, seek feedback, improve the overall quality of reports.
	* See if we can knock off <del>[[http://pear.php.net/bugs/search.php?search_for=parse&boolean=0&limit=30&order_by=id&direction=DESC&cmd=display&status=Open&bug_type=Bug&php_os=&packagever=&phpver=&assign=&maintain=&author_email=&bug_age=0&bug_updated=0\|parse error related bugs]]</del> :)		* See if we can knock off <del>[[http://pear.php.net/bugs/search.php?search_for=parse&boolean=0&limit=30&order_by=id&direction=DESC&cmd=display&status=Open&bug_type=Bug&php_os=&packagever=&phpver=&assign=&maintain=&author_email=&bug_age=0&bug_updated=0\|parse error related bugs]]</del> :)

2008-04-06

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

2008/11/07 22:08		current
Line 32:		Line 32:

	Our options are:		Our options are:
-	* a complete rewrite from scratch with PHP 5	+	* a complete rewrite from scratch with PHP 5
-	* incremental attempts to port the newer changes across from perl	+	* incremental attempts to port the newer changes across from perl
-	* write oodles of test cases and see which of the above two scares us less at the end of it	+	* write oodles of test cases and see which of the above two scares us less at the end of it

	See [[Spreadsheet Excel Writer]] for a suggestion on how to write cross language tests.		See [[Spreadsheet Excel Writer]] for a suggestion on how to write cross language tests.

2009

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

2009/03/12 14:50		current
Line 121:		Line 121:
	//Possible mentors: Helgi, Brett//		//Possible mentors: Helgi, Brett//

-	This will involve working on Pyrus installer which is the next generation PEAR installer.	+	Pyrus is a self-contained package delivery system for PHP that takes advantage of PHP's strongest features as of PHP version 5.3.
-	PHP 5.3+, namespaces and all the goodies that come with PHP 5.3	+

-	This includes writing good chunks of the installer from scratches, write extensive unit tests, design APIs and still make it work with existing channels and packages.	+	Pyrus supports
-	This will require very good understanding of PHP, XML and other technologies a like.	+

		+	* Robust, remote dependency validation and download
		+	* Creation of phar/zip/tar packages in conjunction with the Pyrus_Developer package
		+	* Installation of local or remote packages and abstract package installation (as in "install the beta version of this package")
		+	* Redundant registries, allowing re-building corrupted installs
		+	* Registries in Sqlite, Xml, and Serialized PHP format
		+	* managing PEAR installations
		+	* Packages that can work with or without installation to support try-before-you-buy or bundling packages in other projects
		+	* Full asymmetric signed packages using OpenSSL (natively supported through the phar extension)
		+	* No need to install Pyrus, run directly from the downloaded phar archive.
		+	* Customizability through extensions to Pyrus
		+
		+	This is a major leap of functionality over the PEAR Installer, and will be a major component of the PHP Language when completed, as the PEAR installer was for earlier versions of PHP.
		+
		+	To develop Pyrus, you need to have the ability to work with the following technologies on a very high level:
		+
		+	* Subversion source repository use
		+	* XML (including proficiency in XMLReader/XMLWriter/SimpleXML extensions)
		+	* PHP 5 Object-Oriented getters/setters (__get/__set)
		+	* PHP 5 Object-Oriented ArrayAccess interface
		+	* PHP 5 Iterator interface
		+	* PHP 5 SPL iterators
		+	* PHP 5 exceptions and exception handling
		+	* SQL and Sqlite database, in order to maintain Sqlite3 registry
		+
		+	You also need a basic understanding of:
		+
		+	* PHP Namespaces (new in PHP 5.3)
		+	* PHP closures (new in PHP 5.3)
		+	* PHPT testing format
		+	* Testing methodologies (code coverage/testing behavior/designing code to be testable)
		+	* PEAR packages and the PEAR Installer
		+	* Basic compilation of PECL extensions
		+
		+	Architecturally, you will be expected to assist in the following processes:
		+
		+	- Writing unit tests for the installer in the PHPT test format
		+	- Implementing the plugin system for Pyrus
		+	- Improving the command-line interface to Pyrus
		+	- Ensuring Pyrus can manage an existing PEAR repository
		+	- Porting PECL compilation code from the PEAR Installer to Pyrus
		+	- General bugfixing/small feature implementation as specified by the Pyrus roadmap
		+
		+	As of the proposal, Pyrus is at approximately 50% code coverage, and it will be much higher by the time GSoC begins
		+
		+	====Deliverables====
		+	===Midterm===
		+	We expect a working plugin system and PECL compilation to be working on unix, as well as approximately 70% code coverage
		+
		+	===Final===
		+	For the final review we would expect a fully functioning installer with approximately 80% code coverage.

	===== PEAR CI =====		===== PEAR CI =====

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;
	}		}

2008-05-03

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

2026/09/01 07:02	current
Line 1:	Line 1:
	+	=== Who's running it? ===
	+
	+	=== What are we doing ===
	+	Working from [[http://pear.php.net/bugs/search.php?search_for=&boolean=0&limit=All&order_by=&direction=ASC&cmd=display&status=Open&bug_type=Bug&php_os=&packagever=&phpver=&assign=&maintain=&author_email=&bug_age=0&bug_updated=0\|lowest to highest]]
	+
	+
	+	=== Help needed / Low hanging fruit ===
	+	* [http://pear.php.net/bugs/bug.php?id=11815 Bug 11815] - decide which version is the one true version
	+	* [http://pear.php.net/bugs/bug.php?id=6356 Bug 6356] - Fatal error with PHP 5 / Determine future of Image_Remote package
	+	* [http://pear.php.net/bugs/bug.php?id=2067 Doc Req 2067] - Package documentation for [http://pear.php.net/package/Auth_PrefManager2 Auth_PrefManager2]
	+	* [http://pear.php.net/bugs/2885 Bug 2885] - Wrong class name in Auth_PrefManager2
	+
	+	* [http://pear.php.net/bugs/bug.php?id=7252 Bug 7252] - Undefined variable (tests needed)
	+	* [http://pear.php.net/bugs/bug.php?id=7897 Bug 7897] - XML_FastCreate makes the wrong sort of CDATA
	+	* [http://pear.php.net/bugs/bug.php?id=11511 Bug 11511] - BC break (use of self vs PHP 4)
	+	* [http://pear.php.net/bugs/bug.php?id=12575 Bug 12575] - Resolve licencing confusion
	+	* [http://pear.php.net/bugs/bug.php?id=13482 Bug 13482] - Bad md5sum for Validate_HU tar
	+	* [http://pear.php.net/bugs/bug.php?id=12086 Bug 12086] - CaseSensitivity patch for Net_UserAgent_Detect
	+	* [http://pear.php.net/bugs/bug.php?id=13605 Bug 13605] - Patch: Make Console_GetArgs work with phpunit3
	+
	+	=== In Progress ===
	+	* doconnor: There's a few packages with source missing from CVS, with no links to a repo. I've been mailing the maintainers to politely hassle.
	+	* http://pear.php.net/package/I18N_UnicodeString
	+	* http://pear.php.net/package/Validate_HU
	+
	+	=== Accomplishments ===
	+	* ashnazg: I've created a test suite for all API methods in XML_Util.
	+	* ashnzag: [http://pear.php.net/bugs/bug.php?id=4950 Bug 4950] - is closed
	+	* firman: [http://pear.php.net/bugs/bug.php?id=13615 Bug 13615] - Patch: Fix timezone data
	+	* doconnor: [http://pear.php.net/bugs/bug.php?id=7924 Bug 7924] - Net_Geo has a dependency on an unstable package
	+

2009-03-21

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

2009/03/22 01:24		current
Line 51:		Line 51:
	* Contact_Vcard_Parse		* Contact_Vcard_Parse
	* Validate_DE - Stefan is busy but aware, emailed March 2nd		* Validate_DE - Stefan is busy but aware, emailed March 2nd
		+	* Net_DNS - emailed 22nd March, doconnor
	==== Targets to update to package 2.0 xml ====		==== Targets to update to package 2.0 xml ====

2008-11-15

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

2008/11/17 07:37		current
Line 7:		Line 7:
	===== Overall Goal =====		===== Overall Goal =====
	Increase the unit test coverage for new issues, while decreasing the amount of failures.		Increase the unit test coverage for new issues, while decreasing the amount of failures.
		+
		+	===== Participants =====
		+	cweiske, doconnor, ifeghali, quipo, gauthierm, & kguest (earlier in week)

	===== What are we doing =====		===== What are we doing =====

faq

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

2010/08/17 03:56		current
Line 1:		Line 1:
	====== FAQ ======		====== FAQ ======
	.. and other mailing list answers.		.. and other mailing list answers.
		+
		+	This page is meant to be a quick and easy scratchpad of good answers and ideas - candidates to be polished and migrated into the proper FAQs.

	===== Where's the proper FAQs? ======		===== Where's the proper FAQs? ======
-	* [[http://pear.php.net/manual/en/faq.users.php Users]]	+	* [[http://pear.php.net/manual/en/faq.users.php\|Users]]
-	* [[http://pear.php.net/manual/en/faq.devs.php Developers]]	+	* [[http://pear.php.net/manual/en/faq.devs.php\|Developers]]

	===== How do I become a PEAR developer? =====		===== How do I become a PEAR developer? =====

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_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 ====

roadmap

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

2011/06/25 22:36		current
Line 185:		Line 185:
	* The ability to freeze / hold a package, while frozen, one can not upgrade it (potentially not remove it either).http://pear.php.net/bugs/10570		* The ability to freeze / hold a package, while frozen, one can not upgrade it (potentially not remove it either).http://pear.php.net/bugs/10570
	* Ability to migrate one package from X channel to Y (PHPUnit) http://pear.php.net/bugs/4208 this one does impose some security implication we have to solve		* Ability to migrate one package from X channel to Y (PHPUnit) http://pear.php.net/bugs/4208 this one does impose some security implication we have to solve
		+	* [Greg Note: ^^ This is already implemented]
	* Look at AMO, yum, apt-get, canory and friends (PackageKit ?)		* Look at AMO, yum, apt-get, canory and friends (PackageKit ?)
	* rpm / deb generations out of the box (external packages like now ?) - potentially others, as plugins perhaps to have less pollution		* rpm / deb generations out of the box (external packages like now ?) - potentially others, as plugins perhaps to have less pollution

ci

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

2012/04/12 23:32		current
Line 31:		Line 31:
	In general, we encourage the use of an appropriate phpunit.xml - we target PHPUnit 3.6 at this time.		In general, we encourage the use of an appropriate phpunit.xml - we target PHPUnit 3.6 at this time.

-	Your package directory layout should allow you to successfully run your test suite as below:	+	Your package directory layout should allow you to successfully run your test suite as below (assuming svn):
	<code bash>		<code bash>
	$ cd Foo_Bar/trunk		$ cd Foo_Bar/trunk

20090920

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

2009/09/20 20:24		current
Line 102:		Line 102:

	Action Items:		Action Items:
-	* Christian will QA_PEAR_CI and put it onto svn.php.net	+	* Christian will fetch QA_PEAR_CI and put it onto svn.php.net
	* Bill will see about getting Chuck in touch with Oleg, Digg's development engineer for pUC build ideas.		* Bill will see about getting Chuck in touch with Oleg, Digg's development engineer for pUC build ideas.

Line 128:		Line 128:
	* Once that's done, Christian will do a new release for pearweb.		* Once that's done, Christian will do a new release for pearweb.
	* Christian or Brett will then enable the cron job, and notify Bill to stop his.		* Christian or Brett will then enable the cron job, and notify Bill to stop his.
-	* Christian will QA_PEAR_CI and put it onto svn.php.net	+	* Christian will fetch QA_PEAR_CI and put it onto svn.php.net
	* Bill will see about getting Chuck in touch with Oleg, Digg's development engineer for pUC build ideas.		* Bill will see about getting Chuck in touch with Oleg, Digg's development engineer for pUC build ideas.
	* Chuck will put the PEAR Group goals on a separate page in the wiki		* Chuck will put the PEAR Group goals on a separate page in the wiki

	=== Next Meeting ===		=== Next Meeting ===
-	Note scheduled. We'll have to do this over email.	+	Not scheduled. We'll have to do this over email.

2008-10-25

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

2026/09/01 07:02	current
Line 1:	Line 1:
	+	====== Bug Triage Day October 25-26th 2008 ======
	+
	+	===== Who's running it? =====
	+	(on auto-pilot)
	+
	+	===== When =====
	+	October 25th, 26th in #pear-bugs on irc.efnet.org
	+
	+	See [[http://www.google.com/calendar/embed?src=rslkppoio4rtq6nm7b6fptclfo%40group.calendar.google.com]]
	+
	+	===== Attendees =====
	+	* cweiske
	+	* doconnor
	+	* kguest
	+	* amir
	+	* justinpatrin
	+	* till
	+	* avb
	+	* Tatsuya Tsuruoka
	+
	+
	+	===== What are we doing =====
	+	* Followup on [[http://pear.php.net/bugs/search.php?cmd=display&search_for=PHPCS&php_os=&boolean=0&bug_type=&bug_age=0&bug_updated=0&order_by=ts1&direction=DESC&packagever=&phpver=&limit=30&handle=&assign=&maintain=&showmenu=1&showmenu=1&status=Open\|PHPCS patches]]
	+	* <del>Validate</del> (amir)
	+	* <del>HTTP_Session2</del> (till)
	+	* <del>Gtk2_PHPConfig</del> (kguest)
	+	* <del>Net_Wifi</del> (cweiske)
	+	* <del>File_XSPF</del> (doconnor)
	+	* <del>Net_Whois</del> (doconnor)
	+
	+	* Followup on [[http://pear.php.net/bugs/search.php?cmd=display&search_for=PHPUnit&php_os=&boolean=0&bug_type=&bug_age=0&bug_updated=0&order_by=ts1&direction=DESC&packagever=&phpver=&limit=30&handle=&assign=&maintain=&showmenu=1&showmenu=1&status=Open\|PHPUnit patches]]
	+	* Make tests pass:
	+	* <del>Text_Wiki</del> (justinpatrin)
	+	* <del>Services_Amazon</del> (Tatsuya Tsuruoka)
	+	* <del>File_Find</del> (doconnor)
	+	* <del>Triage the [[http://pear.php.net/bugs/search.php?search_for=&boolean=0&limit=70&order_by=id&direction=DESC&cmd=display&status=Open&bug_type=All&php_os=&packagever=&phpver=&assign=&maintain=&author_email=&bug_age=0&bug_updated=0\|latest bugs]]</del> (doconnor: done-ish)
	+	* <del>HTTP_Client 1.2.1</del> released (avb)
	+	* <del>File_XSPF missing package.xml</del> (kguest)
	+	* <del>MDB2_Schema test coverage</del> (Igor Feghali)
	+
	+	==== Other items needing volunteers ====
	+	* writing tests for MDB2_Schema bugs (particularly those with patches);
	+	* <del>I18N_UnicodeString needs to be put in CVS (http://news.php.net/php.pear.dev/50419) (in CVS and fixed by kguest)</del>
	+	* <del>PHP_Fork into CVS</del> (cweiske)
	+	* Packages that have the most open bug reports (http://pear.php.net/bugs/stats.php)
	+	* <del>Apply Net_Ping patch for bug #14492</del> (patch by [[shupp]], applied by kguest)
	+	* Docs for Validate packages - ([[amir]] ?)
	+	* Payment_DTA into CVS (doconnor consulting with lead)
	+	* <del>Fix Validate_AU unit tests</del> (doconnor was shirking, but Validate_AU-0.1.2 now exists)
	+
	+	==== Notes: The best way to write unit tests for CVS ====
	+	Say you have a package, Foo_Bar_Item
	+
	+	If you structure you package as:
	+
	+	CVS dir:
	+	<code>/Foo_Bar_Item/</code>
	+
	+	Structure:
	+	<code>/Foo_Bar_Item/Foo/Bar/Item.php
	+	/Foo_Bar_Item/tests/AllTests.php</code>
	+
	+	Then it makes doing
	+	<code>
	+	you@locahost:~/pear$ cvs update
	+	you@locahost:~/pear$ cd Foo_Bar_Item
	+	you@locahost:~/pear/Foo_Bar_Item$ phpunit tests/
	+	</code>
	+	... work just fine with the existing require_once patterns; and when you install the package, the tests should still run.
	+
	+	Otherwise, if you have packages with different structure, you will often have to:
	+
	+	<code>
	+	you@locahost:~/pear$ cvs update
	+	you@locahost:~/pear$ cd Foo_Bar_Item
	+	you@locahost:~/pear/Foo_Bar_Item$ pear package
	+	you@locahost:~/pear/Foo_Bar_Item$ sudo pear install -fa Foo_Bar_Item-0.1.0.tgz
	+	you@locahost:~/pear/Foo_Bar_Item$ phpunit tests/
	+	</code>
	+
	+	==== Unit test results ====
	+	These unit test results are generated overnight / on demand on doconnor's development copy; so may be somewhat overly passing at the moment :)
	+	* [[http://docs.google.com/Doc?id=acm3gmkf7hk_17dfbp7bsw\|Unit test results - Oct 23rd]] 518 / 3195 tests fail or error
	+	* Tests: 3197, Assertions: 20496, Failures: 398, Errors: 48, Incomplete: 86.
	+	* Tests: 3198, Assertions: 20496, Failures: 274, Errors: 48, Incomplete: 86.
	+
	+

2008-03-22

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

2008/11/07 22:03		current
Line 2:		Line 2:

	===== Who's running it? =====		===== Who's running it? =====
-	Helgi is running this [[Bug Triage Day]]	+	Helgi is running this [[pear:qa:bug_triage\|Bug Triage Day]]

	===== What are we doing =====		===== What are we doing =====

migration

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

2011/05/02 23:51		current
Line 6:		Line 6:

	===== How? =====		===== How? =====
-	Two options:	+	Multiple options:
	* Sudden cutover - redirect traffic to pear2.php.net; use the migration pain to inspire contributions and improved functionality.		* Sudden cutover - redirect traffic to pear2.php.net; use the migration pain to inspire contributions and improved functionality.
	* Phased migration - component by component swap processes such as PEPR over to feed into pear2; co-brand the pear.php.net front page experience; end of life unsupported packages.		* Phased migration - component by component swap processes such as PEPR over to feed into pear2; co-brand the pear.php.net front page experience; end of life unsupported packages.

bug_triage

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

2009/03/11 02:10		current
Line 114:		Line 114:
	* [[pear:qa:bug triage:2009-01-17]]		* [[pear:qa:bug triage:2009-01-17]]
	* [[pear:qa:bug triage:2009-02-07]]		* [[pear:qa:bug triage:2009-02-07]]
		+	* [[pear:qa:bug triage:2009-03-21]]

opendocument

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

2011/08/24 06:29		current
Line 3:		Line 3:
	^ Current version: \| 0.2.0 (alpha) was released on 2009-07-28 \|		^ Current version: \| 0.2.0 (alpha) was released on 2009-07-28 \|
	^ Source repository: \| https://github.com/pear/OpenDocument \|		^ Source repository: \| https://github.com/pear/OpenDocument \|
-	^ Bug tracker: \| http://pear.php.net/bugs/search.php?cmd=display&package_name[]=OpenDocument \|	+	^ Bug tracker: \| [[http://pear.php.net/bugs/search.php?cmd=display&package_name[]=OpenDocument]] \|

	OpenDocument is a package to create, read and update [[http://en.wikipedia.org/wiki/OpenDocument\|Open Document Format]] files. ODF is an XML-based file format for office documents such as spreadsheets, charts, presentations and word processing documents, with a standardised specification as an //OASIS Committee Specification// ([[http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2.html\|v.1.2]]) and //ISO/IEC 26300:2006// (v.1.0 with v.1.1 currently a Draft Amendment). The former specification is the most recently updated, is publicly available, and is the one we're working from for this PEAR package.		OpenDocument is a package to create, read and update [[http://en.wikipedia.org/wiki/OpenDocument\|Open Document Format]] files. ODF is an XML-based file format for office documents such as spreadsheets, charts, presentations and word processing documents, with a standardised specification as an //OASIS Committee Specification// ([[http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2.html\|v.1.2]]) and //ISO/IEC 26300:2006// (v.1.0 with v.1.1 currently a Draft Amendment). The former specification is the most recently updated, is publicly available, and is the one we're working from for this PEAR package.

documentation

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

2009/07/21 21:51		current
Line 1:		Line 1:
	====== File_Bittorrent Documentation ======		====== File_Bittorrent Documentation ======
-	The API-Documentation is available here:	+	The API-Documentation is available here:\\
	http://pear.php.net/package/File_Bittorrent2/docs/latest/		http://pear.php.net/package/File_Bittorrent2/docs/latest/

20080713

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

2008/11/09 04:29		current
Line 10:		Line 10:
	===== Minutes =====		===== Minutes =====

-	== Attendees ==	+	==== Attendees ====
	* Brett ([[saltybeagle]])		* Brett ([[saltybeagle]])
	* Helgi ([[helgi]])		* Helgi ([[helgi]])

2008-08-23

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

2026/09/01 07:02	current
Line 1:	Line 1:
	+	=== Who's running it? ===
	+	Daniel ([[doconnor]])
	+
	+	Chuck ([[ashnazg]])
	+
	+	=== When ===
	+	August 23rd, 24th in #pear-bugs on irc.efnet.org
	+
	+	See http://www.google.com/calendar/embed?src=rslkppoio4rtq6nm7b6fptclfo%40group.calendar.google.com
	+
	+	=== Attendees ===
	+	Chuck Burgess [[ashnazg]]
	+
	+	[http://wiki.pear.php.net/index.php/User:Kguest Ken Guest]
	+
	+	Amir Saied [[amir]]
	+
	+	Bill Shupp [[shupp]]
	+
	+	=== What are we doing ===
	+
	+	* writing tests for MDB2_Schema bugs (particularly those with patches);
	+	* I18N_UnicodeString (http://news.php.net/php.pear.dev/50419)
	+	* Bugs with Patches (http://news.php.net/php.pear.dev/50418)
	+	* Packages have the most open bug reports (http://pear.php.net/bugs/stats.php)
	+	* The 50 newest bugs and feature requests
	+	(http://pear.php.net/bugs/search.php?search_for=&boolean=0&limit=50&order_by=id&direction=DESC&cmd=display&status=Open&bug_type=All&php_os=&packagever=&phpver=&assign=&maintain=&author_email=&bug_age=0&bug_updated=0)
	+	* Packages with Coding Style/Unit test problems (http://pear.cweiske.de/overview.htm)
	+
	+	=== In Progress ===
	+	* Follow up on SOAP bugs marked for feedback - ([[doconnor]])
	+	* docs for Validate packages - ([[amir]])
	+
	+	=== Accomplishments ===
	+	* Licensing and package.xml updates for XML related packages - ([[ashnazg]])
	+	* XML_DTD, XML_FOAF, XML_Beautifier, XML_Parser, XML_Serializer
	+	* HTML_TreeMenu bug work - ([[kguest]])
	+	* patches for Genealogy_Gedcom CS issues - ([[kguest]])
	+	* patch for Net_Ping bug #14492 - ([[shupp]])

git

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

2017/09/22 13:28		current
Line 21:		Line 21:

	==== SSH keys ====		==== SSH keys ====
-	* SSH Keys are managed on http://master.php.net/manage/users.php	+	* SSH Keys are managed on https://main.php.net/manage/users.php


Line 31:		Line 31:
	==== Permissions ====		==== Permissions ====
	* Permissions = Karma		* Permissions = Karma
-	* Git Karma management via http://git.php.net/?p=karma.git	+	* Git Karma management via https://github.com/php/karma
	* Which PEAR people have access to karma.git? FIXME		* Which PEAR people have access to karma.git? FIXME

numbers_words

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

2008/11/26 13:34		current
Line 22:		Line 22:
	Do you speak any of:		Do you speak any of:

-	* Bulgarian	+	* <del>Bulgarian</del>
	* Czech		* Czech
	* Danish		* Danish

20090906

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

2009/09/08 13:18		current
Line 37:		Line 37:

	==== Followup from Last Meeting on 2009-08-16 ====		==== Followup from Last Meeting on 2009-08-16 ====
		+	* See the [[pear:group:meetingagenda:20090816\|2009-08-16 meeting's minutes]]
	* Bill got the 'pear' twitter account		* Bill got the 'pear' twitter account
	* Bill created a cron job that puts PEAR package releases on Twitter		* Bill created a cron job that puts PEAR package releases on Twitter

2008-09-14

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

2026/09/01 07:02	current
Line 1:	Line 1:
	+	=== Who's running it? ===
	+	Daniel ([[doconnor]])
	+
	+	Chuck ([[ashnazg]])
	+
	+	=== When ===
	+	September 14th, 15th in #pear-bugs on irc.efnet.org
	+
	+	See http://www.google.com/calendar/embed?src=rslkppoio4rtq6nm7b6fptclfo%40group.calendar.google.com
	+
	+	=== Attendees ===
	+
	+	=== What are we doing ===
	+
	+	* writing tests for MDB2_Schema bugs (particularly those with patches);
	+	* I18N_UnicodeString (http://news.php.net/php.pear.dev/50419)
	+	* Bugs with Patches (http://news.php.net/php.pear.dev/50418)
	+	* Packages have the most open bug reports (http://pear.php.net/bugs/stats.php)
	+	* The 50 newest bugs and feature requests (http://pear.php.net/bugs/search.php?search_for=&boolean=0&limit=50&order_by=id&direction=DESC&cmd=display&status=Open&bug_type=All&php_os=&packagever=&phpver=&assign=&maintain=&author_email=&bug_age=0&bug_updated=0)
	+	* Packages with Coding Style/Unit test problems (http://pear.cweiske.de/overview.htm)
	+
	+	=== In Progress ===
	+	* Follow up on SOAP bugs marked for feedback - ([[doconnor]])
	+	* Docs for Validate packages - ([[amir]])
	+	* Follow up on Genealogy Gedcom patches - ([[kguest]])
	+	* Follow up on Net_Ping patch for bug #14492 - ([[shupp]])
	+
	+

2008-10-04

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

2008/11/07 22:10		current
Line 26:		Line 26:
	* Follow up on SOAP (and other) bugs marked for feedback - ([[doconnor]])		* Follow up on SOAP (and other) bugs marked for feedback - ([[doconnor]])

-
-	[[Category:Bug Triage Day]]

group

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

2009/09/06 17:29		current
Line 8:		Line 8:
	The Group and President roles and responsbilities are set forth in the [[http://pear.php.net/manual/en/constitution.php\|Constitution]].		The Group and President roles and responsbilities are set forth in the [[http://pear.php.net/manual/en/constitution.php\|Constitution]].

-	===== 2009-2010 =====	+	==== 2009-2010 ====
	[[http://pear.php.net/election/info.php?election=12&results=1\|Election Results]]		[[http://pear.php.net/election/info.php?election=12&results=1\|Election Results]]
	* Brett Bieber		* Brett Bieber

payment_process2

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

2009/03/19 06:24		current
Line 123:		Line 123:

	==== 0.3.0 ====		==== 0.3.0 ====
		+	* <del>Add ANZ driver</del>
	* Fix typeMapping concept		* Fix typeMapping concept
	* Fix cvvCode concept in results		* Fix cvvCode concept in results

documentation

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

2008/11/17 05:30		current
Line 23:		Line 23:


-	'''Items which I don't know where to place:'''	+	==== Items which I don't know where to place: ====
	- <del>Decide on a move to a set/book structure, and where the sets/books are separated at (categories/collectives, or individual packages)</del> - done, cweiske		- <del>Decide on a move to a set/book structure, and where the sets/books are separated at (categories/collectives, or individual packages)</del> - done, cweiske
	- <del>what, semantically is involved in this - docbook reference</del> - done, cweiske		- <del>what, semantically is involved in this - docbook reference</del> - done, cweiske
Line 38:		Line 37:
	This is a start at a conversion script, which will handle almost all of step 4 above.		This is a start at a conversion script, which will handle almost all of step 4 above.

-	'''Execution examples:'''	+	==== Execution examples ====

-	Convert all files $	+	Convert all files
	<code>./peardoc_conversion.sh</code>		<code>./peardoc_conversion.sh</code>

-	Convert one file $	+	Convert one file
	<code>./peardoc_conversion.sh peardoc/en/chapters/installation/shared.xml</code>		<code>./peardoc_conversion.sh peardoc/en/chapters/installation/shared.xml</code>

20090816

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

2009/08/19 00:52		current
Line 74:		Line 74:
	* agenda item was mostly skipped as Christian and Daniel are not present		* agenda item was mostly skipped as Christian and Daniel are not present
	* QA needs to be emphasized for PEAR		* QA needs to be emphasized for PEAR
-	* PHPUC is on sg1 for testing with multiple PHP versions	+	* phpUnderControl is planned for sg1 for testing with multiple PHP versions

	=== Attracting New Developers ===		=== Attracting New Developers ===

migration

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

2010/10/05 10:24		current
Line 31:		Line 31:
	* <del>[[pear:packages:Event_Dispatcher]]</del> (unmaintained, new release, doconnor)		* <del>[[pear:packages:Event_Dispatcher]]</del> (unmaintained, new release, doconnor)
	* [[pear:packages:File_DICOM]]		* [[pear:packages:File_DICOM]]
-	* [[pear:packages:File_DNS]]	+	* <del>[[pear:packages:File_DNS]]</del>
	* [[pear:packages:File_Find]]		* [[pear:packages:File_Find]]
	* [[pear:packages:File_Fstab]]		* [[pear:packages:File_Fstab]]
Line 46:		Line 46:
	* [[pear:packages:HTML_Safe]]		* [[pear:packages:HTML_Safe]]
	* [[pear:packages:HTML_Select]]		* [[pear:packages:HTML_Select]]
-	* [[pear:packages:HTML_Select_Common]]	+	* <del>[[pear:packages:HTML_Select_Common]]</del>
	* <del>[[pear:packages:HTML_Table_Matrix]]</del> (new release)		* <del>[[pear:packages:HTML_Table_Matrix]]</del> (new release)
	* [[pear:packages:HTML_Template_Xipe]]		* [[pear:packages:HTML_Template_Xipe]]
	* [[pear:packages:HTTP_Header]]		* [[pear:packages:HTTP_Header]]
-	* [[pear:packages:HTTP_Server]]	+	* <del>[[pear:packages:HTTP_Server]]</del>
	* [[pear:packages:HTTP_SessionServer]]		* [[pear:packages:HTTP_SessionServer]]
	* <del>[[pear:packages:HTTP_Upload]]</del> (new release)		* <del>[[pear:packages:HTTP_Upload]]</del> (new release)
Line 75:		Line 75:
	* [[pear:packages:Math_Finance]]		* [[pear:packages:Math_Finance]]
	* [[pear:packages:Math_Histogram]]		* [[pear:packages:Math_Histogram]]
-	* [[pear:packages:Math_Integer]]	+	* <del>[[pear:packages:Math_Integer]]</del>
	* <del>[[pear:packages:Math_Matrix]]</del>		* <del>[[pear:packages:Math_Matrix]]</del>
	* [[pear:packages:Math_Polynomial]]		* [[pear:packages:Math_Polynomial]]

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_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 =====

2008-08-02

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

2026/09/01 07:02	current
Line 1:	Line 1:
	+	=== Who's running it? ===
	+	Daniel ([[doconnor]])
	+
	+	Chuck ([[ashnazg]])
	+
	+	=== When ===
	+	August 2nd, 3rd in #pear-bugs on irc.efnet.org
	+
	+	See http://www.google.com/calendar/embed?src=rslkppoio4rtq6nm7b6fptclfo%40group.calendar.google.com
	+
	+	=== What are we doing ===
	+	* writing tests for MDB2_Schema bugs (particularly those with patches);
	+	* looking at [http://pear.cweiske.de/overview.htm broken tests in packages]
	+
	+	A detailed breakdown of several items is included here -- http://article.gmane.org/gmane.comp.php.pear.qa/3397
	+
	+	See also: http://clockwerx.blogspot.com/2008/08/pear-bug-day-august-2nd-3rd.html
	+
	+	=== Misc other open items ===
	+	* Bugs with Patches (http://news.php.net/php.pear.dev/50418)
	+	* I18N_UnicodeString (http://news.php.net/php.pear.dev/50419)
	+
	+	=== Done ===
	+	* Find a new owner for Services_Trackback - (taken by [[doconnor]])
	+	* Validate_HU (http://news.php.net/php.pear.dev/50420) - (done by [[doconnor]] and [[bbieber]])
	+	* Check out bugs in SOAP marked for feedback from previous triage ([[Bug Triage Day 2008 07 13]]) - (done by [[doconnor]])
	+	* last parts of licensing for XML related packages - (done by [[helgi]] for [[ashnazg]])
	+	* completed some (as yet uncommitted) work on relicensing and package.xml v2 for XML_FOAF and XML_DTD - ([[ashnazg]])
	+
	+

policy

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

2008/11/24 13:30		current
Line 63:		Line 63:
	Package maintainers can also grant QA the rights to make a releases for their packages.		Package maintainers can also grant QA the rights to make a releases for their packages.

-	==== pearweb QA subsection ====

-	It seems that there is a lack of QA material in the manual that people agree on and there is also need to make it move visible for people so they will actually follow those rules/guidelines. The QA team will therefore get its own QA subsection in the manual and will have control over it just like package maintainer controls package related docs in the manual. The QA team also gets its own subsection on pearweb so people can more easily access QA material which is too dynamic or just related to the QA team own internal documentation purposes. There the QA will, for example, publish their latest decisions. Furthermore here the QA team will be able to provide interfaces to QA team services. For example, here the QA team could offer an interface for maintainers to configure the access rights they want to grant the QA. Finally the core QA team can add QA related notes to each package homepage to communicate QA related information to the user base.

	==== Approving first stable release ====		==== Approving first stable release ====

20070513

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

2008/11/09 03:03		current
Line 63:		Line 63:
	* Why so many dead proposals?		* Why so many dead proposals?
	* Some sort of Design Guide to go along with coding standards		* Some sort of Design Guide to go along with coding standards
		+
		+	===== Minutes =====
		+	These are the minutes from the May 13th PEAR Group meeting, if you have any questions feel free to send us an email (pear-group at php.net).
		+
		+	These minutes will be posted on the pear website at a latter date.
		+	-josh
		+	--------
		+
		+	===Attending===
		+
		+	* Arnaud Limbourg (arnaud)
		+	* Christian Weiske (cweiske)
		+	* Helgi Pormar (helgi)
		+	* Joshua Eichorn (jeichorn)
		+	* Lukas Smith (lsmith)
		+
		+	* Pear President Greg Beaver (cellog)
		+
		+	===Not Attending===
		+	* David Coallier (davidc)
		+	* Martin Jansen (mj)
		+
		+
		+	arnaud and lsmith left the meeting after the first hour
		+	cellog arrived 2 hours into the meeting
		+
		+	==Discussion==
		+
		+	Agenda for meeting is at: [[MeetingAgenda20070513]]
		+
		+	===Making decisions (non-policy)===
		+	Decisions are made by consensus (http://en.wikipedia.org/wiki/Consensus), any member can call for a vote if they disagree, voting has to be seconded
		+	If the entire pear group is available in a meeting voting can be done during the meeting otherwise an email vote is done
		+	Email votes should be a minmum of 7 days (or until all votes are cast) with sponsor of vote having the ability to set a longer time
		+	Email votes should be managed by any PEAR Group momber other then the membe rhwo called for the vote
		+	All Votes are final
		+
		+	Community notification will be on a case by case basis depending on the importance of the decision, with a minimum of an email to pear-dev
		+	A pear group member can call for a pear group vote to decide an issue by full pear election
		+
		+	====action items====
		+	* jeichorn - post this wording to the group for review
		+	* helgi - find a place on the website for items like this
		+
		+	===Community Notification, increasing transparency===
		+	Minutes will be posted from each meeting to a new section of the website with notifications to pear-dev and website front page
		+
		+	====action items====
		+	* arnaud - sending current thoughts to the rest of the pear group and making sure everyone else is fine with our solution
		+	* helgi - creating a new section on the website to post minutes too
		+	* jeichorn - post minutes from this meeting
		+
		+	===Vice President===
		+	candidates:
		+	* jeichorn
		+
		+	====action items====
		+	* postponing until after the runoff election to give winner a chance to be a candidate if they want
		+
		+	===Meeting Schedule===
		+	Meet every 2 weeks, need at least 3 members present to have a meeting
		+
		+	====action items====
		+	* helgi - schedule another meeting next week
		+
		+	===Constitution updates===
		+	Cover pear group tie for last position runoff
		+	Cover winning president less then 50% of votes
		+	Schedule election on new wording within a month
		+
		+	====action items====
		+	* cweiske will work on the language of the amendment
		+
		+	===Defining Collectives===
		+	Goal is for each collective to have at least 5 packages
		+	Review with pear group, and then entire community
		+	http://wiki.bluga.net/pear/collectives
		+	We will need to create a guide to help collectives get started
		+
		+	====action items====
		+	* jeichorn- send out url and ask for feedback
		+	* jeichorn- put back on agenda for next meeting
		+
		+	===Managing ongoing tasks===
		+	Were just going to leave this to whoever has time, we seem to be covering things well right now
		+
		+	====action items====
		+	* helgi - add a feature request for a cron check on limbo account approvals http://pear.php.net/bugs/bug.php?id=11026
		+
		+	===RFC Process===
		+	http://wiki.bluga.net/pear/rfc
		+	Working off current proposal
		+	Need to look at when to do a full pear vote
		+
		+	====action items====
		+	* jeichorn - get review from rest of the pear group
		+	* cweiske - create RFC section of the manual
		+
		+	Skip Items #9 to #11 on agenda
		+
		+	===Licensing in general===
		+	were not going to push any license on the approved list, but we will discourage the php license on none extension code
		+	recommendations about handling multiple copyright owners on code, and license compatibility would be good
		+	recommend GFDL for the manual
		+
		+	====action items====
		+	* cellog - search for legal advice to help review current licenses
		+
		+	===Mozilla Code and the MPL===
		+	We don't want another license in PEAR it's hard enough as it stands
		+
		+	====action items====
		+	* cellog - contact and mozilla and work out their concerns
		+	* jeichorn - find original pear-dev email
		+
		+	===Review Suggestions===
		+	Need to cover more, with the rest of the group
		+	spent some time covering a new include proposal from cellog for pear2 that would solve include_path concerns
		+
		+	Prop Summary:
		+	1 file per package that includes all its code
		+	Support autoload for people who want that
		+	PEAR2 provides an autoload class
		+
		+	====action items====
		+	* jeichorn - make sure all of pear group has read the comments
		+
		+	All other items on the Agenda were moved to the next meeting
		+
		+	===General Action Items===
		+	* jeichorn - start agenda for the next meeting
		+	* jeichorn - get minutes approved and published on pear-dev
		+

20080622

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

2008/11/09 03:07		current
Line 14:		Line 14:
	* Plan for removing package v1		* Plan for removing package v1
	* Bug Triage Updates/Plan		* Bug Triage Updates/Plan
		+
		+	===== Minutes =====
		+
		+	==== Attendees ====
		+	* Greg Beaver [Past President] ([[cellog]])
		+	* Christian Weiske ([[cweiske]])
		+	* Chuck Burgess ([[ashnazg]])
		+	* Travis Swicegood ([[tswicegood]])
		+	* Brett Bieber ([[saltybeagle]])
		+	* Josh Eichorn ([[jeichorn]])
		+	* Joe Stump ([[jstump]])
		+	* David Coallier ([[davidc]])
		+
		+	==== Topics ====
		+
		+	Greg requested a past-president summary.
		+
		+	===Past President Summary===
		+
		+	* Congrats to new people
		+	* Limited Nominations/Voting as a sign that current PEAR devs are content
		+	* Volume of proposals has risen = thanks to the old people
		+	* Number of bugs is rising, despite declining new bug reports
		+	* Talk of PEAR2 is encouraging new devs and could be holding off development of old packages
		+	* Yet unresolved - how collectives will work/look.
		+	* A few constitutional amendments that were informally proposed by the old group - need to be approved by referendum.
		+	* Important for president to maintain relations with PHP internals
		+	* Important for the president to identify the individuals who have the most influence over PHP internals issues that affect PEAR
		+
		+	Greg recommended:
		+
		+	* Keep tabs on the stats
		+	* Brainstorm ways of improving retention if we are losing people
		+	* Keep attendance up at conferences for face-to-face
		+
		+
		+	=== Administrative ===
		+	* [[saltybeagele\|Brett]] will take meeting minutes
		+	* [[helgi\|Helgi]] will update pearweb index
		+	* [[jeichorn\|Josh]] granted access to group members to the PEAR blog
		+	* [[cweiske\|Christian]] granted pear.group karma
		+
		+	=== Conference Meetup ===
		+
		+	* Group will try and have a face to face meeting, PHP Appalachia in the USA, another in Europe if possible.
		+	* Christian will try and suggest a meeting in Canada or Europe, FOWA was suggested, which is in London this year early Oct.
		+
		+	=== Vice President was voted on ===
		+	* 6 votes for [[cweiske\|Christian]]
		+
		+	=== PEARDOC DB4=>DB5 conversion ===
		+	peardoc upgrade is planned for Next Week, June 30th - July 4th, Christian and Brett will take the lead on this and get Rudy from GSoC's code running and upgrade peardoc - solicit help from pear-dev - We WILL NOT Branch! A freeze will be announced on the pear-doc list
		+
		+	===Bug Triage Updates/Plan===
		+	Once every two months?
		+	Chuck will assist in bug triage updates on the wiki, highlight agenda to be sent to the list, josh suggests a post on the blog and pear-dev announcements for each event.
		+
		+	===Plan for removing package v1===
		+	Version bump?
		+	* Chuck +1
		+	* Christian +1
		+	* Travis +1
		+	* Josh +1
		+	* Brett +1
		+	* Joe +1
		+
		+	Try and contact developers first to upgrade their package.xml to version 2. Brett will draft an email to be sent to developers of package v1 packages.
		+
		+	====Next meeting time/date====
		+	Christian suggested meetings should not be held by a hard date, adjust meetings by amount of work to be done.
		+
		+	[[twsicegood\|Travis]] suggested a maximum/limit of time to ensure meetings happen on some schedule
		+
		+	The next meeting will be July 13th, same time 5pm GMT.
		+
		+	==== Action Items ====
		+
		+	* [[davidc\|David]] will email systems and get pear-group@ alias updated. - Done
		+	* [[davidc\|David]] plans to post a introductory post on the president's blog - Done
		+	* [[ashnazg\|Chuck]] will email Helgi about updates to the Calendar of events
		+	* [[ashnazg\|Chuck]] will send notices regarding upcoming bug triage events
		+	* [[saltybeagle\|Brett]] will draft an email to developers of package v1 packages, announcing the update.

controversial_changes

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

2026/09/01 07:02	current
Line 1:	Line 1:
	+	====== Controversial Changes to PEAR2 Standards ======
	+	See [[pear:rfc:pear2_standards]]
	+
	+	====== Summary ======
	+
	+	===== Information =====
	+
	+	==== Document Information ====
	+	* Title: PEAR2 Coding Standards Controversial Changes
	+	* Version: 0.4.0
	+	* Status: Draft
	+	* Type: Standards
	+	* Last updated: September 3rd, 2007
	+
	+	==== Author(s) Information ====
	+	* Name: Gregory Beaver
	+	* Email: cellog@php.net
	+
	+	==== Legal Information ====
	+
	+	* This proposal is under CC-By-Sharealike ([http://creativecommons.org/licenses/by-sa/3.0/]) licensing.
	+
	+	==== Discussion List ====
	+	* Mailing List: http://news.php.net/php.pear.dev
	+
	+	===== Introduction =====
	+
	+	This document itemizes changes to the coding standards that refer to loading of external files containing classes.
	+
	+	These have been extracted from the general [[PEAR2 Standards]].
	+
	+	Documenting the location of external classes (classes not contained within a file)
	+	is an important problem to solve within PEAR2. There are two kinds of external classes:
	+
	+	- those contained within the current package
	+	- external package dependencies
	+
	+	This recommendation defines how to handle both
	+
	+	===== Summary =====
	+
	+	This document describes the coding standards and coding conventions for the new PEAR2 repository.
	+
	+	===== Approach & Requirements =====
	+
	+	Packages that wish to be accepted into the PEAR2 repository must conform to these standards
	+
	+	===== Definition =====
	+
	+
	+	==== Handling dependencies ====
	+
	+	File dependencies (required and optional) should be registered at the top of the file using /** */ documentation comments as well as with full import statements:
	+
	+	<?php
	+	/**
	+	* My Package
	+	* @uses PEAR2::SomeotherPackage in PEAR2/SomeotherPackage.php (package PEAR2::Someotherpackage must be installed)
	+	* @uses PEAR2::PackageName::Exception in PEAR2/PackageName/Exception.php
	+	* @package PEAR2_PackageName
	+	*/
	+	namespace PEAR2;
	+	use ::PEAR2::PackageName::Exception as Exception;
	+	use ::PEAR2::SomeotherPackage as PEAR2::SomeotherPackage;
	+	?>
	+
	+	=== Requirement ===
	+	No Exceptions to this rule

file_bittorrent

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

2011/04/06 10:59		current
Line 25:		Line 25:
	* [[http://pear.php.net/package/File_Bittorrent2\|Visit the official package homepage]]		* [[http://pear.php.net/package/File_Bittorrent2\|Visit the official package homepage]]
	* [[http://pear.php.net\|PEAR Homepage]]		* [[http://pear.php.net\|PEAR Homepage]]
-	* [[http://www.bittorrent.com<Bittorrent Homepage]]	+	* [[http://www.bittorrent.com\|Bittorrent Homepage]]

rfc_policy

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

2026/09/01 07:02	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

20090107

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

2026/09/01 07:02	current
Line 1:	Line 1:
	+	====== PEAR Group Meeting 7th January 2009 ======
	+	* Review the open RFCs.
	+
	+	===== Minutes =====
	+	==== Attendees ====
	+	* Brett Bieber ([[saltybeagle]])
	+	* Josh Eichorn ([[jeichorn]])
	+	* Christian Weiske ([[cweiske]])
	+	* David Coallier ([[cpunerd]])
	+	* Chuck Burgess ([[ashnazg]])
	+
	+	==== Topics ====
	+	Review the three RFCs.
	+
	+	=== Class Naming RFC ===
	+	Todo:
	+	* Add examples
	+	* Solicit a 2nd author
	+
	+	=== Exception RFC ===
	+	Todo:
	+	* Check with Joe Stump
	+	* Solicit a 2nd author
	+
	+	=== PEAR2 Package Naming RFC ===
	+	Todo:
	+	* Handle comments from the discussions tab.
	+
	+	=== Add doc.php.net as a default channel ===
	+	The group voted on adding the PEAR channel maintained by the PHP
	+	documentation team at doc.php.net to the list of default channels.
	+	Brett +1
	+	Chuck +1
	+	Josh +1
	+	Christian +1
	+
	+	Vote passes. The PEAR installer and Pyrus need to be modified to add doc.php.net as a default channel.
	+
	+	==== Action Items ====
	+	* Brett will send out the minutes
	+	* Brett will look at adding doc.php.net to the PEAR installer

image_qrcode

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

2026/09/01 07:02	current
Line 1:	Line 1:
	+	==== Usage ====
	+	Generating QRCodes

	+	<code>
	+	$qrcode = new Image_QRCode();
	+	$qrcode->makeCode('http://pear.php.net/');
	+	</code>
	+
	+	The second parameter of [[http://pear.php.net/package/Image_QRCode/docs/latest/Image_QRCode/Image_QRCode.html#methodmakeCode\|makeCode()]] allows runtime configuration using an options array.
	+
	+	\| Name \| Type \| Description \|
	+	\| image_type \| string \| Defines the return image type (from 'jpeg', or 'png'). Default is PNG format \|
	+	\| output_type \| string \| Sets what to do once the code has been generated ('display' or 'return'). Default is to display the image, complete with headers. \|
	+	\| error_correct \| string \| Sets the error correction level. One of: L: 7% error level M: 15% error level Q: 25% error level H: 30% error level \|
	+	\| module_size \| integer \| Sets the default module size Defaults are PNG: 4, JPEG: 8 \|
	+
	+	Generating JPEG image with best error correction
	+	<code>
	+	require_once 'Image/QRCode.php';
	+
	+	$qrcode = new Image_QRCode();
	+	$qrcode->makeCode('http://pear.php.net/', array(
	+	'image_type' => 'jpeg',<br>
	+	'error_correct' => 'H', // 30% error correction<br>
	+	));
	+	</code>

pear2_package_wishlist

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

2008/11/09 03:17		current
Line 3:		Line 3:

	* Light-Weight PDO Wrapper (adding utility functions, possibly some basic abstraction)		* Light-Weight PDO Wrapper (adding utility functions, possibly some basic abstraction)
-	* HTML to Text Converter (see [http://php-html.sourceforge.net/html2text.php\|HTML2Text ])	+	* HTML to Text Converter (see [[http://php-html.sourceforge.net/html2text.php\|HTML2Text]])
	* Router		* Router
-	* Generalized Template Package (see [http://svn.pear.php.net/wsvn/PEARSVN/sandbox/template_engine/?rev=0&sc=0\|pear2::template_engine])	+	* Generalized Template Package (see [[http://svn.pear.php.net/wsvn/PEARSVN/sandbox/template_engine/?rev=0&sc=0\|pear2::template_engine]])
	* Rest Server Package		* Rest Server Package
	* Rest/Webservices Base class		* Rest/Webservices Base class
Line 12:		Line 12:
	* Validation		* Validation
	* CSRF protection		* CSRF protection
-	* Mail packages Sending/Imap (see [http://pear.php.net/package/Mail_IMAPv2\|IMAPv2])	+	* Mail packages Sending/Imap (see [[http://pear.php.net/package/Mail_IMAPv2\|IMAPv2]])

20080803

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

2008/11/09 03:12		current
Line 3:		Line 3:
	Items:		Items:
	* Do we need to clean up/out lingering proposals in PEPr? As per this RFC - http://pear.php.net/pepr/pepr-proposal-show.php?id=188		* Do we need to clean up/out lingering proposals in PEPr? As per this RFC - http://pear.php.net/pepr/pepr-proposal-show.php?id=188
		+
		+	===== Minutes =====
		+	==== Attendees ====
		+
		+	* Brett ([[saltybeagle]])
		+	* Josh ([[jeichorn]])
		+	* Chuck ([[ashnazg]])
		+	* Travis ([[tswicegood]])
		+	* Joe ([[jstump]])
		+
		+	Josh called the meeting to order.
		+
		+	==== Topics ====
		+
		+	=== Naming Recommendations ===
		+
		+	Chuck discussed his upcoming RFC for class, abstract, and interface naming.
		+	It was discussed that the RFC should seek a recommendation for naming
		+	classes, specifically abstract and interface. FooAbstract may be
		+	allowed in some circumstances but FooInterface should be avoided.
		+
		+	Chuck will continue work on this RFC.
		+
		+	=== PEPr cleanup ===
		+
		+	Chuck brought up the issue of PEPr cleanup -
		+
		+	The group agreed that the QA proposal for Orphan PEPr proposals should
		+	be followed, starting with the 'initial cleanup' phase.
		+
		+	http://pear.php.net/pepr/pepr-proposal-show.php?id=188
		+
		+	The next meeting will be August 24th, 2008.
		+
		+	==== Action Items ====
		+
		+
		+	* [[saltybeagle\|Brett]] will send out the minutes
		+	* [[tswicegood\|Travis]] will check in to MSDN accounts for pear group
		+

download

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

2026/09/01 07:02	current
Line 1:	Line 1:
	+	====== Downloading File_Bittorrent ======
	+	===== File_Bittorrent2 =====
	+	==== via PEAR ====
	+	Use the CLI or Web installer to download and install this package automatically.
	+	<code>$ pear install File_Bittorrent2</code>
	+	The Package can be downloaded here:\\
	+	http://pear.php.net/package/File_Bittorrent2/download
	+	==== via SVN ====
	+	The latest development version is located at\\
	+	http://svn.php.net/repository/pear/packages/File_Bittorrent2/trunk/
	+	===== File_Bittorrent =====
	+	==== via PEAR ====
	+	Use the CLI or Web installer to download and install this package automatically.
	+	<code>$ pear install File_Bittorrent</code>
	+	The Package can be downloaded here:\\
	+	http://pear.php.net/package/File_Bittorrent/download
	+	==== via SVN ====
	+	The latest development version is located at\\
	+	http://svn.php.net/repository/pear/packages/File_Bittorrent/trunk/

backport_to_pear

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

2026/09/01 07:02	current
Line 1:	Line 1:
	+	PEAR2 backported to PEAR(1)

	+	Two major changes -
	+	- supporting the 'paranoia' option in PEAR. - [[pear:rfc:pear2_versioning_standard_revision]]
	+	- allowing packages using pear2 standards to be released on pear.php.net
	+
	+	Through the use of the 'paranoia' option in Pyrus which prevents BC breaking changes to be upgraded, packages in PEAR1 could have BC breaking changes without affecting existing installations, as long as they require pyrus as the pearinstaller (IE: minimum pearinstaller=2.0.0a1)
	+
	+	This means we could modify the PEAR2 standards, and make them work for the existing PEAR packages, and allow them to be upgraded at will.
	+
	+	=== Pros: ===
	+	* Keeps pear.php.net running
	+	* New code behind the website
	+	* No confusion over PEAR and PEAR2, people won't see it as abandoning the current code base
	+
	+	=== Cons: ===
	+
	+	* Potential name conflicts
	+
	+	=== Changes Required: ===
	+
	+	* Change namespace to PEAR\ within the PEAR2 standards code
	+	* Documentation has to be able to reflect v1 and v2 properly if they are wildly different (PHP 4 code vs. PHP 5.3+ code with other standards)

20080824

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

2008/11/09 04:25		current
Line 13:		Line 13:

	===== Minutes =====		===== Minutes =====
-	[[Category: Meeting Minutes]]
-
-	PEAR Group Aug 24, 2008
-	2008-08-24
-	Meeting Minutes

	==== Attendees ====		==== Attendees ====

mdb2_schema

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

2008/11/30 03:08		current
Line 10:		Line 10:
	===== Maintainer =====		===== Maintainer =====
	* Igor Feghali [Wishlist] (lead)		* Igor Feghali [Wishlist] (lead)
-	* Lars Olesen (helper, inactive)
	* Lukas Smith [Wishlist] (lead, inactive)		* Lukas Smith [Wishlist] (lead, inactive)
-	* Andrew Hill (contributor, inactive)
	* Helgi Þormar Þorbjörnsson [Wishlist] (lead, inactive)		* Helgi Þormar Þorbjörnsson [Wishlist] (lead, inactive)
-	* Ali Fazelzadeh (contributor, inactive)

	===== Overview of Code =====		===== Overview of Code =====

services_amazon

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

2026/09/01 07:02	current
Line 1:	Line 1:
	+	====== Services_Amazon ======
	+
	+	===== Deprecated Functionality - how to migrate =====
	+	Please use Services_Amazon instead of Services_AmazonECS4.
	+
	+	Deprecated code will not be processed after August 15:
	+	require_once 'Services/AmazonECS4.php';
	+	$amazon = new Services_AmazonECS4(YOUR_ACCESS_KEY_ID);
	+	$amazon->ItemSearch(...);
	+
	+	New code works fine:
	+	require_once 'Services/Amazon.php';
	+	$amazon = new Services_Amazon(YOUR_ACCESS_KEY_ID, YOUR_SECRET_ACCESS_KEY);
	+	$amazon->ItemSearch(...); // <= backward compatible with Services_AmazonECS4
	+

spreadsheet_excel_writer

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

2009/08/03 13:45		current
Line 6:		Line 6:
	===== Alternatives =====		===== Alternatives =====
	* [[pear:packages:opendocument]]		* [[pear:packages:opendocument]]
		+
		+	===== Who uses it? =====
		+	It's pretty darned widely used, because it's unique and mostly works.
		+
		+	We see a fair number of relatively inexperienced developers who make use of it (rather than simple alternatives, like a CSV), and a smattering of more determined developers who contribute back fixes.

	===== The original =====		===== The original =====
Line 39:		Line 44:

	The problem with this is the fragility involved.		The problem with this is the fragility involved.
		+
		+	===== How do we tell if patches are any good? =====
		+	Well, this is a tricky one.
		+
		+	The majority of the users are very enthusiastic, but there's not much in the way of testing you can do on the changes; nor does casual review really help.
		+

pear2.php.net

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

2011/05/06 17:40		current
Line 15:		Line 15:
	* [[pear/rfc/PEAR Package Release Protocol]]		* [[pear/rfc/PEAR Package Release Protocol]]
	* PhD renderer for PEAR2 manual		* PhD renderer for PEAR2 manual
-	* Rendering of package API documentation via PHPDocumentor	+	* Rendering of package API documentation via DocBlox
-	- Bug Tracker	+	- <del>Bug Tracker</del> (implemented via GitHub)
	- User Management		- User Management
	- Package Proposals and Releases		- Package Proposals and Releases
	- Channel Aggregator		- Channel Aggregator

20070520

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

2026/09/01 07:02	current
Line 1:	Line 1:
	+	====== PEAR Group Meeting Sunday 20th May 2007 ======
	+
	+	Looks like the meeting will be on Sunday the 20th 7pm UTC, check the pear clock for your timezone
	+
	+	http://clock.bluga.net/pear.php
	+
	+	You should all watch this before the meeting: http://video.google.com/videoplay?docid=-4216011961522818645
	+
	+	* Review last weeks action items
	+	* Review decision making process http://wiki.bluga.net/pear/decision_making?
	+	* Vote on vice president
	+	* Schedule some future meetings
	+	* Defining Collectives
	+	* Review RFC Proposal ((rfc))
	+	* Getting more people involved
	+	* Mentor Program
	+	* Reduction of adversarial attitude to new proposals
	+	* Community Outreach program (phpwomen, phpgtk, users groups)
	+	* PEAR Evangelist(s) who reach out to other libraries/frameworks/communities to try and foster PEAR use within their projects
	+	* Overall attitude and behaviors of current developers
	+	* Figuring out what people think of PEAR (and how we can make that positive)
	+	* I don't think its all great thoughts
	+	* Lots of people are turned off by the installer21
	+	* We have lots of positive aspects too, how do we focus on them
	+	* Website organization/updates
	+	* get users' feedback. A lot of people use pear or even write articles yet very little exists to show this material on the site
	+	* Review Suggestions from:
	+	* http://blog.joshuaeichorn.com/archives/2007/05/03/how-would-you-improve-pear/
	+	* http://www.sitepoint.com/blogs/2004/04/12/more-debate-on-pear/
	+	* Dealing with unmaintained/deprecated/dead packages
	+	* Also dead pepr proposals
	+	* Thoughts on PEAR2
	+	* Creating some sort of roadmap to move us forward
	+	* Creation of working groups to move projects forward
	+	* Reviewing RFCs
	+	* Creating a mentoring program
	+	* Community outreach
	+	* Evangelists (Driven by Greg?)
	+	* Success Stories
	+	* porting peardoc to livedoc (mainly helping the php effort, has to be this summer, phillip has more details)
	+	* Website Look/Feel Redesign/Update
	+	* Some kind of news effort, weekly/bi-weekly/monthly, perhaps working with Steph, this would only be couple of people that would over see the project and other people should be able to contribute easily
	+	* Good way to get outside people more in sync what's happening in the community
	+	* PEAR's week of code (David)
	+	* Idea
	+	* Sponsorship
	+	* Priorities
	+	* Tools
	+	* how to keep track of all that (wiki, trac, other: basecamp, etc) ?
	+	* have a serendipity install or other to manage publishing news on the site (committing to cvs and updating the site is not the greatest thing). We can also have a PEAR official blog.
	+	* Some sort of Design Guide to go along with coding standards, this would be a more in depth guide covering some common patterns guidelines for class/method sizes etc, would also be non binding just a guide, would need lots of community help

20070603

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

2026/09/01 07:02	current
Line 1:	Line 1:
	+	====== PEAR Group Meeting Sunday 3rd June 20077 ======
	+	Looks like the meeting will be on Sunday June 3rd 7pm UTC, check the pear clock for your timezone
	+
	+	http://clock.bluga.net/pear.php
	+
	+	You should all watch this before the meeting: http://video.google.com/videoplay?docid=-4216011961522818645
	+
	+	* Review last weeks action items
	+	* Schedule Next meeting
	+	* Vote on Vice President
	+	* Accept constitution extension. This should be added to the constitution on II Checks and balances:
	+	''PEAR Group and president elections take one month.
	+	In case of a tie, a runoff election between
	+	the tied competitors will be held. The runoff election will commence 10
	+	days after the previous election concludes, and will last 10 days.''
	+	* Review Collective List
	+	* Vote on RFC
	+	* Review Suggestions from:
	+	* http://blog.joshuaeichorn.com/archives/2007/05/03/how-would-you-improve-pear/
	+	* http://www.sitepoint.com/blogs/2004/04/12/more-debate-on-pear/
	+	* Dealing with unmaintained/deprecated/dead packages
	+	* Also dead pepr proposals
	+	* Coding standards: How to deal with "{" after "class Foo" -> Current consensus is a newline, then {, but that's not written down
	+	* Thoughts on PEAR2
	+	* Creating some sort of roadmap to move us forward
	+	* Naming (branding) of new installer/repository (Pyrus/Peach? Pyrus/PEAR2? etc.)
	+	* Creation of working groups to move projects forward
	+	* Reviewing RFCs
	+	* Creating a mentoring program
	+	* Community outreach
	+	* Evangelists (Driven by Greg?)
	+	* Success Stories
	+	* porting peardoc to livedoc (mainly helping the php effort, has to be this summer, phillip has more details)
	+	* Website Look/Feel Redesign/Update
	+	* Some kind of news effort, weekly/bi-weekly/monthly, perhaps working with Steph, this would only be couple of people that would over see the project and other people should be able to contribute easily
	+	* Good way to get outside people more in sync what's happening in the community
	+	* PEAR's week of code (David)
	+	* Idea
	+	* Sponsorship
	+	* Priorities
	+	* Tools
	+	* how to keep track of all that (wiki, trac, other: basecamp, etc) ?
	+	* Wiki needs to accept pear logins, not require pear devs to register.
	+	* have a serendipity install or other to manage publishing news on the site (committing to cvs and updating the site is not the greatest thing). We can also have a PEAR official blog.
	+	* Some sort of Design Guide to go along with coding standards, this would be a more in depth guide covering some common patterns guidelines for class/method sizes etc, would also be non binding just a guide, would need lots of community help
	+	* Mission statement
	+	* have a wiki page with the mission statement (thread from october 2006 on pear-dev)

20080406

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

2026/09/01 07:02	current
Line 1:	Line 1:
	+	====== PEAR Group Meeting 6th April 2008 ======
	+
	+	===== Minutes =====
	+
	+	==== Attendees ====
	+	* Joshua Eichorn ([[jeichorn]])
	+	* Christian Weiske ([[cweiske]])
	+	* David Coallier ([[davidc]])
	+	* Arnaud Limbourg ([[arnaud]])
	+	* Martin Jansen ([[mj]])
	+
	+	==== Topics ====
	+	* PEAR2 Standards and Policies
	+	* PEAR2 website
	+	* PEAR2 svn ssh access
	+	* Extending PEAR2 svn access
	+	* Elections
	+	* Action Items
	+
	+
	+	=== PEAR2 Standards and Policies ===
	+	The standards seem to mainly be set, last topic outstanding is Namespace usage, waiting for a conclusion on [[pear-dev]]
	+
	+	=== PEAR2 Website ===
	+	Would be good to have a site ready for php\|tek, [[Helgi]] is working on it, visual differentiation from http://pear.php.net would be good
	+
	+	=== PEAR2 svn ssh access ===
	+	[[cweiske\|Christian]] and [[mj\|Marten]] will be given ssh access in the case that [[jeichorn\|Joshua]] isn't available and there is a [[pear2]] svn problem
	+
	+	=== Extending PEAR2 svn access ===
	+	* Agreed that giving more people access to the sandbox to start development would be good
	+	* Permissions management isn't complete, [[jeichorn\|Joshua]] to follow up with [[Helgi]]
	+
	+	=== Elections ===
	+	Last [[Pear-group]] elections were in April, time to start this years
	+	* [[mj\|Marten]] will send out a call for new people to run
	+
	+	==== Action Items ====
	+	* [[cweiske\|Christian]] will post last minutes on the wiki
	+	* [[jeichorn\|Joshua]] will send out a notification email
	+	* [[Arnaud]] will update [[pear2]] rules with external hosting decision from the last meeting

gsoc

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

2009/03/10 13:23		current
Line 1:		Line 1:
	===== PEAR Google Summer of Code Pages =====		===== PEAR Google Summer of Code Pages =====
		+

	* [[pear/gsoc/2009]]		* [[pear/gsoc/2009]]
		+
		+
		+	===== Planning =====
		+
		+	We made some experiences with GSoC and have some ideas to improve. Probably there will be a GSoC 2009 so let's collect all of the plans to improve:
		+
		+	* [[gsoc::planning_2009]] PHP GSoC 2009 Planning for a better GSoC

pyrus

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

2026/09/01 07:02	current
Line 1:	Line 1:
	+	Information tid bits about Pyrus. Roadmaps, todo lists, site maps etc. - Originally this information was on Google Wave until they gave up.
	+
	+	* [[pear:pear2:pyrus:sitemap\|Sitemap for pyrus.php.net]]
	+	* [[pear:pear2:pyrus:backport_to_pear\|Pyrus features to backport to PEAR]]
	+	* [[pear:pear2:pyrus:roadmap\|Roadmap for the Pyrus development]]

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,

20100117

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

2010/01/25 05:55		current
Line 20:		Line 20:
	The PEAR2 Incubator has been in discussion for two years. A brief summary of what it is:		The PEAR2 Incubator has been in discussion for two years. A brief summary of what it is:

-	The PEAR2 incubator is a channel in the PEAR umbrella that is easy to add packages to. The PEAR2 Incubator is intended as a channel for developers to get code in PEAR without first going through PEPr and with the easy option of later going through PEPr.	+	> The PEAR2 incubator is a channel in the PEAR umbrella that is easy to add packages to. The PEAR2 Incubator is intended as a channel for developers to get code in PEAR without first going through PEPr and with the easy option of later going through PEPr.

	== QA Of Incubator ==		== QA Of Incubator ==

sitemap

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

2026/09/01 07:02	current
Line 1:	Line 1:
	+	A potential sitemap for pyrus.php.net

	+	* Home
	+	* Downloads & Changelog
	+	* About/Documentation
	+	* Support
	+	* Developers/Development
	+	* Plugins
	+	* Generator (the bundle generator effectively)
	+

2011/08/24 06:29		current
Line 3:		Line 3:
	^ Current version: \| 0.2.0 (alpha) was released on 2009-07-28 \|		^ Current version: \| 0.2.0 (alpha) was released on 2009-07-28 \|
	^ Source repository: \| https://github.com/pear/OpenDocument \|		^ Source repository: \| https://github.com/pear/OpenDocument \|
-	^ Bug tracker: \| http://pear.php.net/bugs/search.php?cmd=display&package_name[]=OpenDocument \|	+	^ Bug tracker: \| [[http://pear.php.net/bugs/search.php?cmd=display&package_name[]=OpenDocument]] \|

	OpenDocument is a package to create, read and update [[http://en.wikipedia.org/wiki/OpenDocument\|Open Document Format]] files. ODF is an XML-based file format for office documents such as spreadsheets, charts, presentations and word processing documents, with a standardised specification as an //OASIS Committee Specification// ([[http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2.html\|v.1.2]]) and //ISO/IEC 26300:2006// (v.1.0 with v.1.1 currently a Draft Amendment). The former specification is the most recently updated, is publicly available, and is the one we're working from for this PEAR package.		OpenDocument is a package to create, read and update [[http://en.wikipedia.org/wiki/OpenDocument\|Open Document Format]] files. ODF is an XML-based file format for office documents such as spreadsheets, charts, presentations and word processing documents, with a standardised specification as an //OASIS Committee Specification// ([[http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2.html\|v.1.2]]) and //ISO/IEC 26300:2006// (v.1.0 with v.1.1 currently a Draft Amendment). The former specification is the most recently updated, is publicly available, and is the one we're working from for this PEAR package.