Changes between Version 1 and Version 2 of GitolitePlan


Ignore:
Timestamp:
Jul 30, 2013 7:52:59 AM (21 months ago)
Author:
thoughtpolice
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GitolitePlan

    v1 v2  
     1= The Gitolite Switch = 
     2 
    13Currently, the developer setup on `ghc.haskell.org` is a bit complicated and unfortunate. Most importantly, it hosts all of the git repositories we use. When a developer for GHC is inducted, we: 
    24 
     
    1315 * Every user needs a full shell account. While we probably *won't* be forkbombed by someone, few people actually *need* a full shell account, and the principle of least privilege applies here. Really, everybody is just pushing to git. 
    1416 
    15  * Because of the last point, group and access permissions on the repositories regularly get screwed up, causing situations where people don't have access (and can't push,) or we have to have `post-receive` hooks that modify the permissions. Both of these suck (this doesn't affect people like the Linux kernel who have pull-based development models, because they can afford to have strict maintainer models.) 
     17 * Because of the last point, group and access permissions on the repositories regularly get screwed up, causing situations where people don't have access (and can't push,) or we have to have `post-receive` hooks that modify the permissions. Both of these suck (this doesn't affect e.g. the Linux kernel developers, who have pull-based development models, because they can afford to.) 
    1618 
    1719 * Leading on more with the last point, people invariably fix this but it's always slightly patchy, and so the repositories that need 'fixing' for things like permissions are inconsistent, and it's hard to keep track of what needs to be maintained. 
     
    2123Gitolite is a piece of software that can alleviate most of these pains and also make central management easier: https://github.com/sitaramc/gitolite/wiki 
    2224 
    23 ## TODO FIXME 
     25= Proposed plan = 
    2426 
    25 Austin Seipp (thoughtpolice) and Herbert Valerio Riedel will put more notes here on the proposed changes, switchover details, etc. 
     27Below are some notes about how we (Austin & Herbert) would like to go about doing this. 
     28 
     29== Setup == 
     30 
     31== The switch == 
     32 
     33Ideally, most of the new setup can occur concurrently with the normal one undisturbed. Presumably 'the big switch' can happen in an hour or so downtime, in which we take the old URIs offline, bring gitolite online and tell people this is the time to fix your push URLs. 
     34 
     35== Developer changes == 
     36 
     37TODO FIXME: note what changes here for developers who already have push based access 
     38 
     39= Current status = 
     40 
     41The server currently isn't setup, but Austin can easily make it so. 
     42 
     43== Questions == 
     44 
     45 * Tangential: should we deprecate the darcs.haskell.org URL? Who uses it? The name was known to be a funny misnomer from the git switchover times, but As Far As Austin Knows, only GHC developers really use it these days. Perhaps we could just retire it. 
     46 
     47  * Austin notes that both nhc and yhc use it, so Malcolm and Neil will need to be asked. 
     48 
     49 * Who's actively committing, and does anybody beyond that actually *need* a shell account? It's unclear who uses `ghc.haskell.org` for what at the moment. 
     50 
     51 * Tangential: The current directory setup is a total mess on `darcs.haskell.org`. 
     52 
     53== Contact points === 
     54 
     55Austin Seipp (thoughtpolice) and Herbert Valerio Riedel (hvr) can be contacted about details or specifics.