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: | Alexey Borzov | Date: | Wed, 24 Jun 2009 18:06:10 +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 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-52047@lists.php.net to get a copy of this message | ||
Hi Travis,
Travis Swicegood wrote:
Agreed on all points. I know know Chris, but Scott and I are fellow authors, so I have a bit of an in there. I've managed to secure both the pear and pear2 user for our use, one for the old legacy code and another for the new pear2 5.3 code. The idea that I've been kicking around is that each package would be created independent of those accounts until its an official package. At that time, the PEAR Group would create a real repo for the pear2 user and pull in the lead's work.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, 2) It will introduce unnecessary security problems. 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. [1] http://github.com/site/terms