Joerg Jaspert writes ("Re: Meeting agenda bot, website, git, ssh"):
> [Ian Jackson:]
> > Is there one single access control setup for the whole thing, or are
> > there several ? It would be nice to be able to let people edit the
> > website without giving them the power to run code on the server, for
> > example.
>
> Noone gets access to the server directly. :)
>
> (Well, in case someone needs access to a server, we can certainly
> arrange things. But thats completly seperate from git access)
If the code for something running on the server is kept in git then
effectively everyone who can write to the git can run code on the
server, because even if pushing to the running copy is manual no-one
will review every diff.
Ian.