|Team Lead: Kendall Libby||Mailing List: email@example.com|
|The Developer Services team works on version control systems and related tools at Mozilla.
Oncall for VCS
"Oncall" is really "escalation path" for services we handle. Start with the service owner, then irc channel (below), then escalate to oncall if no response.
|Backup on call||Jacob Watkins||dividehex|
As always with service issues, please indicate urgency and contact information in any page or voice mail. Using Nagios paging is most reliable. For less urgent contact methods, see contact info below.
|Kendall Libby||fubar||Boston, MA, USA||BMO, Treeherder, MozReview, DXR, hg, git||ET|
|Jake Watkins||dividehex||California, USA||MozReview, Autoland|
|David House||dhouse||Montana, USA|
|Gregory Szorc||gps||San Francisco, CA, USA||hg, MozReview, build module owner||PT|
|Hal Wine (on loan from RelEng)||hwine||San Francisco, CA, USA||VCSs, releng and IT liaison||PT|
To contact all of the above, use the list firstname.lastname@example.org or #vcs.
Additional folks work on various modifications and extensions to the version control systems. They can be reached at email@example.com or #vcs.
The other systems we support follow the "devops" model -- the first point of contact for operations and support are the following channels on irc:
- #bteam for BMO
- #treeherder for Treeherder (discussion list)
- #mozreview for MozReview
- #static for DXR