DeveloperServices: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(add jake to rotation \o/)
(update roster, services)
Line 5: Line 5:
|mailinglist=developer-services@mozilla.org
|mailinglist=developer-services@mozilla.org
|description=The Developer Services team works on version control systems and related tools at Mozilla.
|description=The Developer Services team works on version control systems and related tools at Mozilla.
* We work on hg, git, and svn.
* We work on hg, git-internal, and svn.
* We support the try repository.
* We support the try repository.
* We also provide operational support for BMO, MozReview, Treeherder, MXR, and DXR.
* We also provide operational support for BMO, MozReview, Treeherder, and DXR.
}}<section end=summary />
}}<section end=summary />


Line 46: Line 46:
|fubar
|fubar
|Boston, MA, USA
|Boston, MA, USA
|BMO, Treeherder, Reviewboard, DXR, MXR, hg, git
|BMO, Treeherder, MozReview, DXR, hg, git
|ET
|ET
|-
|Jake Watkins
|dividehex
|California, USA
|MozReview, Autoland
|-
|David House
|dhouse
|Montana, USA
|-
|-
|Gregory Szorc
|Gregory Szorc
|gps
|gps
|San Francisco, CA, USA
|San Francisco, CA, USA
|hg, Reviewboard, build module owner
|hg, MozReview, build module owner
|PT
|PT
|-
|-
Line 72: Line 81:
* [ircs://irc.mozilla.org/#mozreview #mozreview] for MozReview
* [ircs://irc.mozilla.org/#mozreview #mozreview] for MozReview
* [ircs://irc.mozilla.org/#static #static] for DXR
* [ircs://irc.mozilla.org/#static #static] for DXR
* There is no help to be found for MXR. Abandon all hope, etc, etc.


= Meetings =
= Meetings =

Revision as of 17:57, 7 September 2016

Developer Services
Team Lead: Kendall Libby 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-internal, and svn.
  • We support the try repository.
  • We also provide operational support for BMO, MozReview, Treeherder, 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 Kendall Libby fubar
Backup on call Jake Watkins dividehex
Backup Hal Wine hwine
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, 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 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:

Meetings

Services

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