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 ¹⁾
• 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