Support base committer category for security

[jberry@…]

We need to restrict commits such that:

Any commiter can change:

trunk/dports

Only "base" committers can change:

• trunk/(all other)
• downloads/
• tags/
• branches/

I'm not sure what the full set of base committers should be now, as we've certainly lost some, but for a start:

jmpp, mww, jberry, pguyot, yeled, kvv, landonf, jkh, ...?

At some point, we may need to provide access to www or docs for a broader set of users, but it's not clear to me at present that's necessary given our new documenation arrangements.

[wsiegrist@…]

Stealing kvv's tickets... I'll do some research on the options for this.

[wsiegrist@…]

Email me a map of directories to lists of users and I'll implement this. I dont need the list of committers, you can just call them "committers". For admin, base, whatever-else, I'll need a list (of email addresses registered as MacOSForge).

[wsiegrist@…]

Cc Me!

[raimue (Rainer Müller)]

I think this limitation would restrict committers from doing base development. As we have version control, I don't fear any malicious commits we would miss. Developers should be responsible enough to submit patches as a ticket first if they are unsure if it should be committed.

[(none)]

Milestone Website & Documentation deleted