May 13th PEAR Group Meeting Minutes
| From: | Joshua Eichorn | Date: | Mon, 14 May 2007 23:07:43 +0000 |
| Subject: | May 13th PEAR Group Meeting Minutes | ||
| Groups: | php.pear.dev | ||
| Request: | Send a blank email to pear-dev+get-46759@lists.php.net to get a copy of this message | ||
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
--------
May 13th PEAR Group Meeting
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
Agenda for meeting is at: http://wiki.bluga.net/index.php?area=pear&page=agenda-may-07
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 - 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
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 - 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