Re: Re: [PEPr] -1 for RFC::Package CVS/Package Web Access Sync
| From: | anatoly techtonik | Date: | Wed, 28 Dec 2005 05:24:30 +0000 |
| Subject: | Re: Re: [PEPr] -1 for RFC::Package CVS/Package Web Access Sync | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-40843@lists.php.net to get a copy of this message | ||
Hello Sergio,
>> 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?
SC> The proposal text is:
SC> «How about to give pearweb maintainer/lead status automatically to
SC> developers, who already have package CVS access?»
SC> Besides being extremely short for an RFC, I'd say this is a proposal to
SC> give any PEAR developer (anyone with CVS access to PEAR) lead status on
SC> pearweb (the project).
SC> Your interpretation is something I'd vote +1. It seems bureaucratic to
SC> have pearweb manage permissions and then have developers go ask for CVS
SC> karma to be set manually. Unfortunately, that's not what is on the RFC text.
Yep. Once set bureacracy is unbeatable. =)
t
--