Boost logo

Boost :

Subject: Re: [boost] Git permissions model
From: Agustín K-ballo Bergé (kaballo86_at_[hidden])
Date: 2013-12-03 23:51:14


On 04/12/2013 01:44 a.m., Vladimir Prus wrote:
>
> Hi,
>
> I have a couple of questions about the permission models that we use for
> git.
>
> - To give somebody push access to the 'build' repository, I need to file an
> admin issue. Why can't I control access to the repository I maintain?
> In fact, why I can't even edit repository description?

+1 I believe library authors/maintainers should have admin access to
their own repositories, and thus have direct control over the
permissions granted to collaborators.

> - Suppose I find a random typo in library X. In SVN, I can just fix it
> within a minute.
> In Git, I would have to either ask for push access (which I think
> won't scale), or
> I need to fork the repo, to the change, and submit a pull request,
> which is equally
> cumbersome. Was not Git supposed to simplify things?

True, that's the recommended procedure. Note however that you can edit
the file "in-place" from github, and it will take care of the fork and
pull request for you. All you need to do is edit the file on a web form.

Regards,

-- 
Agustín K-ballo Bergé.-
http://talesofcpp.fusionfenix.com

Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk