Re: Owner for Commit Access Policy

On 04/08/16 06:06, Gregory Szorc wrote: > I'm going to say something that might be a bit contentious: I think a > single commit access policy for all of Mozilla reflects the needs of > Mozilla from several years ago, not the needs of Mozilla today. The world > has changed. Mozilla has changed. The

Re: Owner for Commit Access Policy

On 04/08/16 16:22, Hal Wine wrote: > On Thu, Aug 4, 2016 at 1:48 AM, Gervase Markham > wrote: > > I had a few abortive goes at this a few years ago; it's an enormous > effort to get everyone on the same bandwagon, and just leads to the > creation of bureaucrac

Re: Owner for Commit Access Policy

On Wed, Aug 3, 2016 at 10:31 PM, Mitchell Baker wrote: > Ah yes, good point. For me personally, there's very little that's > contentious about adapting our policies to reflect changing engineering > practices. When I wrote a bunch of our original policies many years back, > they were a reflecti

Re: Owner for Commit Access Policy

I think there are at least five reasonably distinct classes of repositories in active use. I'm sure we could be more fine-grained as needed. I would suggest that if someone were to draft a new policy, access to each class of repo should have a separate sign-off process. * Firefox and upstream comp

Re: Owner for Commit Access Policy

FWIW, for the 300+ accounts that I vouched for, I relied on risk management. I looked at what I knew about the folks that I vouched for, and what they're intending to do, and what mitigation strategy there was when things wouldn't go as intended. That risk management also shaped how we're ship