Re: Bug#366938: svn commit access to the d-i repo ...
Anthony Towns writes ("Re: Bug#366938: svn commit access to the d-i repo ..."):
> Access controls to source code repos hosted on .debian.org seem a
> technical decision to me, so plausibly within the committee's domain. We
> can, of course, decline to consider the question anyway. I wasn't
> intending to delegate anything.
I think we should settle the question of whether decisions of this
nature are technical or not, before a case turns up where the DPL and
the TC disagree.
Some situations that all seem similar to me:
* the maintainers for something (probably a package) revoke
someone's commit access to the repo (this is the case in question)
* the sysadmin team revokes someone's membership of some
group, or removes their account on some machine, or similar
* the listadmins revoke or restrict someone's posting ability
I think these are all political decisions implemented through
technical means. I think we can review the mechanisms used for access
control (eg, we could with insist on the use svn-over-ssh instead of
svn-over-ssl or vice versa) but we can't review the access control
list which specifies who gets the ability to do what.