Changes

 When we Mozilla moved to the "inbound" model of tree management, the Tree Sheriffs became a crucial part important stewards 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 so a A formal module for the Tree Sheriffs in the larger context of the Activities Module was created: [[Modules/Activities#Tree_Sheriffs]]. 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 and this document will help give the sheriffs a platform to work from for future changes.

The owners & peers of the Tree Sheriffs module can be found on the [[Modules/Activities#Tree_Sheriffs|module page]], however for day -to -day sheriffduty coverage , look for the following people in #developers (the and #sheriffs. The on-duty sheriff will typically have "|sheriffduty " appended to their IRC nick):.

If you want to know more about us see our [[Auto-tools/The Sheriffs|Teampage]] For more info on what's happening at the moment, see the on-duty notescurrent activity log:[https://publicdocs.etherpad-mozillagoogle.orgcom/document/pd/sheriffing-notes1Zqh0EGE2zymR0c8aB1GYnPLjOyKnmdTB8ctEgFC2YRQ/edit# Activity Log]

We're always looking for more people to join the community team and help out - just drop us a message!