pear:group:meetingagenda:20090906

This is an old revision of the document!


PEAR Group Meeting 6th September 2009

Apologies: doconnor is on holiday

  1. PEAR test server - discussion, look at its role in the future of PEAR (doconnor, cweiske)
  2. Set goals for group for 2009 to 2010 (short, middle and long term)
  • Action Items from last meeting
    • New group members will catch up on content of RFC's before next meeting and will be ready to discuss or present changes.
    • Group will vote on PEAR2 policy and standards RFC's at beginning of next meeting.
    • Other RFC's will be discussed in detail during next meeting.

Goals for This Year

  • Short term
  • Mid term
    • stable PEAR2/Pyrus release
    • attracting new developers to PEAR2
  • Long term
    • get active maintainers of quality PEAR1 packages to port them to PEAR2

Minutes

Unresolved Issues from Last Year

  • Three outstanding RFC's are awaiting Group voting

Testing and Continuous Integration Server

  • agenda item was mostly skipped as Christian and Daniel are not present
  • QA needs to be emphasized for PEAR
  • phpUnderControl is planned for sg1 for testing with multiple PHP versions

Attracting New Developers

  • Community outreach via blogs, social networks, etc was suggested
    • PEAR needs mention on Facebook, Twitter, etc.
    • Group members' blogs should be on Planet PHP
    • Group members should post PEAR-related posts to the shared PEAR blog.
      • this will include meeting minutes, vote outcomes, security notices, etc.
  • The website was mentioned as a place where PEAR could improve its appearance to attract new developers. It was suggested that the website should include tutorials and screen-casts for new developers.
  • The members of the PEAR group should all use Pyrus and promote

its use to other developers.

  • High-quality packages with active developers will encourage other developers to use and contribute to PEAR.
  • Being friendly, timely and helpful to new developers will help retain and attract new developers. Recent technical issues caused some slow turn-around recently, but these issues have since been fixed.
    • Being quick to respond to new accounts and karma requests is important.
  • IRC support is being handled pretty well.
  • Action items
    • Bill will look into wrangling control of the pear and pear2 Twitter accounts.
    • Bill will set up a Twitter account for pearphp
    • Bill will ask if Digg has any design resources to give for the PEAR Website.
    • David will make sure Group will be given accounts on the PEAR blog
    • Group members will start using Pyrus and tell their developer friends how cool it is.

PEAR2

  • Brett and Greg (cellog) are the only two developers working on PEAR2--they may need some help.
    • website needs assistance in terms of development and design
  • PEAR2 cannot launch until at least PHP 5.3.1, but the website and bug-tracking infrastructure likely won't be ready by then anyway.
  • Marketing
    • Teaser posts on Pyrus features will increase interest in PEAR2.
    • Major marketing will be withheld until the stable launch of Pyrus.
  • Bug Manager
    • a functioning bug tracker is needed before PEAR2 can launch
    • some PHP internals developers want a global bug tracker for all PHP projects
    • PEAR2 developers want to build a stand-alone bug tracking package that could be used for PEAR2 and for other projects. (Bug Manager)
    • either of these goals will take some time
  • Action items
    • Bill will look into assisting Greg with the Bug Manager package
    • Christian will work on getting pearweb running on PHP 5.3.x to test the Bug Manager package with real-world data.

Next Meeting

  • 2009-09-06 at 14:00 UTC
  • Action items
    • Brett will post to pear-group with a potential new time. Possibly 2-3 hours earlier as Bill doesn't mind early mornings and Daniel is 16.5 hours away.
pear/group/meetingagenda/20090906.1252192889.txt.gz · Last modified: 2017/09/22 13:28 (external edit)