Re: priorities for PEAR project as a whole

--On September 27, 2006 5:06:30 PM -0400 David Coallier <davidc@php.net> wrote: > Well yes it is important to make the site good first, but we have to > establish what we need for the site first.. I mean, do we need a total new > architecture ? do we need only couples packages changing, we need to > establish some ground rules (ideas) my thoughts: we (the entire PEAR community and all of it's contributors) have to keep our efforts focused in three distinct areas 1) steering 2) infrastructure 3) development development - covers everything from proposing, maintaining, fixing and supporting(supporting the endusers) packages. The Pear-dev list serves people collaborating in this area. Infrastructure - work on the web site's features, management of mailing lists, overall coordination of efforts. Steering - things bigger than PackDev, or Infra. PEAR Group holds the reigns in this focus area. ---mental break :) I'll pitch some concrete tasks for thought: Let's split/extend the proposal system into "Package related" and "Infrastructure". As in: Completely seperate so people can subscribe to just proposals in one or the other. This will let us start proposing working on Infrastructure (eg, yacking about web site features/changes) without swamping the developers who are doing real work on real packages. Move this discussion to Pear-core which is dedicated to infrastructure. (Although I'm guessing the original meaning was the PHP code which makes PEAR work.)