I think that moving to new jenkins,foreman server will allow us to better manage authership via misc roles.
jenkins will probably use open-id plugin to allow access and we'll manage users permissions per project/view.. foreman also have a very extensive permissions system, so we can allow certain users to manage some services without giving them administrator. as for "sudo" access, we can create "system jobs" in jenkins to allow specific functions to run on slaves, like installing new rpms on jenkins slaves (which we have now). Eyal. ----- Original Message ----- > From: "Karsten 'quaid' Wade" <kw...@redhat.com> > To: "infra" <infra@ovirt.org> > Sent: Monday, December 17, 2012 5:13:30 PM > Subject: Adding new admin members > > What should our process be for: > > * When a new person is interested in helping on the Infra team? > * When that new person is ready for more more responsibility? > * When that new person is now an experienced person and can be handed > one or more root account accesses? > > Ideally we'll use sudo and groups to segment what people can do, so > that > means: > > * What are the logical groups we should make for sudo? > ** One for each service we want to split out? > > - Karsten > -- > Karsten 'quaid' Wade, Sr. Analyst - Community Growth > http://TheOpenSourceWay.org .^\ http://community.redhat.com > @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 > > > _______________________________________________ > Infra mailing list > Infra@ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
