Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:54482
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain joeysmith.com designates 209.90.98.146 as permitted sender)
Date: Mon, 8 Aug 2011 22:27:25 -0600
To: internals@lists.php.net
Message-ID: <20110809042725.GA21131@joeysmith.com>
References: <slrnj3tulc.6vi.dsp@experimentalworks.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <slrnj3tulc.6vi.dsp@experimentalworks.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [PHP-DEV] [RFC] Choosing a distributed version control system
 for PHP (or not). Call for Participation.
From: joey@joeysmith.com (Joey Smith)

On Sun, Aug 07, 2011 at 04:50:55PM -0400, David Soria Parra wrote:
> Hi Internals,
> 
> NOTE: this is not the place for any religiouise discussion about git vs
> mercurial whatsover. if you have nothing else to add than "hg is $***
> anyway" or think hosting platform XY will solve all our problems
> without reading the RFC carefully, please post to alt.relgion.* and not
> here.
> 
> 
> - David

I feel like maybe the RFC throws in the towel too early on the idea of
using SSH keys to manage access control. On the git side, there's a tool
called gitolite which makes management of access controls via SSH keys
incredibly trivial. While I've never looked at the code behind the online
"Manager Users" tool we have, I can't imagine it would be terribly hard to
expand that to allow people to add their public SSH keys for plugging into
gitolite [1].

[1] https://github.com/sitaramc/gitolite