PHP Wiki

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:24	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:24	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.