Changes

When we moved to the "inbound" model of tree management, the Tree Sheriffs became a crucial part of our engineering infrastructure. The primary responsibility of the Sheriffs is and will always be to aid developers to easily, quickly, and seamlessly land their code in the proper location(s) and ensure that code does not break our automated tests. In the service of this objective, the Sheriffs work closely with the larger engineering organization to create and enforce landing policies that increase productivity while maintaining an efficient and robust automated testing system. Beyond the policy role, they have also become shepherds of automation quality by monitoring intermittent failures, performing uplifts and merges, and identifying poorly performing automation machines. This role has proven successful, and it feels like it is time to propose so a formal module for the Tree Sheriffs in the larger context of the Activities Modulewas created: [[Modules/Activities#Tree_Sheriffs]].

Ed Morley (edmorley) The living document of Sheriff roles and responsibilities will be kept up to date on this wiki page and will certainly change over time as our organization and our automation continues to expand. But this module owner and this document will help give the sheriffs a platform to work from for Tree Sheriffingfuture changes.

The living document of Sheriff roles and responsibilities will be kept up to date on this wiki page and will certainly change over time as* UTC+5:30: Nigel Babu [:nigelb]our organization and our automation continues to expand. But this module and this document will help give the sheriffs * UTC+1: Carsten Book [:Tomcat]* UTC+1: Ms2ger (who denies being a platform to worksheriff unless it suits him)* UTC-4: Ryan VanderMeulen [:RyanVM]* UTC-8: Wes Kocher [:KWierso]from for future changes.* UTC-8: Phil Ringnalda [:philor]