Sheriffs typically need level 3 access to fulfill their roles. But they aren't chosen based on number and quality of patches, so often don't meet the current requirements.
Kyle do you want to propose some language for the exception? If I write it i'll end up coming back to those of you living with this day to day in any case ..
I would change "module owners or peers of code stored at this level" to "module owners or peers of code stored at this level or owners or peers of the 'Tree Sheriffs' module."
I noticed there was some discussion of mentorship in this case, given an incoming sheriff isn't as familar with the process. Should that be included? I guess that might mean adding the sheriffs as an exception, and the excption to the policy applies provided the commitments from the mentors etc are made ... This could be over complex; perhaps your simple solution is best .. not srue
I think we can probably leave it to the sheriffs to police their own and make sure someone getting access under this exception doesn't embarrass themselves. Gerv
I noted the proposed change in dev.platform, .governance and firefox-dev this evening. So far, a suggestion we describe the scope of this policy, since a bunch of mozilla projects living in github are living with different policies.
You need to log in before you can comment on or make changes to this bug.