Re: Bug#550817: ITP: gitolite -- standalone, souped-up version of gitosis

[Sitaram Chamarty <sitaram@atc.tcs.com>]

on 13/10/09 14:33 Stefano Zacchiroli wrote:
> On Tue, Oct 13, 2009 at 10:15:24AM +0200, Gerfried Fuchs wrote:
>   
>>   Description     : standalone, souped-up version of gitosis
>>
>> Gitolite is a rewrite of gitosis, with a completely different config
>> file that allows (at last!) access control down to the branch level,
>> including specifying who can and cannot rewind a given branch.
>>     
>
> /me playing devil's attorney role
>
> What if one has no idea of what "gitosis" is? For such a person, the
> above description will be close to meaningless. I suggest expanding in a
> couple of words what gitosis is, turning the reference to it as
> something like "similar to gitosis".
>   

Gitosis (and therefore Gitolite) is an ssh-based gatekeeper for a server
that hosts many git repos, and that needs access control of some sort. 
Without gitosis/gitolite, each developer needing to push to one of the
repositories hosted will need a (Unix) userid and password on that
server; gitosis/gitolite let you do that just using ssh public keys tied
to a single, common, user that hosts all the repositories.

Gitolite goes further than gitosis.  Its primary target is corporate
environments where the ability to restrict who can push to what branch
is also important.  Over the past few weeks it has grown a bit beyond
that primary reason, and acquired several other neat features described
in the main README.

> Thanks for your packaging work!
> Cheers.
>
>   

-- 
Sitaram Chamarty