Hello, (I apologize for cross-posting but I think this subject concerns webapps because original draft, pkg-php because it's the place for PHP PEAR modules and debian-mentors because there are a lot of ITP/RFS last weeks. Please respect the Reply-To/Mail-Followup-To, which is set to [EMAIL PROTECTED], thanks)
We have a lot of ITP/RFS for PHP PEAR modules, mainly because new webapps need this modules. Note there are today 459 PHP PEAR modules in "pear.php.net" and I think we need a clear policy to avoid a lot of unmaintained packages. That why I propose a up-to-date draft for packaging PHP PEAR modules here: http://wiki.debian.org/GregoryColpart/PearPolicyDraft Feel free to comment it and send me updates by mail or IRC. The main idea is to have similar packaging for all modules to make easier collaborative maintenance. I hope this could also permit to "foo web application" maintainer to ask for new modules instead of packaging and take the responsability to maintain it. Regards, -- Gregory Colpart <[EMAIL PROTECTED]> GnuPG:1024D/C1027A0E Evolix - Informatique et Logiciels Libres http://www.evolix.fr/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
