DeveloperServices: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(update oncall)
(update oncall)
Line 18: Line 18:
|-
|-
| Primary
| Primary
| Hal Wine
| hwine
|-
| Backup on call
| Kendall Libby
| Kendall Libby
| fubar
| fubar
|-
| Backup on call
| Hal Wine
| hwine
|-
|-
| Escalation
| Escalation
| Mark Côté
| Amy Rich
| mcote
| arr
|}
|}
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|contact info]] below.
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|contact info]] below.

Revision as of 19:39, 14 April 2016

Developer Services
Team Lead: Lawrence Mandel Mailing List: developer-services@mozilla.org
The Developer Services team works on version control systems and related tools at Mozilla.
  • We work on hg, git, and svn.
  • We support the try repository.
  • We also provide operational support for BMO, MozReview, Treeherder, MXR, and DXR.

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.

Role Name IRC Contact
Primary Hal Wine hwine
Backup on call Kendall Libby fubar
Escalation Amy Rich arr

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.

Roster

Name Contact Location Project(s) Working Hours
Kendall Libby fubar Boston, MA, USA BMO, Treeherder, Reviewboard, DXR, MXR, hg, git ET
Gregory Szorc gps San Francisco, CA, USA hg, Reviewboard, 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 developer-services@mozilla.org or #vcs.

Additional folks work on various modifications and extensions to the version control systems. They can be reached at dev-version-control@lists.mozilla.org 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:

Projects

Project Name Description Primary Contact
project This project does something laura@mozilla.com

Meetings

Services

  • /Account Recovery - how to re-enable account access
  • /git - details of our Git DVCS system
  • /hg - details of our Mercurial DVCS system