Re: Re: Keeping CVS? was - Re: [PEAR-DEV] CVS 2 SVN (Re: [PEAR-DEV] candidatesfor PEAR Group: why should we vote for you? Tell us your plans and
yourhistory)

From: Date: Wed, 24 Jun 2009 22:22:04 +0000
Subject: Re: Re: Keeping CVS? was - Re: [PEAR-DEV] CVS 2 SVN (Re: [PEAR-DEV] candidatesfor PEAR Group: why should we vote for you? Tell us your plans and
yourhistory)
References: 1 2 3 4 5 6 7 8  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-52051@lists.php.net to get a copy of this message
Hi Alexey; On Jun 24, 2009, at 1:06 PM, Alexey Borzov wrote:
I immediately see at least three problems with having "pear" and "pear2" accounts anywhere, including GitHub: 1) It will introduce a bottleneck if any sort of approval will be required from such account,
There already is a bottleneck. Each package must be approved by a member of the PEAR community with enough karma to ok it. This is no different whether it's someone flipping a switch on pear.php.net or adding a public key to a repository on GitHub.
2) It will introduce unnecessary security problems.
Unless you are willing to back this statement up with examples of stated "security problems", I would like to ask you to refrain from spreading FUD.
And, last but not least, it is a violation of GitHub terms of service [1]:
4. Your login may only be used by one person – a single login shared by multiple people is not permitted. You may create separate logins for as many people as your plan allows.
Knowing "Chris" and "Scott" may be nice, but following the rules may be more useful when "Chris" and/or "Scott" leave for greener pastures.
This is an excellent point. Thanks for bringing it up. I've already started a discussion with GitHub about this, as I'm sure they've run into similar issues within other large open source projects that are using their service. As soon as I have a response from them, I'll let you know what they say about it. -T

« previous php.pear.dev (#52051) next »