Re: [PEPr] -1 for RFC::Package CVS/Package Web Access Sync

Martin Jansen wrote:

On Sun Dec 11, 2005 at 04:0908PM -0000, Sérgio Carvalho wrote:

While pearweb could be more open, perhaps posting feature requests on a public board for PEAR developers to pick up and develop, I don't see a reason to give CVS access to pearweb to everyone. It should be a project lead as other PEAR packages.

Could it be that you guys misinterpreted Anatoly's proposal? If I got him right, he is suggesting that the CVS karma file (on cvs.php.net) is automagically synchronized with the karma database table that is used on pear.php.net. In practice this means that whenever developers get CVS write access to a package, they also become a (lead?) maintainer of the package. Or is it my interpretation that is bogus?

The proposal text is: «How about to give pearweb maintainer/lead status automatically to developers, who already have package CVS access?» Besides being extremely short for an RFC, I'd say this is a proposal to give any PEAR developer (anyone with CVS access to PEAR) lead status on pearweb (the project). Your interpretation is something I'd vote +1. It seems bureaucratic to have pearweb manage permissions and then have developers go ask for CVS karma to be set manually. Unfortunately, that's not what is on the RFC text. -- Sérgio

- Martin