Re: pear.php.net site activities?

> Hi, > > A lot of people have offered to step in and help out with the web site, > but I feel that this process is a bit too closed right now. Could > everyone who's still working on it give a hint to the list? > > To re-iterate, these are my ideas for the site: > > * Pear.php.net will be an infrastructure site for PEAR, where we (PEAR > contributors) administer the PEAR package space (add "directories", > appoint maintainers to each directory and so on) and maintain packages > (bug reports, releases, user notes). > Yes. I think the bug reports should basically be a "pearified" version of PHP's bug reporting system... The pear site should also have a fairly complex administration system, ie, have regular users (download packages), users who can add packages to a directory and remove there own packages and then users who have access to everything (create dirs, remove dirs, edit packages, remove packages, etc.) > * Pear.php.net has two interfaces: HTML (for us human types) and XML > (for programs). > Can you elaborate on this a little bit? How would it be useful for machines (I have a basic idea, I just want to make sure we're on the same page ;-)? > * All PEAR developers get accounts on this site. When you get a PEAR > account you also get an account in PHP's CVS system with ACLs based on > your project/package memberships. > sounds good. > * All packages will be registered as separate "projects" (DB is one, > Chuck's Log stuff is one, PHPDoc is one, and so on), with one or more > lead developers and members, their own releases and so on. > yup. > * Users (of PHP and PEAR) can use the "pear" command-line utility (and > possibly other methods later) to maintain their packages. As we get > this infrastructure in place, less PEAR packages will be distributed > with PHP, and more will be made available for installation from this > repository. > I assume this is where the XML interface comes into play... > In addition, we will offer the following: > > * A license we encourage (but not require) people to use, basically a > Zend-less PHP license > Well, I don't think Zend has much todo with the matter, I think perhaps a sub-group should be formed to create a license which will be beneficial to PEAR (GPL compatible) and beneficial to people contributing code to pear. Then of course pear code contributors could also release there code under: GPL LGPL MPL Artistic License Public Domain Any others agreed upon (ie, lets steal a bit from source forge) > * CVS space on cvs.php.net for those who want it > But not an automatic process.... _Sterling