PEAR2 wiki document

Hi all, I've made some significant revisions to the wiki based on some of the complaints and a few exciting developments in the PHP language itself. The revised document is at http://wiki.pear.php.net/index.php/PEAR2_Standards As a reminder, PEAR2 is intended to be a giant leap forward, and so we're still feeling our way around in the darkness of possibility. Any proposed changes can be negotiated, although I hope that we can be more civil than in the last iteration which was a complete nightmare. This was due to an unfortunate combination of people being on vacation, incompletely thought-out ideas, and abject terror on the part of those who would be subjected to those ideas. I promise to focus on making the incomplete ideas work, and I trust you to understand that I may not fully understand what makes them incomplete until you provide me a perspective I have not seen yet. Highlights: * require the use of namespaces, and the minimum PHP version to support these (most likely 5.3.0, although we will know for sure when 5.2.4 is released in a week or so) * rewording of introduction to explain better the goals - further work will be done to explain the problems that are being solved, probably in a separate document * clarification of allfiles.php to show alternative syntax may be used if the result is the same * note added to the data files handling section to expect changes based on a proposal I emailed to pear-dev today * Extensive rewording of the commit policy for collectives, explaining that although commit access will be allowed for all collective developers, it is still expected that committing will function very much like it does today - with lead developer permission except in exceptional circumstances. This shifts more control back to developers while still opening things up. * Extensive rewording of the package design section to also give developers more control than the original wording * Added a note to the move from alpha->beta for a package saying that package names are available on a first-come-first-serve basis. * Added notes to the potential problems section so we don't forget them. Please let us know if this helps to address some of the concerns raised. There is a LOT more work to be done, but I would like to know if this is a step in the right direction. Greg