PHP Wiki

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]]

2008-10-25

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

2026/04/23 12:14	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.
	+
	+

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.
		+

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

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

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

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

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]]

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

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

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>

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
		+

20070520

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

2026/04/23 12:14	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/04/23 12:14	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)

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.

2008-05-03

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

2026/04/23 12:14	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 ====

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.