From: Konstantin Khomoutov <flatworm@users.sourceforge.net>
Date: Fri, 28 Jan 2011 12:06:31 GMT
Subject: Re: Permissions and authorisations in git repository
Message-ID: <20110128150631.33be0a9d.kostix@domain007.com>
In-Reply-To: <1296214884133-5969556.post@n2.nabble.com>

On Fri, 28 Jan 2011 03:41:24 -0800 (PST)
vikram2rhyme <vikram2rhyme@gmail.com> wrote:

> I am wondering if there are any permission and authorization control
> over git repository.
[...]

In the simplest case -- r/w access via SSH -- those who know the
login/password or possess the necessary private key have (full) access
to the repository. The repository can also be made accessible for
read-only via Git protocol (as a whole as well). This can be used for
simple write/read access discrimination.
If a more fine-grained control
is needed, third-party tools exist: gitolite:
https://github.com/sitaramc/gitolite gitosis: http://swik.net/gitosis

Note that as Git does not suffer from a centralised VCS syndrome of
having a single repository shared by everyone involved, the problem
you're facing might not exist at all: every developer or a group of
related developers maintains their own repository and a "central"
repository (in whatever sense you're willing to put into it) is owned
by a special person or a group of persons.