Re: [SVN-MIGRATION] Re: Github
| From: | Johannes Schlüter | Date: | Wed, 25 Feb 2009 18:47:40 +0000 |
| Subject: | Re: [SVN-MIGRATION] Re: Github | ||
| References: | 1 2 3 | Groups: | svn.migration |
| Request: | Send a blank email to svn-migration+get-274@lists.php.net to get a copy of this message | ||
On Wed, 2009-02-25 at 09:28 -0800, Andrei Zmievski wrote:
> We can have a GitHub user "PHP Dev" owning the mainline
> project, and then just add the SSH public keys of those
> users that are allowed to update the mainline (or use the new ACL
> method that Rasmus was talking with GitHub guys about).
As long as we have a good process for changing ssh keys (taking our
number of devs I'd say there's _at least_ one who's getting a new box
per month in average) and ACLs that's fine but we shouldn't find
ourselves in the need for a single shared password owned by a group
people to set such basic things using a Web GUI. So just a thing to
check before migrating and hopefully no show stopper.
I think the issue about adding/removing extensions while keeping history
is way more important and complex. :-)
johannes