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: Proposed change to Commit Access Policy Level 3

Looks great to me! David On 4 August 2016 at 06:20, Mitchell Baker wrote: > Over time we've made a series of exceptions to the level 3 requirements > for Sheriffs and this proposal addresses that. > > > The current Policy for level 3 is: > > Level 3 - Core Product Access > > Req

Re: Proposed change to Commit Access Policy Level 3

SGTM! - jst On Thu, Aug 4, 2016 at 8:57 AM, David Burns wrote: > Looks great to me! > > David > > On 4 August 2016 at 06:20, Mitchell Baker wrote: > >> Over time we've made a series of exceptions to the level 3 requirements >> for Sheriffs and this proposal addresses that. >> >> >> The current

Build System Project - Latest Update

Below is a highlight of all work the build peers have done since the last report[1]. The build peers have been working to get faster builds in automation as well as well as local developers. We have updated the way that Taskcluster decision and linting jobs use version control[2]. This has driven

Re: Proposed change to Commit Access Policy Level 3

+1 Good change. Lawrence On Wednesday, 3 August 2016, Mitchell Baker wrote: > Over time we've made a series of exceptions to the level 3 requirements > for Sheriffs and this proposal addresses that. > > > The current Policy for level 3 is: > > Level 3 - Core Product Access > >