on the RFC policy - Re: [PEAR-DEV] PEAR Group June 24 2007 Meeting Minutes

Hi guys, The overall process and doc looks pretty good to me as far as I can judge. I have a few comments. I don't clearly understand the following sentence in the Summary: "vote on actual language for all official PEAR policy that affects more than 1 collective". Not sure what you actually mean by "language" here. What is a "collective"? Please, note that English is not my mother tongue. Everybody should be able to understand those things. Maybe it is just me though :-) The vote by just the PEAR Group folks, if I understand correctly, seems a bit restrictive to me. I do appreciate that there is a call for review by all. But it is just a handful of people that finally make the call for hundreds (?) of people. You may want to include the top 20 (?) most active PEAR developers, based on simple and verifiable criteria, e.g. those that raise/fix the most bugs, release/enhance the most packages... Makes sense? Regards, MC ----- Original Message ---- From: Joshua Eichorn <josh@bluga.net> To: PEAR Announce <pear-dev@lists.php.net> Sent: Thursday, July 5, 2007 10:18:47 PM Subject: [PEAR-DEV] PEAR Group June 24 2007 Meeting Minutes Here are the meeting minutes from the PEAR Group's June 24th meeting. Sorry about taking so long to get them posted. -josh ---- June 24th PEAR Group Meeting 7PM UTC to 8:15 UTC Meeting took place over IRC Attending Christian Weiske (cweiske) Helgi Þormar (helgi) Joshua Eichorn (jeichorn) PEAR President - Greg Beaver (cellog) Not Attending Martin Jansen (mj) Paul M Jones (pmjones) Arnaud Limbourg (arnaud) David Coallier (davidc) Pear Mission Statement PEAR's mission is to provide reusable components, lead innovation in PHP, provide best practices for PHP development and educate developers. Action Items: cweiske: handle email review and voting on mission statement Last Weeks tasks http://wiki.pear.php.net/index.php/TaskList PEAR2 Infrastructure Review Wiki + pear auth, not working right, hopefully davidc can get it solved next week SVN basics are inplace, next steps are adding an api so pearweb can manage it PEAR services will be moving to a new faster server in the next few weeks PEAR2 Decisions SVN location is going to be: http://svn.pear.php.net/PEAR2/{package_name} Action Items: cweiske: run and email vote to make sure everyone agrees Vote on RFC_Policy http://wiki.pear.php.net/index.php/RFC_Policy Action Items: cweiske: run an email vote PEAR2 Standards RFC http://wiki.pear.php.net/index.php/PEAR2_Coding_Standards Need to decide on location of php code in the SVN repo Action Items: cweiske: run an email vote Design Guide Fits into ears best practices goals, big project, maybe start something on the wiki Welcome Email New user process for pear2 would be: 1) users proposes a package 2) a mentor is assigned to the user to answer their questions and help tweak the package 3) user does a few alpha releases, then proposes moving to beta Mentor sends the welcome email Mini-FAQ will help new dev and mentor through first steps docs for package.xml, a quick how-to-use-the-roadmap-bugtracker to generate a first package.xml, locations of stuff (svn, mailing list archives etc) Action Items: cweiske: ask pear.dev what should be a on new developer faq Schedule Next Meeting Shooting for: 2007-07-08 -- PEAR Development Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php ____________________________________________________________________________________ Fussy? Opinionated? Impossible to please? Perfect. Join Yahoo!'s user panel and lay it on us. http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7