Steve Long wrote: > I'm thinking in any case that a db app can save old revisions or use a svn > backend. I'm looking at this from a workflow perspective, in terms > especially of the security issue around giving commit access to the whole > tree. If the individual maintainer only has permission for those ebuilds > s/he is responsible for, it might make it easier to allow new people write > access.
The idea of restricting access to specific parts of gentoo-x86 has come up many times. It doesn't fix anything and actually makes some things worse. Committers still have access to wherever they can commit, so they can work whatever evil they want there without needing the rest of the tree. If we trust people to commit anywhere, we should trust them to commit everywhere. If we don't trust them to commit, why do they have commit access? This implies a basic lack of trust within our development team, which means it can never be a true team. Thanks, Donnie
signature.asc
Description: OpenPGP digital signature
