Re: Proposed change to Commit Access Policy Level 3

I haven't heard any negative comments, so it's time to go ahead and make this change. mitchell On 8/3/16 10:20 PM, 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:

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 > >

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

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

Proposed change to Commit Access Policy Level 3

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 Requirements: two vouchers - module owners or peers of code stored at this level The iss