----- Original Message -----
From: "Trevor Vaughan" <tvaughan(a)onyxpoint.com>
To: "SCAP Security Guide" <scap-security-guide(a)lists.fedorahosted.org>
Sent: Tuesday, November 22, 2016 9:16:33 AM
Subject: Re: How should we expand commit access to SSG?
I would suggest making sub-projects for each of the distributions and then
use git submodules to tie it all together at the build level.
That way, you can restrict write access to particular users.
Alternatively, you could use protected branches and allow branch
maintainers to manage those and have a small set of core mergers that bring
it into the mainline.
I think we can trust people have good intentions and there is no need to
separate access like this. Either we trust the contributors and they can
change anything or we don't trust them and we don't let them push any
commits.
Many of the changes affect all the products and this separation would
complicate that I think.
--
Martin Preisler
Identity Management and Platform Security | Red Hat, Inc.