[tei-council] fine-grained permissions for subversion

Martin Holmes mholmes at uvic.ca
Tue Apr 12 13:39:54 EDT 2011

For me, the strongest argument for granular permissions would be the 
possibility to designate specific people as "maintainers" for particular 
areas of the specification in which they happen to be expert. I rather 
like the idea of gatekeepers (rather than having lots of people with 
commit privileges over the whole repo). There are some areas where I'd 
feel qualified to be a gatekeeper, but others where I definitely should 
not be; and with designated people for each area, it would be easier to 
know who is responsible for making a specific change once the council 
has agreed to it.


On 11-04-12 09:40 AM, Piotr Bański wrote:
> Much as you say, Sebastian, we didn't consider it critical, just
> something potentially nice to have. So no special concern, I was just
> following up on a conversation on SF access and the granularity of
> permissions.
>    P.
> On 12.04.2011 09:43, Sebastian Rahtz wrote:
>> On 12 Apr 2011, at 05:30, Piotr Bański wrote:
>>> We talked today (in the *better* taxi, coming from Martin's place) about
>>> SVN permissions and their granularity. Here is the link to where you can
>>> cast your vote for introducing directory-based permissions in SF:
>>> https://sourceforge.net/apps/ideatorrent/sourceforge/ideatorrent/idea/2/
>> I agree it would be nice, but I don't think its holding our work back. The
>> chance of irrecoverable abuse is really very very small, I would say.
>> do you have a special concern that this would solve?
>> --
>> Sebastian Rahtz
>>   Information and Support Group Manager
>> Oxford University Computing Services
>> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
>> Sólo le pido a Dios
>> que el futuro no me sea indiferente
> _______________________________________________
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
> PLEASE NOTE: postings to this list are publicly archived

More information about the tei-council mailing list