pear:group:meetingagenda:20070513

This is an old revision of the document!


Looks like the meeting will be on Sunday the 13th http://www.doodle.ch/dpgNgSFqcw87

http://clock.bluga.net/pear.php

http://video.google.com/videoplay?docid=-4216011961522818645

  • Document decision making process (regular day to day stuff, larger policy (RFC stuff further down the list)
  • Decided on a way to notifying the community of what were doing (meeting minutes etc)
    • Decide who is going to post this info (Vice President, rotating?)
  • Vote on vice president
  • Creating a meeting schedules
  • Plan for updating the constitution for handling ties (and many none majority winners for president)
  • Defining Collectives
  • How are we going to handle tasks like approving accounts
  • How to move forward with RFC (Setting policy, maybe we need a new name?)
    • Proposal Wiki page: 1)
    • Review Current RFCs
    • Website Updates
  • 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 installer
    • 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
  • Licensing in general (lots of push for only BSD on the lists) (I would consider bringing Lukas Feiler into this discussion if possible - david)
    • Consider LGPL as a way to push PEAR as the “free and always free” library without forcing users of the code to adopt an open-source license.
    • Talk about LGPL-CC
    • Documentation new license : GFDL (http://www.gnu.org/licenses/fdl.html)
  • Mozilla Licensing (lets get that code in PEAR)
  • Review Suggestions from:
  • Dealing with unmaintained/deprecated/dead packages
  • Thoughts on PEAR2
  • 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.
  • PEAR Roadmap
    • we can ask for volunteers to translate the constitution
  • Cleaning out PEPR
    • Why so many dead proposals?
  • Some sort of Design Guide to go along with coding standards
1)
rfc
pear/group/meetingagenda/20070513.1226199530.txt.gz · Last modified: 2017/09/22 13:28 (external edit)