MozillaWiki - User contributions [en]

DeveloperServices

2019-06-21T21:24:33Z

Klibby:

<section begin=summary />{{TeamSummary
|teamtitle=Developer Services
|teampagelocation=DeveloperServices
|teamlead=Kendall Libby
|mailinglist=developer-services@mozilla.org
|description=The Developer Services team works on version control systems and related tools at Mozilla.
* We work on hg, git-internal, and vcs-sync.
* We support the try repository.
* We also provide operational support for Treeherder (DB only), and DXR.
}}<section end=summary />

= 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.
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Role'''
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''IRC Contact'''
|-
| Primary
| devservices@moz-svc-ops.pagerduty.com
|}
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.

= Roster =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''Contact'''
| style="background:#EFEFEF;" | '''Location'''
| style="background:#EFEFEF;" | '''Project(s)'''
| style="background:#EFEFEF;" | '''Working Hours'''
|-
|Kendall Libby
|fubar
|Boston, MA, USA
|Treeherder (DB), DXR, hg, git-internal
|ET
|-
|Jake Watkins
|dividehex
|California, USA
|Autoland, Treeherder (DB)
|PT
|-
|David House
|dhouse
|Montana, USA
|DXR, vcssync
|MT
|-
|Connor Sheehan
|sheehan
|Toronto, CA
|hg
|ET
|-
|Steven Macleod
|smacleod
|Toronto, CA
|hg
|ET
|-
|Byron Jones
|glob
|Perth, AUS
|hg
|GMT+08:00
|}

<div id="contact"> </div>
To contact all of the above, use the list developer-services@mozilla.org or [ircs://irc.mozilla.org/#vcs #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 [ircs://irc.mozilla.org/#vcs #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:
* [ircs://irc.mozilla.org/#bteam #bteam] for BMO
* [ircs://irc.mozilla.org/#treeherder #treeherder] for Treeherder ([https://groups.google.com/forum/#!forum/mozilla.tools.treeherder discussion list])
* [ircs://irc.mozilla.org/#mozreview #mozreview] for MozReview
* [ircs://irc.mozilla.org/#static #static] for DXR

= Meetings =
* [[DeveloperServices/TeamMeetings|https://wiki.mozilla.org/DeveloperServices/TeamMeetings]]

= Services =
* [[/Account Recovery]] - how to re-enable account access
* [[/git]] - details of our Git DVCS system
* [[/hg]] - details of our Mercurial DVCS system

WeeklyUpdates/2019-01-07

2019-01-07T00:15:12Z

Klibby: Add new hire

{{WeeklyUpdateNav}}
* Every Monday @ 11:00am Pacific Time (19:00 UTC)
* https://air.mozilla.org to watch and listen
* join irc.mozilla.org #airmozilla for backchannel discussion
* Presenters only: Vidyo room "Brownbags". Do '''not''' use this room if you're not planning to speak.
{{conf|8600}}
** If you plan on presenting, please join the Vidyo BrownBags 20 minutes prior to the start of the meeting and announce to the A/V Technicians that you will be speaking so that they can confirm your Audio and Video.

__TOC__

= All-hands Status Meeting Agenda =

Items in this section will be shared during the live all-hand status meeting.

== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===

=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===

=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===

=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===

=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===

=== Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===

=== Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===

=== Next Week ===

== Speakers ==

The limit is '''3 minutes per topic'''. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week. The meeting is streamed in a 4:3 format in order to allow for split screen. If your slides are 16:9 "widescreen" format, please indicate in the "Sharing" column below.

{| class="fullwidth-table wikitable"
|-
! [https://mozillians.org/u/USERNAME Presenter]
! Title
! Topic
! Location
! Sharing
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, 4:3 or 16:9)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
|}

= Welcome! =

Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.

{| class="fullwidth-table wikitable"
|-
! ''Who is being introduced?''
! ''Who are you? (the introducer)''
! ''Where are you doing the introduction?''
! ''Where are they from?''
! ''How will they be part of Mozilla?''
|-
| Their Name
| Your Name
| Intro location
| Their Location
| Their Role
|-

| Lily Chaskelman
| Alicia Gray
| Mountain View
| Mountain View
| Sr. Privacy Analyst, Trust & Security
|-
| Andrew Erickson
| Kendall Libby
| San Francisco
| San Francisco
| Sr Android Operations Engineer
|-
|}

[[Category:Weekly Updates]]
[[Category:Meeting Notes]]

DeveloperServices

2018-10-16T17:08:34Z

Klibby:

<section begin=summary />{{TeamSummary
|teamtitle=Developer Services
|teampagelocation=DeveloperServices
|teamlead=Kendall Libby
|mailinglist=developer-services@mozilla.org
|description=The Developer Services team works on version control systems and related tools at Mozilla.
* We work on hg, git-internal, and vcs-sync.
* We support the try repository.
* We also provide operational support for Treeherder (DB only), and DXR.
}}<section end=summary />

= 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.
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Role'''
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''IRC Contact'''
|-
| Primary
| Kendall Libby
| fubar
|-
| 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|contact info]] below.

= Roster =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''Contact'''
| style="background:#EFEFEF;" | '''Location'''
| style="background:#EFEFEF;" | '''Project(s)'''
| style="background:#EFEFEF;" | '''Working Hours'''
|-
|Kendall Libby
|fubar
|Boston, MA, USA
|Treeherder (DB), DXR, hg, git-internal
|ET
|-
|Jake Watkins
|dividehex
|California, USA
|Autoland, Treeherder (DB)
|PT
|-
|David House
|dhouse
|Montana, USA
|DXR, vcssync
|MT
|-
|Gregory Szorc
|gps
|San Francisco, CA, USA
|hg, build module owner
|PT
|-
|Connor Sheehan
|sheehan
|Toronto, CA
|hg
|ET
|-
|Steven Macleod
|smacleod
|Toronto, CA
|hg
|ET
|-
|Byron Jones
|glob
|Perth, AUS
|hg
|GMT+08:00
|}

<div id="contact"> </div>
To contact all of the above, use the list developer-services@mozilla.org or [ircs://irc.mozilla.org/#vcs #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 [ircs://irc.mozilla.org/#vcs #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:
* [ircs://irc.mozilla.org/#bteam #bteam] for BMO
* [ircs://irc.mozilla.org/#treeherder #treeherder] for Treeherder ([https://groups.google.com/forum/#!forum/mozilla.tools.treeherder discussion list])
* [ircs://irc.mozilla.org/#mozreview #mozreview] for MozReview
* [ircs://irc.mozilla.org/#static #static] for DXR

= Meetings =
* [[DeveloperServices/TeamMeetings|https://wiki.mozilla.org/DeveloperServices/TeamMeetings]]

= Services =
* [[/Account Recovery]] - how to re-enable account access
* [[/git]] - details of our Git DVCS system
* [[/hg]] - details of our Mercurial DVCS system

DeveloperServices

2018-10-05T19:44:37Z

Klibby:

<section begin=summary />{{TeamSummary
|teamtitle=Developer Services
|teampagelocation=DeveloperServices
|teamlead=Kendall Libby
|mailinglist=developer-services@mozilla.org
|description=The Developer Services team works on version control systems and related tools at Mozilla.
* We work on hg, git-internal, and vcs-sync.
* We support the try repository.
* We also provide operational support for Treeherder (DB only), and DXR.
}}<section end=summary />

= 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.
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Role'''
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''IRC Contact'''
|-
| Primary
| David House
| dhouse
|-
| 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|contact info]] below.

= Roster =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''Contact'''
| style="background:#EFEFEF;" | '''Location'''
| style="background:#EFEFEF;" | '''Project(s)'''
| style="background:#EFEFEF;" | '''Working Hours'''
|-
|Kendall Libby
|fubar
|Boston, MA, USA
|Treeherder (DB), DXR, hg, git-internal
|ET
|-
|Jake Watkins
|dividehex
|California, USA
|Autoland, Treeherder (DB)
|PT
|-
|David House
|dhouse
|Montana, USA
|DXR, vcssync
|MT
|-
|Gregory Szorc
|gps
|San Francisco, CA, USA
|hg, build module owner
|PT
|-
|Connor Sheehan
|sheehan
|Toronto, CA
|hg
|ET
|-
|Steven Macleod
|smacleod
|Toronto, CA
|hg
|ET
|-
|Byron Jones
|glob
|Perth, AUS
|hg
|GMT+08:00
|}

<div id="contact"> </div>
To contact all of the above, use the list developer-services@mozilla.org or [ircs://irc.mozilla.org/#vcs #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 [ircs://irc.mozilla.org/#vcs #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:
* [ircs://irc.mozilla.org/#bteam #bteam] for BMO
* [ircs://irc.mozilla.org/#treeherder #treeherder] for Treeherder ([https://groups.google.com/forum/#!forum/mozilla.tools.treeherder discussion list])
* [ircs://irc.mozilla.org/#mozreview #mozreview] for MozReview
* [ircs://irc.mozilla.org/#static #static] for DXR

= Meetings =
* [[DeveloperServices/TeamMeetings|https://wiki.mozilla.org/DeveloperServices/TeamMeetings]]

= Services =
* [[/Account Recovery]] - how to re-enable account access
* [[/git]] - details of our Git DVCS system
* [[/hg]] - details of our Mercurial DVCS system

DeveloperServices

2018-02-20T16:37:30Z

Klibby:

<section begin=summary />{{TeamSummary
|teamtitle=Developer Services
|teampagelocation=DeveloperServices
|teamlead=Kendall Libby
|mailinglist=developer-services@mozilla.org
|description=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 (DB only), and DXR.
}}<section end=summary />

= 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.
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Role'''
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''IRC Contact'''
|-
| Primary
| Kendall Libby
| fubar
|-
| 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|contact info]] below.

= Roster =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''Contact'''
| style="background:#EFEFEF;" | '''Location'''
| style="background:#EFEFEF;" | '''Project(s)'''
| style="background:#EFEFEF;" | '''Working Hours'''
|-
|Kendall Libby
|fubar
|Boston, MA, USA
|BMO, Treeherder (DB), MozReview, DXR, hg, git
|ET
|-
|Jake Watkins
|dividehex
|California, USA
|MozReview, Autoland, Treeherder (DB)
|PT
|-
|David House
|dhouse
|Montana, USA
|BMO, DXR, vcssync
|MT
|-
|Gregory Szorc
|gps
|San Francisco, CA, USA
|hg, MozReview, build module owner
|PT
|-
|Connor Sheehan
|sheehan
|Toronto, CA
|hg
|ET
|}

<div id="contact"> </div>
To contact all of the above, use the list developer-services@mozilla.org or [ircs://irc.mozilla.org/#vcs #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 [ircs://irc.mozilla.org/#vcs #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:
* [ircs://irc.mozilla.org/#bteam #bteam] for BMO
* [ircs://irc.mozilla.org/#treeherder #treeherder] for Treeherder ([https://groups.google.com/forum/#!forum/mozilla.tools.treeherder discussion list])
* [ircs://irc.mozilla.org/#mozreview #mozreview] for MozReview
* [ircs://irc.mozilla.org/#static #static] for DXR

= Meetings =
* [[DeveloperServices/TeamMeetings|https://wiki.mozilla.org/DeveloperServices/TeamMeetings]]

= Services =
* [[/Account Recovery]] - how to re-enable account access
* [[/git]] - details of our Git DVCS system
* [[/hg]] - details of our Mercurial DVCS system

DeveloperServices

2018-02-20T16:35:10Z

Klibby:

<section begin=summary />{{TeamSummary
|teamtitle=Developer Services
|teampagelocation=DeveloperServices
|teamlead=Kendall Libby
|mailinglist=developer-services@mozilla.org
|description=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 (DB only), and DXR.
}}<section end=summary />

= 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.
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Role'''
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''IRC Contact'''
|-
| Primary
| Kendall Libby
| fubar
|-
| 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|contact info]] below.

= Roster =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''Contact'''
| style="background:#EFEFEF;" | '''Location'''
| style="background:#EFEFEF;" | '''Project(s)'''
| style="background:#EFEFEF;" | '''Working Hours'''
|-
|Kendall Libby
|fubar
|Boston, MA, USA
|BMO, Treeherder (DB), MozReview, DXR, hg, git
|ET
|-
|Jake Watkins
|dividehex
|California, USA
|MozReview, Autoland, Treeherder (DB)
|-
|David House
|dhouse
|Montana, USA
|-
|Gregory Szorc
|gps
|San Francisco, CA, USA
|hg, MozReview, build module owner
|PT
|}

<div id="contact"> </div>
To contact all of the above, use the list developer-services@mozilla.org or [ircs://irc.mozilla.org/#vcs #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 [ircs://irc.mozilla.org/#vcs #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:
* [ircs://irc.mozilla.org/#bteam #bteam] for BMO
* [ircs://irc.mozilla.org/#treeherder #treeherder] for Treeherder ([https://groups.google.com/forum/#!forum/mozilla.tools.treeherder discussion list])
* [ircs://irc.mozilla.org/#mozreview #mozreview] for MozReview
* [ircs://irc.mozilla.org/#static #static] for DXR

= Meetings =
* [[DeveloperServices/TeamMeetings|https://wiki.mozilla.org/DeveloperServices/TeamMeetings]]

= Services =
* [[/Account Recovery]] - how to re-enable account access
* [[/git]] - details of our Git DVCS system
* [[/hg]] - details of our Mercurial DVCS system

DeveloperServices

2017-09-19T19:38:53Z

Klibby: /* Oncall for VCS */

<section begin=summary />{{TeamSummary
|teamtitle=Developer Services
|teampagelocation=DeveloperServices
|teamlead=Kendall Libby
|mailinglist=developer-services@mozilla.org
|description=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.
}}<section end=summary />

= 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.
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Role'''
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''IRC Contact'''
|-
| Primary
| Kendall Libby
| fubar
|-
| Backup on call
| Jacob Watkins
| dividehex
|-
| 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|contact info]] below.

= Roster =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''Contact'''
| style="background:#EFEFEF;" | '''Location'''
| style="background:#EFEFEF;" | '''Project(s)'''
| style="background:#EFEFEF;" | '''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
|}

<div id="contact"> </div>
To contact all of the above, use the list developer-services@mozilla.org or [ircs://irc.mozilla.org/#vcs #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 [ircs://irc.mozilla.org/#vcs #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:
* [ircs://irc.mozilla.org/#bteam #bteam] for BMO
* [ircs://irc.mozilla.org/#treeherder #treeherder] for Treeherder ([https://groups.google.com/forum/#!forum/mozilla.tools.treeherder discussion list])
* [ircs://irc.mozilla.org/#mozreview #mozreview] for MozReview
* [ircs://irc.mozilla.org/#static #static] for DXR

= Meetings =
* [[DeveloperServices/TeamMeetings|https://wiki.mozilla.org/DeveloperServices/TeamMeetings]]

= Services =
* [[/Account Recovery]] - how to re-enable account access
* [[/git]] - details of our Git DVCS system
* [[/hg]] - details of our Mercurial DVCS system

DeveloperServices

2017-09-06T14:08:52Z

Klibby: /* Oncall for VCS */ update oncall

<section begin=summary />{{TeamSummary
|teamtitle=Developer Services
|teampagelocation=DeveloperServices
|teamlead=Kendall Libby
|mailinglist=developer-services@mozilla.org
|description=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.
}}<section end=summary />

= 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.
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Role'''
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''IRC Contact'''
|-
| Primary
| Dave House
| dhouse
|-
| Backup on call
| Jacob Watkins
| dividehex
|-
| 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|contact info]] below.

= Roster =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''Contact'''
| style="background:#EFEFEF;" | '''Location'''
| style="background:#EFEFEF;" | '''Project(s)'''
| style="background:#EFEFEF;" | '''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
|}

<div id="contact"> </div>
To contact all of the above, use the list developer-services@mozilla.org or [ircs://irc.mozilla.org/#vcs #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 [ircs://irc.mozilla.org/#vcs #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:
* [ircs://irc.mozilla.org/#bteam #bteam] for BMO
* [ircs://irc.mozilla.org/#treeherder #treeherder] for Treeherder ([https://groups.google.com/forum/#!forum/mozilla.tools.treeherder discussion list])
* [ircs://irc.mozilla.org/#mozreview #mozreview] for MozReview
* [ircs://irc.mozilla.org/#static #static] for DXR

= Meetings =
* [[DeveloperServices/TeamMeetings|https://wiki.mozilla.org/DeveloperServices/TeamMeetings]]

= Services =
* [[/Account Recovery]] - how to re-enable account access
* [[/git]] - details of our Git DVCS system
* [[/hg]] - details of our Mercurial DVCS system

ReleaseEngineering/PuppetAgain/HowTo/Hack on PuppetAgain

2017-09-05T14:50:10Z

Klibby: Update puppet-lint documentation

= Hacking =
PuppetAgain is (or, at least, will be) a [http://www.mozilla.org/hacking/module-ownership.html code module], and as such people working on PuppetAgain follow the usual Mozilla process for making changes:
* hack
* post a patch, request review from a module owner or peer
* repeat until r+ (and sr+ if necessary)
* commit
* monitor and handle any problems as a result of the commit
The last point is particularly important, since puppet masters automatically update to the latest commit, and start deploying that to hosts.

== Exceptions to Review Requirement ==
* <tt>a=nodechange</tt> - self-approval if you're only changing node definitions, and only for nodes you're responsible for
* <tt>a=org-only</tt> - self-approval if you're changing $org-config.pp or $org-nodes.pp and your org does not require review
* <tt>a=versionbump</tt> - self-approval if you're only changing the version of a package and have considered the implications for all orgs of the change
* <tt>a=userdir</tt> - self-approval if you're changing your '''*own*''' user directory files with the explicit rule of excluding large files
* <tt>r=bustage</tt> - self-approval if you're backing out a broken update, in order to restore service.

= Coding guidelines =
== Classes ==

Class name should not contain "-".

== Spacing, indentation, and whitespace ==

Module manifests should follow best practices for spacing, indentation, and whitespace.

Manifests:
* Must use two-space soft tabs,
* Must not use literal tab characters,
* Must not contain trailing whitespace,
* Must include trailing commas after all resource attributes and parameter definitions,
* Must end the last line with a new line,
* Must use one space between the resource type and opening brace, one space between the opening brace and the title, and no spaces between the title and colon.

== Arrays and hashes ==

To increase readability of arrays and hashes, it is almost always beneficial to break up the elements on separate lines.
Use a single line only if that results in overall better readability of the construct where it appears, such as when it is very short. When breaking arrays and hashes, they should have:
* Each element on its on line,
* Each new element line indented one level,
* First and last lines used only for the syntax of that data type.

== Documentation comments ==

Documentation comments for Puppet Strings should be included for each of your classes, defined types, functions, and resource types and providers.
See the [https://docs.puppet.com/puppet/5.0/style_guide.html#documenting-puppet-code documentation section] of this guide for complete documentation recommendations

== Arrow alignment ==

Hash rockets (=>) in a resource’s attribute/value list may be aligned. The hash rockets should be placed one space ahead of the longest attribute name. Nested blocks must be indented by two spaces, and hash rockets within a nested block may be aligned (one space ahead of the longest attribute name).
Each attribute should be placed on a separate line, with the exception that very short or single purpose resource declarations may be declared on a single line.

== Attribute ordering ==

If a resource declaration includes an ensure attribute, it should be the first attribute specified so that a user can quickly see if the resource is being created or deleted.

== File modes ==

* POSIX numeric notation must be represented as 4 digits.
* POSIX symbolic notation must be a string.
* You should not use file mode with Windows; instead use the acl module.
* You should use numeric notation whenever possible.
* The file mode attribute should always be a quoted string, never an integer.

== Resource attribute indentation and alignment ==

Resource attributes must be uniformly indented in two spaces from the title.

== Display order of parameters ==

In parameterized class and defined type declarations, required parameters must be listed before optional parameters (that is, parameters with defaults). Required parameters are parameters which are not set to anything, including undef. For example, parameters such as passwords or IP addresses might not have reasonable default values.

Note that treating a parameter like a namevar and defaulting it to $title or $name does not make it a required parameter. It should still be listed following the order recommended here.

== Parameter indentation and alignment ==

Parameters to classes or defined types must be uniformly indented in two spaces from the title. The equals sign should be aligned.

== Variable format ==

When defining variables you must only use numbers, lowercase letters, and underscores. '''Do not use uppercased letters within a word''', such as “CamelCase”, as it introduces inconsistency in style. You must not use dashes, as they are not syntactically valid.

== Defaults for case statements and selectors ==

Case statements must have default cases. If you want the default case to be “do nothing,” you must include it as an explicit default: {} for clarity’s sake.
Case and selector values must be quoted. Selectors should omit default selections only if you explicitly want catalog compilation to fail when no value matches.

== Documenting Puppet code ==

Use Puppet Strings code comments to document your Puppet classes, defined types, functions, and resource types and providers. Strings processes the README and comments from your code into HTML or JSON format documentation. This allows you and your users to generate detailed documentation for your module.

Include comments for each element (classes, functions, defined types, parameters, and so on) in your module. If used, comments must precede the code for that element. Comments should contain the following information, arranged in this order:

* A description giving an overview of what the element does.
* Any additional information about valid values that is not clear from the data type. (For example, if the data type is [String], but the value must specifically be a path.)
* The default value, if any for that element.

Multiline descriptions must be uniformly indented by at least one space.

For more coding guidelines, please visit [https://docs.puppet.com/puppet/5.0/style_guide.html puppet style guide] page

== Test your code on the local machine ==

Before committing your changes you should check your code with puppet-lint. A lightweight [https://hub.docker.com/r/mozillarelops/puppet-linter/ Docker image] has been created to make this easier, as installing [http://puppet-lint.com/ puppet-lint] natively requires a number of dependencies.

* [https://docs.docker.com/engine/installation/#supported-platforms Install and configure Docker] on your local machine.
* Download the Docker image:
docker pull mozillarelops/puppet-linter
* Run it, inserting the path to your checkout of the puppet repo:
docker run --rm --name puppet-linter -v <path_to_puppet>:/puppet mozillarelops/puppet-linter

= Patch Guidelines / Review Checklist =

== Be Generic ==
PuppetAgain should be usable externally. Do not hard-code things that external users may want to adjust, and extract them from CSV so they can be overridden easily. That includes:
* SSH authorized_keys (note that known_hosts don't hurt)
* usernames (cltbld isn't universal)
* hostnames

== Changes Only ==
Do not write resources that will be instantiated on every puppet run. This makes it difficult to tell if a particular puppet run has actually done anything, and will result in misleading data in the puppet dashboard. Note that the "unless" or "onlyif" parameters to Exec, while they still run an external command (and thus aren't especially efficient), can effectively prevent a command from running.

== Be Modular ==
Keep code where it belongs:
* Node declarations should ''only'' set variables and include toplevel classes (this is looking forward to using an ENC).
* Toplevel classes should ''only'' include other classes, although parameterized classes are OK. Don't do anything substantial directly in a toplevel class -- make a new module and include it.
* Package classes should ''only'' install packages. These classes should be extremely formulaic, and readers should not need to look at them to figure out what they do. Conversely, nothing else should install packages.
* Include requirements near where they are needed. It never hurts to include packages::foo from several places, if foo is used in several places.
* Many modules have a few variables that are needed throughout the module. In this case, make a modulename::settings class that contains only these variables, then include it in all of the classes where those variables are needed.
* In general, more, smaller, more easily-digested classes are better than single, large classes.

== DRY ==
(Don't Repeat Yourself) This applies in a few cases:
* If your action module has a long list of repetitive resources (file, exec, etc.), it can probably be refactored nicely into a utility class or define. This applies even for long lists of ''file'' resources. If that utility class is not purpose-specific, put it in its own module so it can be shared.
* When customizing a configuration file for different purposes, it's tempting to just use several files and ''source => "puppet:///modules/${module_name}/myfile.${purpose}"''. In many cases those files share common code, which will be difficult to keep in sync as it evolves. In this case, prefer to use a template or concatenation to construct the configuration file with the common parts only specified once.

== Use the Toplevel Naming Structure ==
The toplevel naming hierarchy and inheritance hierarchy should be identical. That is, ''toplevel::foo::bar::baz'' should be a subclass of ''toplevel::foo::bar'', which is a subclass of ''toplevel::foo'', which is a subclass of ''toplevel''.

== Common Directories ==
We tend to use the same directories for multiple projects. That's what the ''dirs'' module is for! Creating extra ''dirs'' classes is easy and never hurts. Remember that the class names in this module *exactly* mirror the directory names.

== Packages ==
Remember that we're running puppet on multiple operating systems. If a new package is only required on one operating system, include a ''case $operatingsystem'' and call ''fail()'' in the default branch, so that it will fail loudly if the class is applied on another operating system. If a utility is installed by default on some operating systems, include a clause in the ''case'' with a comment indicating that.

=== DMGs ===
Every DMG's provenance should be documented somehow in the puppet hg repository. For publicly available DMGs, this can be described in the $package.pp file. Otherwise, add a $package-dmg.sh script that builds the DMG from its prerequisites. See [[ReleaseEngineering/PuppetAgain/HowTo/Build_DMGs]].

DMGs that are hand-built but not customized in any way should be installed by packages::xxx, rather than packages::mozilla::xxx. Include the xxx-dmg.sh script in the modules/packages/manifests directory, alongside the manifest file.

=== Custom Packages ===
If you create a custom package, it should be installed with a class named ''python::mozilla::$package'', so it's clear that it's customized. The package should be documented on the [[ReleaseEngineering/PuppetAgain/Modules/packages|packages module page]].

For RPMs, the spec file should be checked into build/puppet in ''modules/packages/manifests/mozilla'', with the same base name as the ''.pp'' file. When you land the changes, the resulting RPM and SRPM should both be added to the appropriate [[ReleaseEngineering/PuppetAgain/Repositories|repository]]. The contents (but maybe not filename) of the spec file embedded in the SRPM should match the checked-in spec file exactly. This system allows (a) review of spec changes and (b) easy rebuilding of custom RPMS. See [[ReleaseEngineering/PuppetAgain/HowTo/Modify a Custom RPM]] for hints on how to build RPMs.

== Strong Dependencies ==
Wherever a dependency might exist, specify it. Dependency errors are difficult to spot when you're incrementally building a system as you develop your patch. Unspecified dependencies can even work in production -- for a while, until a new and unrelated resource shakes up the nondeterministic ordering and suddenly things don't work.

=== Graphs ===
You can get puppet to give you a dependency graph in .dot format! See http://bitfieldconsulting.com/puppet-dependency-graphs - although the results are enormous and due to some puppet bugs not that helpful.
yum install graphviz
dot -Tpng /var/lib/puppet/state/graphs/expanded_relationships.dot > relationships.png
Note that in current versions of puppet, these are fairly unusable, as they show all relationships as bidirectional.

=== Class Dependencies ===
In general, try to use ''require => Class['some::class']'' rather than requiring a basic resource that you know the class defines (especially avoid ''require => Package['some-package']''). This way, you are not depending on an implementation detail of that other class. This also creates many more dependencies (on all of the concrete resources in that class), which keeps things predictable.

Unfortunately, these dependencies do *not* extend to included classes. See [[ReleaseEngineering/PuppetAgain/Anchoring Classes]] for the workaround. Every class that can be required by another class (which are explicitly labeled as such in the wiki) should be anchored.

=== Tips ===
Keep in mind that puppet automatically requires parent directories, so ''File['/builds/slave']'' automatically requires ''File['/builds']'' if it exists. Also, note that in many cases packages will write default configuration files when they are installed, so you should make sure that the File resource installing the custom configuration requires the package class.

== Document ==
Adjust/amend the documentation on the wiki while landing the change after review.

== No Bad Habits ==
* Even if all of the FooAPI servers are running OpenSolaris, $::operatingsystem=="Solaris" does not mean this is a FooAPI server. OS does not imply role. Roles are defined in node declarations, by including <tt>toplevel::*</tt> classes.
* It can be tempting to put "just one resource" into an already-existing class. User::builder seems to be a popular target. Adding new classes is easy, and avoids surprises. If the resource you're adding isn't obviously tied to the name of the class you're adding it to, put it in another (probably new) class.

== Config Files ==
* For file-resources where you can easily implement a run-parts format design, do so, rather than modify the global config.
** Examples crontab vs cron.d/*, http.d.
* You should specify the parent dir to purge and recursive, so that when you remove a resource from puppet it removes itself from the machine.
* The crontab resource has complex gotchyas - *always* use /etc/cron.d/* files for cron.
* When installing files that might be executed immediately, e.g., crontabs or application scripts, use ''require'' to ensure that all prerequisites are installed first, to avoid unnecessary failures.

== Revertible ==
Where it's not too difficult, try to write classes so that *removing* a resource will cause a corresponding removal on clients. For example, when ''sudoers::custom { foo: command => "foo" }'' is removed from a client's catalog, the 'foo' command can no longer be run from sudo. To do otherwise could cause nasty security problems!

== Syntax ==
Puppet gets a little unpredictable around what it does and does not allow in names. To be safe, stick with [a-zA-Z_][a-zA-Z0-9_] for class and variable names, just like C identifiers. In particular, do not use '-' in class or variable names (the latter won't work; the former will almost work but is [http://docs.puppetlabs.com/learning/modules1.html#an-aside-names-namespaces-and-scope illegal]).

== Nit-Worthy Code Style ==

While everyone will have different opinions on the best Coding Style, one thing we can all agree on, life is better when we all agree. So the following are Nit's we should all strive to adhere to, but exceptions can be made with good reasoning. (mistakes can sneak in, if so, just edit them out next time you touch that area of code)

=== Whitespace and Tabs ===

* '''TABS''': NEVER in a puppet manifest file. ONLY when necessary in other files.
* '''Trailing Whitespace''': Shouldn't exist.
* '''EOL''': Always Unix style line-endings.
* '''EOF''': Always include a newline at EOF
* '''Indentation''': Four Space indents.

=== Comments ===

* We prefer the <code>#</code> style comments throughout, C-Style is frowned upon.
* Manifests that are not very obvious by their name should have a very brief comment at the top of the file describing it, these comments are informative, normative reference is the wiki docs.
* When it helps understanding of why something is in the manifest (or not in the manifest) please include brief comment saying so.

== Tips ==
In a template, if you have a variable that may be a single value or an array, and you need it to be an array, use
Array(@var)
to convert it to an array. If the array may be created from other arrays in the puppet DSL (which does not support concatenation of arrays), use
Array(@var).flatten

= Landing Changes =

Before you land your changes, think carefully about the ramifications. There are some common gotchas with Puppet:

== Changing Puppet Config ==

If your change requires changes to puppet.conf or related files, be sure it applies fresh! As an example, landing a change that requires a plugin, and setting ''pluginsync = true'' at the same time will likely not work -- the puppet.conf change will not be made if the catalog compilation fails due to the missing plugin. This particular case has been addressed (pluginsync is already enabled), but be alert to similar situations.

== Adding Packages ==

When adding packages, be aware that the order in which the packages and your updated manifests are applied is difficult to ensure.

Most packages are installed with ''ensure => latest'', which will upgrade the packages on a client during the next puppet run *iff* the packages are synchronized to the relevant puppetmaster *and* the repository cache on that client is cleared (see [[ReleaseEngineering/PuppetAgain/Modules/packages]]). Without this, it's quite likely that ''puppet agent'' will run successfully without upgrading the packages. On the other hand, the ''ensure => latest'' can also cause upgrades to occur before the corresponding manifest changes are committed to hg.

There are a few ways to work around this. One is to -- at least temporarily -- specify an exact version of the package in the manifests. Then puppet runs will fail in any corner cases, preventing further damage.

DeveloperServices

2017-07-18T15:29:19Z

Klibby: /* Oncall for VCS */ update oncall

<section begin=summary />{{TeamSummary
|teamtitle=Developer Services
|teampagelocation=DeveloperServices
|teamlead=Kendall Libby
|mailinglist=developer-services@mozilla.org
|description=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.
}}<section end=summary />

= 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.
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Role'''
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''IRC Contact'''
|-
| Primary
| Kendall Libby
| fubar
|-
| Backup on call
| Jacob Watkins
| dividehex
|-
| 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|contact info]] below.

= Roster =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''Contact'''
| style="background:#EFEFEF;" | '''Location'''
| style="background:#EFEFEF;" | '''Project(s)'''
| style="background:#EFEFEF;" | '''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
|}

<div id="contact"> </div>
To contact all of the above, use the list developer-services@mozilla.org or [ircs://irc.mozilla.org/#vcs #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 [ircs://irc.mozilla.org/#vcs #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:
* [ircs://irc.mozilla.org/#bteam #bteam] for BMO
* [ircs://irc.mozilla.org/#treeherder #treeherder] for Treeherder ([https://groups.google.com/forum/#!forum/mozilla.tools.treeherder discussion list])
* [ircs://irc.mozilla.org/#mozreview #mozreview] for MozReview
* [ircs://irc.mozilla.org/#static #static] for DXR

= Meetings =
* [[DeveloperServices/TeamMeetings|https://wiki.mozilla.org/DeveloperServices/TeamMeetings]]

= Services =
* [[/Account Recovery]] - how to re-enable account access
* [[/git]] - details of our Git DVCS system
* [[/hg]] - details of our Mercurial DVCS system

DeveloperServices

2017-06-29T17:30:52Z

Klibby: /* Oncall for VCS */ update oncall

<section begin=summary />{{TeamSummary
|teamtitle=Developer Services
|teampagelocation=DeveloperServices
|teamlead=Kendall Libby
|mailinglist=developer-services@mozilla.org
|description=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.
}}<section end=summary />

= 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.
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Role'''
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''IRC Contact'''
|-
| Primary
| Dave House
| dhouse
|-
| Backup on call
| Jacob Watkins
| dividehex
|-
| 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|contact info]] below.

= Roster =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''Contact'''
| style="background:#EFEFEF;" | '''Location'''
| style="background:#EFEFEF;" | '''Project(s)'''
| style="background:#EFEFEF;" | '''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
|}

<div id="contact"> </div>
To contact all of the above, use the list developer-services@mozilla.org or [ircs://irc.mozilla.org/#vcs #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 [ircs://irc.mozilla.org/#vcs #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:
* [ircs://irc.mozilla.org/#bteam #bteam] for BMO
* [ircs://irc.mozilla.org/#treeherder #treeherder] for Treeherder ([https://groups.google.com/forum/#!forum/mozilla.tools.treeherder discussion list])
* [ircs://irc.mozilla.org/#mozreview #mozreview] for MozReview
* [ircs://irc.mozilla.org/#static #static] for DXR

= Meetings =
* [[DeveloperServices/TeamMeetings|https://wiki.mozilla.org/DeveloperServices/TeamMeetings]]

= Services =
* [[/Account Recovery]] - how to re-enable account access
* [[/git]] - details of our Git DVCS system
* [[/hg]] - details of our Mercurial DVCS system

BMO/Meetings/2017-02-28

2017-02-28T16:40:35Z

Klibby: Add cloud ops migration section

== OKRs ==
* user survey {{bug|1339290}}
** Awaiting word from Travis on survey
** Lifecycle Marketing will send survey next week
** Status on sample
* reduce time spent developing user forms
** Q1 time spent thus far: 2

== Project Updates ==
* Modal View, {{bug|1150541}}
* Elasticsearch, {{bug|1307485}}
* Emoji/utf8mb4, {{bug|1253535}}
** check if we can ask MySQL server if it supports the features we need at the time we a commit push

== What Are We Working on This Week? ==
* emceeaich: finish getting survey out, continue on regressions work
* dylan:

== Operations ==
* Cloud Ops migration
** Performance and component/version data gathering, {{bug|1339516}}

== Other Updates ==

* Trying to retire outdated flags {{bug|1343137}}
* Bi-weekly BMO triage starting this week (all open, untriaged bugs since 2016-06-01)

=== Outreachy/GSoC ===

DeveloperServices

2016-12-20T16:36:00Z

Klibby: update oncall

<section begin=summary />{{TeamSummary
|teamtitle=Developer Services
|teampagelocation=DeveloperServices
|teamlead=Kendall Libby
|mailinglist=developer-services@mozilla.org
|description=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.
}}<section end=summary />

= 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.
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Role'''
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''IRC Contact'''
|-
| Primary
| Kendall Libby
| fubar
|-
| Backup on call
| Jacob 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|contact info]] below.

= Roster =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''Contact'''
| style="background:#EFEFEF;" | '''Location'''
| style="background:#EFEFEF;" | '''Project(s)'''
| style="background:#EFEFEF;" | '''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
|}

<div id="contact"> </div>
To contact all of the above, use the list developer-services@mozilla.org or [ircs://irc.mozilla.org/#vcs #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 [ircs://irc.mozilla.org/#vcs #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:
* [ircs://irc.mozilla.org/#bteam #bteam] for BMO
* [ircs://irc.mozilla.org/#treeherder #treeherder] for Treeherder ([https://groups.google.com/forum/#!forum/mozilla.tools.treeherder discussion list])
* [ircs://irc.mozilla.org/#mozreview #mozreview] for MozReview
* [ircs://irc.mozilla.org/#static #static] for DXR

= Meetings =
* [[DeveloperServices/TeamMeetings|https://wiki.mozilla.org/DeveloperServices/TeamMeetings]]

= Services =
* [[/Account Recovery]] - how to re-enable account access
* [[/git]] - details of our Git DVCS system
* [[/hg]] - details of our Mercurial DVCS system

DeveloperServices

2016-09-07T17:57:48Z

Klibby: update roster, services

<section begin=summary />{{TeamSummary
|teamtitle=Developer Services
|teampagelocation=DeveloperServices
|teamlead=Kendall Libby
|mailinglist=developer-services@mozilla.org
|description=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.
}}<section end=summary />

= 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.
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Role'''
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''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|contact info]] below.

= Roster =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''Contact'''
| style="background:#EFEFEF;" | '''Location'''
| style="background:#EFEFEF;" | '''Project(s)'''
| style="background:#EFEFEF;" | '''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
|}

<div id="contact"> </div>
To contact all of the above, use the list developer-services@mozilla.org or [ircs://irc.mozilla.org/#vcs #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 [ircs://irc.mozilla.org/#vcs #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:
* [ircs://irc.mozilla.org/#bteam #bteam] for BMO
* [ircs://irc.mozilla.org/#treeherder #treeherder] for Treeherder ([https://groups.google.com/forum/#!forum/mozilla.tools.treeherder discussion list])
* [ircs://irc.mozilla.org/#mozreview #mozreview] for MozReview
* [ircs://irc.mozilla.org/#static #static] for DXR

= Meetings =
* [[DeveloperServices/TeamMeetings|https://wiki.mozilla.org/DeveloperServices/TeamMeetings]]

= Services =
* [[/Account Recovery]] - how to re-enable account access
* [[/git]] - details of our Git DVCS system
* [[/hg]] - details of our Mercurial DVCS system

DeveloperServices

2016-06-16T08:30:18Z

Klibby: update oncall

<section begin=summary />{{TeamSummary
|teamtitle=Developer Services
|teampagelocation=DeveloperServices
|teamlead=Kendall Libby
|mailinglist=developer-services@mozilla.org
|description=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.
}}<section end=summary />

= 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.
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Role'''
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''IRC Contact'''
|-
| Primary
| Kendall Libby
| fubar
|-
| Backup on call
| 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|contact info]] below.

= Roster =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''Contact'''
| style="background:#EFEFEF;" | '''Location'''
| style="background:#EFEFEF;" | '''Project(s)'''
| style="background:#EFEFEF;" | '''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
|}

<div id="contact"> </div>
To contact all of the above, use the list developer-services@mozilla.org or [ircs://irc.mozilla.org/#vcs #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 [ircs://irc.mozilla.org/#vcs #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:
* [ircs://irc.mozilla.org/#bteam #bteam] for BMO
* [ircs://irc.mozilla.org/#treeherder #treeherder] for Treeherder ([https://groups.google.com/forum/#!forum/mozilla.tools.treeherder discussion list])
* [ircs://irc.mozilla.org/#mozreview #mozreview] for MozReview
* [ircs://irc.mozilla.org/#static #static] for DXR
* There is no help to be found for MXR. Abandon all hope, etc, etc.

= Meetings =
* [[DeveloperServices/TeamMeetings|https://wiki.mozilla.org/DeveloperServices/TeamMeetings]]

= Services =
* [[/Account Recovery]] - how to re-enable account access
* [[/git]] - details of our Git DVCS system
* [[/hg]] - details of our Mercurial DVCS system

DeveloperServices

2016-06-07T18:40:37Z

Klibby: update oncall

<section begin=summary />{{TeamSummary
|teamtitle=Developer Services
|teampagelocation=DeveloperServices
|teamlead=Kendall Libby
|mailinglist=developer-services@mozilla.org
|description=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.
}}<section end=summary />

= 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.
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Role'''
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''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|contact info]] below.

= Roster =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''Contact'''
| style="background:#EFEFEF;" | '''Location'''
| style="background:#EFEFEF;" | '''Project(s)'''
| style="background:#EFEFEF;" | '''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
|}

<div id="contact"> </div>
To contact all of the above, use the list developer-services@mozilla.org or [ircs://irc.mozilla.org/#vcs #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 [ircs://irc.mozilla.org/#vcs #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:
* [ircs://irc.mozilla.org/#bteam #bteam] for BMO
* [ircs://irc.mozilla.org/#treeherder #treeherder] for Treeherder ([https://groups.google.com/forum/#!forum/mozilla.tools.treeherder discussion list])
* [ircs://irc.mozilla.org/#mozreview #mozreview] for MozReview
* [ircs://irc.mozilla.org/#static #static] for DXR
* There is no help to be found for MXR. Abandon all hope, etc, etc.

= Meetings =
* [[DeveloperServices/TeamMeetings|https://wiki.mozilla.org/DeveloperServices/TeamMeetings]]

= Services =
* [[/Account Recovery]] - how to re-enable account access
* [[/git]] - details of our Git DVCS system
* [[/hg]] - details of our Mercurial DVCS system

DeveloperServices

2016-04-21T15:32:27Z

Klibby: update oncall

<section begin=summary />{{TeamSummary
|teamtitle=Developer Services
|teampagelocation=DeveloperServices
|teamlead=Kendall Libby
|mailinglist=developer-services@mozilla.org
|description=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.
}}<section end=summary />

= 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.
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Role'''
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''IRC Contact'''
|-
| Primary
| Kendall Libby
| fubar
|-
| Backup on call
| 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|contact info]] below.

= Roster =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''Contact'''
| style="background:#EFEFEF;" | '''Location'''
| style="background:#EFEFEF;" | '''Project(s)'''
| style="background:#EFEFEF;" | '''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
|}

<div id="contact"> </div>
To contact all of the above, use the list developer-services@mozilla.org or [ircs://irc.mozilla.org/#vcs #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 [ircs://irc.mozilla.org/#vcs #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:
* [ircs://irc.mozilla.org/#bteam #bteam] for BMO
* [ircs://irc.mozilla.org/#treeherder #treeherder] for Treeherder ([https://groups.google.com/forum/#!forum/mozilla.tools.treeherder discussion list])
* [ircs://irc.mozilla.org/#mozreview #mozreview] for MozReview
* [ircs://irc.mozilla.org/#static #static] for DXR
* There is no help to be found for MXR. Abandon all hope, etc, etc.

= Meetings =
* [[DeveloperServices/TeamMeetings|https://wiki.mozilla.org/DeveloperServices/TeamMeetings]]

= Services =
* [[/Account Recovery]] - how to re-enable account access
* [[/git]] - details of our Git DVCS system
* [[/hg]] - details of our Mercurial DVCS system

DeveloperServices

2016-04-14T19:39:18Z

Klibby: update oncall

<section begin=summary />{{TeamSummary
|teamtitle=Developer Services
|teampagelocation=DeveloperServices
|teamlead=Lawrence Mandel
|mailinglist=developer-services@mozilla.org
|description=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.
}}<section end=summary />

= 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.
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Role'''
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''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|contact info]] below.

= Roster =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''Contact'''
| style="background:#EFEFEF;" | '''Location'''
| style="background:#EFEFEF;" | '''Project(s)'''
| style="background:#EFEFEF;" | '''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
|}

<div id="contact"> </div>
To contact all of the above, use the list developer-services@mozilla.org or [ircs://irc.mozilla.org/#vcs #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 [ircs://irc.mozilla.org/#vcs #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:
* [ircs://irc.mozilla.org/#bteam #bteam] for BMO
* [ircs://irc.mozilla.org/#treeherder #treeherder] for Treeherder ([https://groups.google.com/forum/#!forum/mozilla.tools.treeherder discussion list])
* [ircs://irc.mozilla.org/#mozreview #mozreview] for MozReview
* [ircs://irc.mozilla.org/#static #static] for DXR
* There is no help to be found for MXR. Abandon all hope, etc, etc.

= Projects =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Project Name'''
| style="background:#EFEFEF;" |'''Description'''
| style="background:#EFEFEF;" | '''Primary Contact'''
|-
| [http://example.com project]
| This project does something
| laura@mozilla.com
|}

= Meetings =
* [[DeveloperServices/TeamMeetings|https://wiki.mozilla.org/DeveloperServices/TeamMeetings]]

= Services =
* [[/Account Recovery]] - how to re-enable account access
* [[/git]] - details of our Git DVCS system
* [[/hg]] - details of our Mercurial DVCS system

DeveloperServices

2016-03-02T14:48:47Z

Klibby: update oncall

<section begin=summary />{{TeamSummary
|teamtitle=Developer Services
|teampagelocation=DeveloperServices
|teamlead=Lawrence Mandel
|mailinglist=developer-services@mozilla.org
|description=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.
}}<section end=summary />

= 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.
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Role'''
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''IRC Contact'''
|-
| Primary
| Kendall Libby
| fubar
|-
| Backup on call
| Hal Wine
| hwine
|-
| Escalation
| Mark Côté
| mcote
|}
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.

= Roster =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''Contact'''
| style="background:#EFEFEF;" | '''Location'''
| style="background:#EFEFEF;" | '''Project(s)'''
| style="background:#EFEFEF;" | '''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
|}

<div id="contact"> </div>
To contact all of the above, use the list developer-services@mozilla.org or [ircs://irc.mozilla.org/#vcs #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 [ircs://irc.mozilla.org/#vcs #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:
* [ircs://irc.mozilla.org/#bteam #bteam] for BMO
* [ircs://irc.mozilla.org/#treeherder #treeherder] for Treeherder ([https://groups.google.com/forum/#!forum/mozilla.tools.treeherder discussion list])
* [ircs://irc.mozilla.org/#mozreview #mozreview] for MozReview
* [ircs://irc.mozilla.org/#static #static] for DXR
* There is no help to be found for MXR. Abandon all hope, etc, etc.

= Projects =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Project Name'''
| style="background:#EFEFEF;" |'''Description'''
| style="background:#EFEFEF;" | '''Primary Contact'''
|-
| [http://example.com project]
| This project does something
| laura@mozilla.com
|}

= Meetings =
* [[DeveloperServices/TeamMeetings|https://wiki.mozilla.org/DeveloperServices/TeamMeetings]]

= Services =
* [[/Account Recovery]] - how to re-enable account access
* [[/git]] - details of our Git DVCS system
* [[/hg]] - details of our Mercurial DVCS system

BMO/Meetings/2016-02-09

2016-02-08T21:03:42Z

Klibby: Created page with "* [fubar] perl packaging hell"

* [fubar] perl packaging hell

BMO/Meetings

2016-02-08T21:02:52Z

Klibby: add 2Feb link

BMO meetings are held [http://arewemeetingyet.com/Toronto/2015-05-05/11:30/w/BMO%20meeting every Tuesday at 11:30 AM EST/EDT], in The A-Team Vidyo Room (8416), [[Teleconferencing|Dial-in]] room number 8416?.

We often cancel meetings if there are no agenda items; admittedly, sometimes this decision is made rather late. We generally announce cancellations in the #bteam channel on irc.mozilla.org.

Minutes:

==2016==
* [[BMO/Meetings/2016-02-09|2016 Feb 09]]
* 2016 Feb 02 cancelled for lack of agenda items
* 2016 Jan 26 cancelled due to several people on PTO.
* 2016 Jan 19 cancelled for lack of agenda items
* [[BMO/Meetings/2016-01-12|2016 Jan 12]]
* [[BMO/Meetings/2016-01-05|2016 Jan 05]]

==2015==
* 2015 Dec 15 cancelled for lack of agenda items
* 2015 Dec 08 cancelled for Mozlando
* [[BMO/Meetings/2015-12-01|2015 Dec 01]]
* [[BMO/Meetings/2015-11-24|2015 Nov 24]]
* [[BMO/Meetings/2015-11-17|2015 Nov 17]]
* [[BMO/Meetings/2015-11-03|2015 Nov 03]]
* [[BMO/Meetings/2015-10-27|2015 Oct 27]]
* [[BMO/Meetings/2015-10-20|2015 Oct 20]]
* [[BMO/Meetings/2015-10-13|2015 Oct 13]] cancelled (agenda items carried forward)
* [[BMO/Meetings/2015-10-06|2015 Oct 06]]
* [[BMO/Meetings/2015-09-29|2015 Sep 29]]
* [[BMO/Meetings/2015-09-22|2015 Sep 22]]
* 2015 Sep 15 cancelled for lack of agenda items
* [[BMO/Meetings/2015-09-08|2015 Sep 08]]
* 2015 Sep 01 cancelled for lack of agenda items
* [[BMO/Meetings/2015-08-25|2015 Aug 25]]
* [[BMO/Meetings/2015-08-18|2015 Aug 18]]
* [[BMO/Meetings/2015-08-11|2015 Aug 11]]
* [[BMO/Meetings/2015-08-04|2015 Aug 04]]
* [[BMO/Meetings/2015-07-28|2015 Jul 28]]
* [[BMO/Meetings/2015-07-21|2015 Jul 21]]
* [[BMO/Meetings/2015-07-14|2015 Jul 14]]
* [[BMO/Meetings/2015-07-07|2015 Jul 07]]
* 2015 Jun 30 cancelled due to Whistler week recovery
* 2015 Jun 23 cancelled due to Whistler week
* [[BMO/Meetings/2015-06-16|2015 Jun 16]]
* [[BMO/Meetings/2015-06-09|2015 Jun 09]]
* [[BMO/Meetings/2015-06-02|2015 Jun 02]]
* [[BMO/Meetings/2015-05-26|2015 May 26]]
* 2015 May 19 cancelled for lack of agenda items
* [[BMO/Meetings/2015-05-12|2015 May 12]]
* 2015 May 05 cancelled for lack of agenda items
* [[BMO/Meetings/2015-04-28|2015 Apr 28]]
* 2015 Apr 21 cancelled for lack of agenda items
* [[BMO/Meetings/2015-04-14|2015 Apr 14]]
* [[BMO/Meetings/2015-04-07|2015 Apr 07]]
* 2015 Mar 31 -- cancelled for lack of agenda items
* [[BMO/Meetings/2015-03-24|2015 Mar 24]]
* [[BMO/Meetings/2015-03-17|2015 Mar 17]]
* [[BMO/Meetings/2015-03-10|2015 Mar 10]]
* [[BMO/Meetings/2015-03-03|2015 Mar 03]]
* [[BMO/Meetings/2015-02-24|2015 Feb 24]]
* [[BMO/Meetings/2015-02-17|2015 Feb 17]]
* [[BMO/Meetings/2015-02-10|2015 Feb 10]]
* [[BMO/Meetings/2015-02-03|2015 Feb 03]]
* [[BMO/Meetings/2015-01-27|2015 Jan 27]]
* [[BMO/Meetings/2015-01-20|2015 Jan 20]]
* [[BMO/Meetings/2015-01-13|2015 Jan 13]]
* [[BMO/Meetings/2015-01-06|2015 Jan 06]]

==2014==
* [[BMO/Meetings/2014-11-25|2014 Nov 25]]
* [[BMO/Meetings/2014-11-18|2014 Nov 18]]
* [[BMO/Meetings/2014-11-11|2014 Nov 11]]
* [[BMO/Meetings/2014-11-04|2014 Nov 04]]
* [[BMO/Meetings/2014-10-21|2014 Oct 21]]
* [[BMO/Meetings/2014-09-30|2014 Sep 30]]
* [[BMO/Meetings/2014-09-23|2014 Sep 23]]
* [[BMO/Meetings/2014-09-16|2014 Sep 16]]
* [[BMO/Meetings/2014-09-02|2014 Sep 02]]
* [[BMO/Meetings/2014-08-26|2014 Aug 26]]
* [[BMO/Meetings/2014-08-12|2014 Aug 12]]
* [[BMO/Meetings/2014-07-22|2014 Jul 22]]
* [[BMO/Meetings/2014-07-15|2014 Jul 15]]
* [[BMO/Meetings/2014-07-08|2014 Jul 8]]
* [[BMO/Meetings/2014-06-10|2014 Jun 10]]
* [[BMO/Meetings/2014-06-03|2014 Jun 3]]
* [[BMO/Meetings/2014-05-27|2014 May 27]]
* [[BMO/Meetings/2014-05-20|2014 May 20]]
* [[BMO/Meetings/2014-05-13|2014 May 13]]
* [[BMO/Meetings/2014-05-06|2014 May 6]]
* [[BMO/Meetings/2014-04-29|2014 Apr 29]]
* [[BMO/Meetings/2014-04-22|2014 Apr 22]]
* 2014 Apr 15 - cancelled for No Meeting Week
* [[BMO/Meetings/2014-04-08|2014 Apr 8]]
* [[BMO/Meetings/2014-04-01|2014 Apr 1]]
* [[BMO/Meetings/2014-03-25|2014 Mar 25]]
* [[BMO/Meetings/2014-03-11|2014 Mar 11]]
* [[BMO/Meetings/2014-03-05|2014 Mar 5]]
* [[BMO/Meetings/2014-02-04|2014 Feb 4]]
* [[BMO/Meetings/2014-01-28|2014 Jan 28]]
* [[BMO/Meetings/2014-01-14|2014 Jan 14]]

==2013==
* [[BMO/Meetings/2013-12-10|2013 Dec 10]]
* [[BMO/Meetings/2013-12-03|2013 Dec 3]]
* [[BMO/Meetings/2013-11-19|2013 Nov 19]]
* [[BMO/Meetings/2013-11-12|2013 Nov 12]]
* [[BMO/Meetings/2013-11-05|2013 Nov 5]]
* [[BMO/Meetings/2013-10-29|2013 Oct 29]]
* [[BMO/Meetings/2013-10-22|2013 Oct 22]]
* [[BMO/Meetings/2013-10-15|2013 Oct 15]]
* [[BMO/Meetings/2013-09-17|2013 Sep 17]]
* [[BMO/Meetings/2013-09-10|2013 Sep 10]]
* [[BMO/Meetings/2013-09-03|2013 Sep 03]]
* [[BMO/Meetings/2013-08-27|2013 Aug 27]]
* [[BMO/Meetings/2013-08-20|2013 Aug 20]]
* [[BMO/Meetings/2013-08-13|2013 Aug 13]]
* [[BMO/Meetings/2013-07-30|2013 July 30]]
* [[BMO/Meetings/2013-07-23|2013 July 23]]
* [[BMO/Meetings/2013-07-16|2013 July 16]]
* [[BMO/Meetings/2013-07-09|2013 July 9]]
* [[BMO/Meetings/2013-07-02|2013 July 2]]
* [[BMO/Meetings/2013-06-24|2013 June 24]]
* [[BMO/Meetings/2013-06-18|2013 June 18]]
* [[BMO/Meetings/2013-06-10|2013 June 10]]
* [[BMO/Meetings/2013-06-03|2013 June 3]]
* [[BMO/Meetings/2013-05-21|2013 May 21]] (moved from May 20)
* [[BMO/Meetings/2013-05-13|2013 May 13]]
*
* [[BMO/Meetings/2013-04-29|2013 Apr 29]]
* [[BMO/Meetings/2013-04-22|2013 Apr 22]]
* [[BMO/Meetings/2013-04-15|2013 Apr 15]]
* [[BMO/Meetings/2013-04-08|2013 Apr 8]]
* [[BMO/Meetings/2013-04-02|2013 Apr 2]] (moved from Apr. 1)
* [[BMO/Meetings/2013-03-26|2013 Mar 26]]
* [[BMO/Meetings/2013-03-19|2013 Mar 19]]
* [[BMO/Meetings/2013-03-11|2013 Mar 11]]
* [[BMO/Meetings/2013-03-04|2013 Mar 4]]
* [[BMO/Meetings/2013-02-18|2013 Feb 18]]
* [[BMO/Meetings/2013-02-11|2013 Feb 11]]
* [[BMO/Meetings/2013-01-28|2013 Jan 28]]
* [[BMO/Meetings/2013-01-14|2013 Jan 14]]
* [[BMO/Meetings/2013-01-07|2013 Jan 7]]

==2012==
* [[BMO/Meetings/2012-11-26|2012 Nov 26]]
* [[BMO/Meetings/2012-11-19|2012 Nov 19]]
* [[BMO/Meetings/2012-11-05|2012 Nov 05]]
* [[BMO/Meetings/2012-10-22|2012 Oct 22]]
* [[BMO/Meetings/2012-10-15|2012 Oct 15]]
* [[BMO/Meetings/2012-10-01|2012 Oct 1]]
* [[BMO/Meetings/2012-09-10|2012 Sept 10]]
* [[BMO/Meetings/2012-09-04|2012 Sept 4]]
* [[BMO/Meetings/2012-08-21|2012 Aug 21]] (moved from 2012 Aug 20)
* 2012 Aug 13 - skipped due to illness
* [[BMO/Meetings/2012-08-06|2012 Aug 6]]
* [[BMO/Meetings/2012-07-30|2012 July 30]]
* [[BMO/Meetings/2012-07-23|2012 July 23]]
* [[BMO/Meetings/2012-07-16|2012 July 16]]
* [[BMO/Meetings/2012-07-09|2012 July 09]]
* [[BMO/Meetings/2012-07-02|2012 July 02]]
* [[BMO/Meetings/2012-06-25|2012 June 25]]
* [[BMO/Meetings/2012-06-18|2012 June 18]]
* [[BMO/Meetings/2012-06-11|2012 June 11]]
* [[BMO/Meetings/2012-06-04|2012 June 4]]
* [[BMO/Meetings/2012-05-21|2012 May 21]]
* [[BMO/Meetings/2012-05-14|2012 May 14]]
* [[BMO/Meetings/2012-05-07|2012 May 07]]
* [[BMO/Meetings/2012-04-30|2012 Apr 30]]

==Long ago==
* [[BMO/Meetings/2011-01-05|2011 Jan 05]]
* [[BMO/Meetings/2010-12-22|2010 Dec 22]]
* [[BMO/Meetings/WorkWeekBOF201104| Work Week April 2011- BMO BOF]]

[[Category:BMO]]

BMO/Meetings/2015-10-27

2015-10-27T14:02:56Z

Klibby: add agenda item

* [dylan] Some bits about group owners
* [dylan] Ed asks [https://bugzilla.mozilla.org/show_bug.cgi?id=1021795#c6 if we have a metabug for BMO performance work].
* [glob] aws/bmo "new requirements"
* [fubar] new BMO certificate

DeveloperServices

2015-09-21T18:26:38Z

Klibby: update oncall

<section begin=summary />{{TeamSummary
|teamtitle=Developer Services
|teampagelocation=DeveloperServices
|teamlead=Lawrence Mandel
|mailinglist=developer-services@mozilla.org
|description=The Developer Services team works on version control systems and related tools at Mozilla.
* We work on hg, git, svn, cvs, and bzr.
* We support the try repository.
* We also provide operational support for BMO, MozReview, Treeherder, MXR, and DXR.
}}<section end=summary />

= 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.
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Role'''
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''IRC Contact'''
|-
| Primary
| Kendall Libby
| fubar
|-
| Backup on call
| Hal Wine
| hwine
|-
| Escalation
| Mark Coté
| mcote
|}
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.

= Roster =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''Contact'''
| style="background:#EFEFEF;" | '''Location'''
| style="background:#EFEFEF;" | '''Project(s)'''
| style="background:#EFEFEF;" | '''Working Hours'''
|-
|Kendall Libby
|fubar
|Boston, MA, USA
|BMO, Treeherder, Reviewboard, DXR, MXR, hg, git
|EST
|-
|Gregory Szorc
|gps
|Vancouver, BC, Canada
|hg, Reviewboard, build module owner
|PST
|-
|Hal Wine (on loan from RelEng)
|hwine
|San Francisco, CA, USA
|VCSs, releng and IT liaison
|PST
|}

<div id="contact"> </div>
To contact all of the above, use the list developer-services@mozilla.org or [ircs://irc.mozilla.org/#vcs #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 [ircs://irc.mozilla.org/#vcs #vcs].

For general help with the systems we support, try:
* [ircs://irc.mozilla.org/#bteam #bteam] for BMO
* [ircs://irc.mozilla.org/#treeherder #treeherder] for Treeherder
* [ircs://irc.mozilla.org/#mozreview #mozreview] for MozReview
* [ircs://irc.mozilla.org/#static #static] for DXR
* There is no help to be found for MXR. Abandon all hope, etc, etc.

= Projects =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Project Name'''
| style="background:#EFEFEF;" |'''Description'''
| style="background:#EFEFEF;" | '''Primary Contact'''
|-
| [http://example.com project]
| This project does something
| laura@mozilla.com
|}

= Meetings =
* [[DeveloperServices/TeamMeetings|https://wiki.mozilla.org/DeveloperServices/TeamMeetings]]

= Services =
* [[/Account Recovery]] - how to re-enable account access
* [[/git]] - details of our Git DVCS system
* [[/hg]] - details of our Mercurial DVCS system

DeveloperServices

2015-08-24T21:14:01Z

Klibby: flip oncall

<section begin=summary />{{TeamSummary
|teamtitle=Developer Services
|teampagelocation=DeveloperServices
|teamlead=Lawrence Mandel
|mailinglist=developer-services@mozilla.org
|description=The Developer Services team works on version control systems and related tools at Mozilla.
* We work on hg, git, svn, cvs, and bzr.
* We support the try repository.
* We also provide operational support for BMO, MozReview, Treeherder, MXR, and DXR.
}}<section end=summary />

= 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.
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Role'''
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''IRC Contact'''
|-
| Primary
| Kendall Libby
| fubar
|-
| Backup on call
| Hal Wine
| hwine
|-
| Escalation
| Mark Coté
| mcote
|}
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.

= Roster =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''Contact'''
| style="background:#EFEFEF;" | '''Location'''
| style="background:#EFEFEF;" | '''Project(s)'''
| style="background:#EFEFEF;" | '''Working Hours'''
|-
|Kendall Libby
|fubar
|Boston, MA, USA
|BMO, Treeherder, Reviewboard, DXR, MXR, hg, git
|EST
|-
|Gregory Szorc
|gps
|Vancouver, BC, Canada
|hg, Reviewboard, build module owner
|PST
|-
|Hal Wine (on loan from RelEng)
|hwine
|San Francisco, CA, USA
|VCSs, releng and IT liaison
|PST
|}

<div id="contact"> </div>
To contact all of the above, use the list developer-services@mozilla.org or [ircs://irc.mozilla.org/#vcs #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 [ircs://irc.mozilla.org/#vcs #vcs].

For general help with the systems we support, try:
* [ircs://irc.mozilla.org/#bteam #bteam] for BMO
* [ircs://irc.mozilla.org/#treeherder #treeherder] for Treeherder
* [ircs://irc.mozilla.org/#mozreview #mozreview] for MozReview
* [ircs://irc.mozilla.org/#static #static] for DXR
* There is no help to be found for MXR. Abandon all hope, etc, etc.

= Projects =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Project Name'''
| style="background:#EFEFEF;" |'''Description'''
| style="background:#EFEFEF;" | '''Primary Contact'''
|-
| [http://example.com project]
| This project does something
| laura@mozilla.com
|}

= Meetings =
* [[DeveloperServices/TeamMeetings|https://wiki.mozilla.org/DeveloperServices/TeamMeetings]]

= Services =
* [[/Account Recovery]] - how to re-enable account access
* [[/git]] - details of our Git DVCS system
* [[/hg]] - details of our Mercurial DVCS system

DeveloperServices

2015-07-28T17:39:17Z

Klibby: update oncall; remove bkero, escalaion

<section begin=summary />{{TeamSummary
|teamtitle=Developer Services
|teampagelocation=DeveloperServices
|teamlead=Lawrence Mandel
|mailinglist=developer-services@mozilla.org
|description=The Developer Services team works on version control systems and related tools at Mozilla.
* We work on hg, git, svn, cvs, and bzr.
* We support the try repository.
* We also provide operational support for BMO, MozReview, Treeherder, MXR, and DXR.
}}<section end=summary />

= 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.
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Role'''
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''IRC Contact'''
|-
| Primary
| Kendall Libby
| fubar
|-
| Backup on call
| Hal Wine
| hwine
|}
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.

= Roster =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''Contact'''
| style="background:#EFEFEF;" | '''Location'''
| style="background:#EFEFEF;" | '''Project(s)'''
| style="background:#EFEFEF;" | '''Working Hours'''
|-
|Kendall Libby
|fubar
|Boston, MA, USA
|BMO, Treeherder, Reviewboard, DXR, MXR, hg, git
|EST
|-
|Gregory Szorc
|gps
|Vancouver, BC, Canada
|hg, Reviewboard, build module owner
|PST
|-
|Hal Wine (on loan from RelEng)
|hwine
|San Francisco, CA, USA
|VCSs, releng and IT liaison
|PST
|}

<div id="contact"> </div>
To contact all of the above, use the list developer-services@mozilla.org or [ircs://irc.mozilla.org/#vcs #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 [ircs://irc.mozilla.org/#vcs #vcs].

For general help with the systems we support, try:
* [ircs://irc.mozilla.org/#bteam #bteam] for BMO
* [ircs://irc.mozilla.org/#treeherder #treeherder] for Treeherder
* [ircs://irc.mozilla.org/#mozreview #mozreview] for MozReview
* [ircs://irc.mozilla.org/#static #static] for DXR
* There is no help to be found for MXR. Abandon all hope, etc, etc.

= Projects =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Project Name'''
| style="background:#EFEFEF;" |'''Description'''
| style="background:#EFEFEF;" | '''Primary Contact'''
|-
| [http://example.com project]
| This project does something
| laura@mozilla.com
|}

= Meetings =
* [[DeveloperServices/TeamMeetings|https://wiki.mozilla.org/DeveloperServices/TeamMeetings]]

= Services =
* [[/Account Recovery]] - how to re-enable account access
* [[/git]] - details of our Git DVCS system
* [[/hg]] - details of our Mercurial DVCS system

EngineeringProductivity/Team Roster

2015-07-27T16:10:03Z

Klibby: add fubar

See us [https://mozillians.org/en-US/group/automation-and-tools on Mozillians.org], and check out our [http://mzl.la/ateam wiki page].

{| class="wikitable"
|-
! Name
! IRC
! Info
! core areas of involvement
|-
| Vaibhav Agrawal
| vaibhav1994
| [https://mozillians.org/en-US/u/vaibhavmagarwal/ Mozillians]
| General Automation (Mochitest), Manifests, Structured Logging, Talos
|-
| Carsten Book
| tomcat
| [https://phonebook.mozilla.org/tree.php#search/cbook@mozilla.com ldap], [https://mozillians.org/en-US/u/Tomcat/ Mozillians]
| [[Sheriffing]], bughunter, plugin checker
|-
| Geoff Brown
| gbrown
| [https://phonebook.mozilla.org/tree.php#search/gbrown@mozilla.com ldap], [https://mozillians.org/en-US/u/geoffbrown/ Mozillians]
| mobile automation
|-
| David Burns
| AutomatedTester
| [https://phonebook.mozilla.org/tree.php#search/dburns@mozilla.com ldap], [https://mozillians.org/en-US/u/AutomatedTester/ Mozillians]
| management, w3c, [[Sheriffing]], [[Auto-tools/Projects/Marionette|Marionette]], WebDriver, community
|-
| Bob Clary
| bc
| [https://phonebook.mozilla.org/tree.php#search/bclary@mozilla.com ldap], [https://mozillians.org/en-US/u/bc/ Mozillians]
| mobile automation, autophone, bughunter
|-
| Mark Côté
| mcote
| [https://phonebook.mozilla.org/tree.php#search/mcote@mozilla.com ldap], [https://mozillians.org/en-US/u/mcote/ Mozillians]
| management, [[BMO]], MozReview, Pulse
|-
| Cameron Dawson
| camd
| [https://phonebook.mozilla.org/tree.php#search/cdawson@mozilla.com ldap], [https://mozillians.org/en-US/u/camd/ Mozillians]
| [[Auto-tools/Projects/Treeherder|Treeherder]], moztrap
|-
| Kaustabh Datta Choudhury
| kaustabh93
| [https://mozillians.org/en-US/u/kaustabh93/ Mozillians]
| [[Auto-tools/Projects/AlertManager|Alert Manager]]
|-
| Mauro Doglio
| mdoglio
| [https://phonebook.mozilla.org/tree.php#search/mdoglio@mozilla.com ldap], [https://mozillians.org/en-US/u/mdoglio/ Mozillians]
| [[Auto-tools/Projects/Treeherder|Treeherder]], mozreview
|-
| Jonathan French
| jfrench
|
[https://mozillians.org/en-US/u/tojonmz/ Mozillians]
| [[Auto-tools/Projects/Treeherder|Treeherder]]
|-
| Maja Frydrychowicz
| maja_zf
| [https://phonebook.mozilla.org/tree.php#search/mfrydrychowicz@mozilla.com ldap], [https://mozillians.org/en-US/u/maja_zf/ Mozillians]
| platform quality automation
|-
| James Graham
| jgraham
| [https://phonebook.mozilla.org/tree.php#search/jgraham@mozilla.com ldap], [https://mozillians.org/en-US/u/jgraham/ Mozillians]
| w3c, web-platform-tests, Firefox OS Cert Suite
|-
| Jonathan Griffin
| jgriffin
| [https://phonebook.mozilla.org/tree.php#search/jgriffin@mozilla.com ldap], [https://mozillians.org/en-US/u/jgriffin/ Mozillians]
| management, Marionette, Firefox OS Cert Suite
|-
| Andrew Halberstadt
| ahal
| [https://phonebook.mozilla.org/tree.php#search/ahalberstadt@mozilla.com ldap], [https://mozillians.org/en-US/u/ahal/ Mozillians]
| general automation, c++ code coverage, mozbase, mozharness
|-
| Dylan Hardison
| dylan
| [https://phonebook.mozilla.org/tree.php#search/dhardison@mozilla.com ldap], [https://mozillians.org/en-US/u/dylan/ Mozillians]
| bugzilla
|-
| Byron Jones
| glob
| [https://phonebook.mozilla.org/tree.php#search/bjones@mozilla.com ldap], [https://mozillians.org/en-US/u/glob/ Mozillians]
| bugzilla
|-
| Wesley Kocher
| kwierso
| [https://phonebook.mozilla.org/tree.php#search/wkocher@mozilla.com ldap], [https://mozillians.org/en-US/u/KWierso/ Mozillians]
| [[Sheriffing]]
|-
| William Lachance
| wlach
| [https://phonebook.mozilla.org/tree.php#search/wlachance@mozilla.com ldap], [https://mozillians.org/en-US/u/wlach/ Mozillians]
| Perfherder, Eideticker, mozbase, mozregression, general automation, A-team handbook
|-
| Kyle Lahnakoski
| ekyle
| [https://phonebook.mozilla.org/tree.php#search/klahnakoski@mozilla.com ldap], [https://mozillians.org/en-US/u/ekyle/ Mozillians]
| statistics, performance alerts, dashboards, BMO/ElasticSearch
|-
| Dave Lawrence
| dkl
| [https://phonebook.mozilla.org/tree.php#search/dlawrence@mozilla.com ldap], [https://mozillians.org/en-US/u/dkl/ Mozillians]
| bugzilla
|-
| Joel Maher
| jmaher
| [https://phonebook.mozilla.org/tree.php#search/jmaher@mozilla.com ldap], [https://mozillians.org/en-US/u/jmaher/ Mozillians]
| management, performance lead, general automation, community
|-
| Christopher Manchester
| chmanchester
| [https://phonebook.mozilla.org/tree.php#search/cmanchester@mozilla.com ldap], [https://mozillians.org/en-US/u/cmanchester/ Mozillians]
| structured logging, general automation
|-
| Dan Minor
| dminor
| [https://phonebook.mozilla.org/tree.php#search/dminor@mozilla.com ldap], [https://mozillians.org/en-US/u/dminor/ Mozillians]
| games benchmarking, mobile automation, Firefox OS Cert Suite, Autoland, general automation
|-
| Ed Morley
| emorley
| [https://phonebook.mozilla.org/tree.php#search/emorley@mozilla.com ldap], [https://mozillians.org/en-US/u/edmorley/ Mozillians]
| [[Auto-tools/Projects/Treeherder|Treeherder]]
|-
| Ted Mielczarek
| ted
| [https://phonebook.mozilla.org/tree.php#search/tmielczarek@mozilla.com ldap], [https://mozillians.org/en-US/u/ted/ Mozillians]
| breakpad, crash reporting, general automation, build system, mozbase, steeplechase, gamepad API
|-
| Syd Polk
| sydpolk
| [https://phonebook.mozilla.org/tree.php#search/spolk@mozilla.com ldap], [https://mozillians.org/en-US/u/spolk/ Mozillans]
| Jenkins, steeplechase, WebRTC, general automation, mozdownload, MSE
|-
| Andreas Tolfsen
| ato
| [https://phonebook.mozilla.org/tree.php#search/atolfsen@mozilla.com ldap], [https://mozillians.org/en-US/u/ato/ Mozillians]
| WebDriver, w3c, Selenium, [[Auto-tools/Projects/Marionette|Marionette]], Firefox OS Cert Suite
|-
| Henrik Skupin
| whimboo
| [https://phonebook.mozilla.org/tree.php#search/hskupin@mozilla.com ldap], [https://mozillians.org/en-US/u/whimboo/ Mozillians]
| Firefox Desktop Automation, [[Auto-tools/Projects/Marionette|Marionette]], Jenkins, Mozmill
|-
| Simarpreet Singh
| simar
| [https://mozillians.org/en-US/u/simar Mozillians]
| mozharness
|-
| Ryan VanderMeulen
| RyanVM
| [https://phonebook.mozilla.org/tree.php#search/rvandermeulen@mozilla.com ldap], [https://mozillians.org/en-US/u/RyanVM/ Mozillians]
| [[Sheriffing]]
|-
| Armen Zambrano G.
| armenzg
| [https://phonebook.mozilla.org/tree.php#search/armenzg@mozilla.com ldap], [https://mozillians.org/en-US/u/armenzg/ Mozillians]
| general automation, buildbot, release engineering
|-
| Kendall Libby
| fubar
| [https://phonebook.mozilla.org/tree.php#search/klibby@mozilla.com ldap], [https://mozillians.org/en-US/u/klibby/ Mozillians]
| ops, bmo, dxr, hg, git, treeherder, mxr
|}

DeveloperServices/TeamMeetings/2015-07-21

2015-07-21T16:43:19Z

Klibby: fubar's stuff

DeveloperServices/TeamMeetings/2015-07-14

2015-07-14T17:20:39Z

Klibby:

DeveloperServices/TeamMeetings/2015-07-14

2015-07-14T16:03:38Z

Klibby: fubar's stuff

DeveloperServices/TeamMeetings/2015-07-14

2015-07-14T16:02:35Z

Klibby: Created page with "<small> « previous meeting — index – DeveloperSe..."

DeveloperServices

2015-07-10T19:39:20Z

Klibby: add irc channels for some of the groups we work with (from mana)

<section begin=summary />{{TeamSummary
|teamtitle=Developer Services
|teampagelocation=DeveloperServices
|teamlead=Lawrence Mandel
|mailinglist=
|description=The Developer Services team works on version control systems and related tools at Mozilla.
* We work on hg, git, svn, cvs, and bzr.
* We support the try repository.
* We also provide operational support for BMO, MozReview, Treeherder, MXR, and DXR.
}}<section end=summary />

= Oncall for VCS =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Role'''
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''IRC Contact'''
|-
| Primary
| Ben Kero
| bkero
|-
| Backup on call
| Hal Wine
| hwine
|-
| Backup on call
| Kendall Libby
| fubar
|-
| Escalation
| Lawrence Mandel
| lmandel
|}
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.

= Roster =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''Contact'''
| style="background:#EFEFEF;" | '''Location'''
| style="background:#EFEFEF;" | '''Project(s)'''
| style="background:#EFEFEF;" | '''Working Hours'''
|-
|Ben Kero
|[[DeveloperServices/Ben Kero|bkero]]
|PDX, OR, USA
|hg, git, github
|PST
|-
|Kendall Libby
|fubar
|Boston, MA, USA
|BMO, Treeherder, Reviewboard, DXR, MXR, hg, git
|EST
|-
|Gregory Szorc
|gps
|Vancouver, BC, Canada
|hg, Reviewboard, build module owner
|PST
|-
|Hal Wine (on loan from RelEng)
|hwine
|San Francisco, CA, USA
|VCSs, releng and IT liaison
|PST
|-
|Lawrence Mandel
|lmandel
|Toronto, ONT, Canada
|Manager
|EST
|}

<div id="contact"> </div>
To contact all of the above, use the list developer-services@mozilla.org or [ircs://irc.mozilla.org/#vcs #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 [ircs://irc.mozilla.org/#vcs #vcs].

For general help with the systems we support, try:
* [ircs://irc.mozilla.org/#bteam #bteam] for BMO
* [ircs://irc.mozilla.org/#treeherder #treeherder] for Treeherder
* [ircs://irc.mozilla.org/#mozreview #mozreview] for MozReview
* [ircs://irc.mozilla.org/#static #static] for DXR
* There is no help to be found for MXR. Abandon all hope, etc, etc.

= Projects =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Project Name'''
| style="background:#EFEFEF;" |'''Description'''
| style="background:#EFEFEF;" | '''Primary Contact'''
|-
| [http://example.com project]
| This project does something
| laura@mozilla.com
|}

= Meetings =
* [[DeveloperServices/TeamMeetings|https://wiki.mozilla.org/DeveloperServices/TeamMeetings]]

= Services =
* [[/Account Recovery]] - how to re-enable account access
* [[/git]] - details of our Git DVCS system
* [[/hg]] - details of our Mercurial DVCS system

DeveloperServices

2015-07-07T18:03:35Z

Klibby: update oncall

<section begin=summary />{{TeamSummary
|teamtitle=Developer Services
|teampagelocation=DeveloperServices
|teamlead=Lawrence Mandel
|mailinglist=
|description=The Developer Services team works on version control systems and related tools at Mozilla.
* We work on hg, git, svn, cvs, and bzr.
* We support the try repository.
* We also provide operational support for BMO, MozReview, Treeherder, MXR, and DXR.
}}<section end=summary />

= Oncall for VCS =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Role'''
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''IRC Contact'''
|-
| Primary
| Ben Kero
| bkero
|-
| Backup on call
| Hal Wine
| hwine
|-
| Backup on call
| Kendall Libby
| fubar
|-
| Escalation
| Lawrence Mandel
| lmandel
|}
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.

= Roster =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''Contact'''
| style="background:#EFEFEF;" | '''Location'''
| style="background:#EFEFEF;" | '''Project(s)'''
| style="background:#EFEFEF;" | '''Working Hours'''
|-
|Ben Kero
|[[DeveloperServices/Ben Kero|bkero]]
|PDX, OR, USA
|hg, git, github
|PST
|-
|Kendall Libby
|fubar
|Boston, MA, USA
|BMO, Treeherder, Reviewboard, DXR, MXR, hg, git
|EST
|-
|Gregory Szorc
|gps
|Vancouver, BC, Canada
|hg, Reviewboard, build module owner
|PST
|-
|Hal Wine (on loan from RelEng)
|hwine
|San Francisco, CA, USA
|VCSs, releng and IT liaison
|PST
|-
|Lawrence Mandel
|lmandel
|Toronto, ONT, Canada
|Manager
|EST
|}

<div id="contact"> </div>
To contact all of the above, use the list developer-services@mozilla.org or [ircs://irc.mozilla.org/#vcs #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 [ircs://irc.mozilla.org/#vcs #vcs].

= Projects =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Project Name'''
| style="background:#EFEFEF;" |'''Description'''
| style="background:#EFEFEF;" | '''Primary Contact'''
|-
| [http://example.com project]
| This project does something
| laura@mozilla.com
|}

= Meetings =
* [[DeveloperServices/TeamMeetings|https://wiki.mozilla.org/DeveloperServices/TeamMeetings]]

= Services =
* [[/Account Recovery]] - how to re-enable account access
* [[/git]] - details of our Git DVCS system
* [[/hg]] - details of our Mercurial DVCS system

DeveloperServices/TeamMeetings/2015-07-07

2015-07-07T17:57:37Z

Klibby: fubar's stuff

DeveloperServices/TeamMeetings/2015-07-07

2015-07-07T17:40:55Z

Klibby: Created page with "<small> « previous meeting — index – DeveloperSe..."

DeveloperServices

2015-06-30T18:04:03Z

Klibby: update oncall

<section begin=summary />{{TeamSummary
|teamtitle=Developer Services
|teampagelocation=DeveloperServices
|teamlead=Lawrence Mandel
|mailinglist=
|description=The Developer Services team works on version control systems and related tools at Mozilla.
* We work on hg, git, svn, cvs, and bzr.
* We support the try repository.
* We also provide operational support for BMO, MozReview, Treeherder, MXR, and DXR.
}}<section end=summary />

= Oncall for VCS =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Role'''
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''IRC Contact'''
|-
| Primary
| Kendall Libby
| fubar
|-
| Backup on call
| Ben Kero
| bkero
|-
| Backup on call
| Hal Wine
| hwine
|-
| Escalation
| Lawrence Mandel
| lmandel
|}
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.

= Roster =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''Contact'''
| style="background:#EFEFEF;" | '''Location'''
| style="background:#EFEFEF;" | '''Project(s)'''
| style="background:#EFEFEF;" | '''Working Hours'''
|-
|Ben Kero
|[[DeveloperServices/Ben Kero|bkero]]
|PDX, OR, USA
|hg, git, github
|PST
|-
|Kendall Libby
|fubar
|Boston, MA, USA
|BMO, Treeherder, Reviewboard, DXR, MXR, hg, git
|EST
|-
|Gregory Szorc
|gps
|Vancouver, BC, Canada
|hg, Reviewboard, build module owner
|PST
|-
|Hal Wine (on loan from RelEng)
|hwine
|San Francisco, CA, USA
|VCSs, releng and IT liaison
|PST
|-
|Lawrence Mandel
|lmandel
|Toronto, ONT, Canada
|Manager
|EST
|}

<div id="contact"> </div>
To contact all of the above, use the list developer-services@mozilla.org or [ircs://irc.mozilla.org/#vcs #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 [ircs://irc.mozilla.org/#vcs #vcs].

= Projects =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Project Name'''
| style="background:#EFEFEF;" |'''Description'''
| style="background:#EFEFEF;" | '''Primary Contact'''
|-
| [http://example.com project]
| This project does something
| laura@mozilla.com
|}

= Meetings =
* [[DeveloperServices/TeamMeetings|https://wiki.mozilla.org/DeveloperServices/TeamMeetings]]

= Services =
* [[/Account Recovery]] - how to re-enable account access
* [[/git]] - details of our Git DVCS system
* [[/hg]] - details of our Mercurial DVCS system

DeveloperServices/TeamMeetings/2015-06-30

2015-06-30T17:55:24Z

Klibby: fubar's stuff update

DeveloperServices/TeamMeetings/2015-06-30

2015-06-30T17:53:22Z

Klibby: fubar's stuff

DeveloperServices/TeamMeetings/2015-06-16

2015-06-16T17:50:21Z

Klibby: fubar's stuff

<small>
[[DeveloperServices/TeamMeetings/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous meeting]] —
[[DeveloperServices/TeamMeetings|index]] –
[[DeveloperServices/TeamMeetings/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]
<sup>[https://wiki.mozilla.org/index.php?title=DeveloperServices/TeamMeetings/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}&action=edit&redlink=1&preload=DeveloperServices/TeamMeetings/Template create?]</sup>
</small>

== Meeting Info ==
* 11 am Pacific Time
* Vidyo room: DeveloperServices
* Backchannel in #vcs

== Hot items ==
* On Call Handoff!!!
** hwine already grabbed until bkero is back-up

== Stand-up ==
=== Last week ===
* bkero
* fubar
** DXR staging issues, w/ devs
** jenkins builds running
* gps
** moz.build Mercurial reading and related work landed in Firefox build system
** moz.build integration with hg.mozilla.org
*** researched security options
** hg.mozilla.org performance follow-ups to metadata introduction
** work to enable pushrebase extension
*** will likely require upstream fixes to extension
** support ReviewBoard production deployments
** Mercurial status meeting w/ Google and Facebook
*** We should start thinking about deploying remotefilelog
* hwine
** vcs-sync - lots of final details
** vcs-sync logs going to AWS account now
** modern vcs-sync bug found & fixed ← first one I've dealt with
** more data pushing to modern mapper
* lmandel
** Whistler session scheduling
** R&D tax credits, hr stuff, interviews all done
** PTO Monday to "play" in a golf tournament
* smacleod
** RB Security & more release fixes
*** Better MozReview diffs now deployed!
*** MozReview tests caught a few regressions in RB Core
**** Tracked down and patched / reviewed regression fixes
*** Work to upgrade to regression fix release 2.0.17

=== Planned for this week ===
* bkero
* fubar
** rust on DXR
** help get staging back to usable, maybe to SCL3
** changes to docker builder for jenkins
* gps
** moz.build integration with hg.mozilla.org
** Whistler prep
** pushrebase hacking
** MozReview developer workflow improvements
* hwine
** finish vcs-sync
* lmandel
** Complete Whistler planning
* smacleod
** Finish up MozReview LDAP

== Other business ==
* [hal] tags, etc, on AWS
* [lmandel] (Maybe obvious) next week's team meeting is cancelled
* [lmandel] Dev Services related Whistler sessions (please add to this list)
** Tue
*** 9:00-11:00: Mozilla All Hands
*** 1:00-2:00: Platform Kick Off All Hands
** Wed
*** 9:00-10:00: Platform lightening talks
*** 11:00-12:00: cbeard and Platform
*** 1:00-2:00: PANEL - Distinguished Engineers AMA!
*** 2:00-3:00: DISCUSSION - Developer Sanity
*** 2:00-5:00: HACKING SESSIONS - Treeherder, Mozharness
*** 4:00-5:00: JS Code Coverage
** Thu
*** 9:00-11:00: Mozilla All Hands
*** 11:00-12:15: moc / releng / relman / devservices meet-up
*** 2:00-5:00: HACKING SESSIONS - Treeherder, MozReview
** Fri
*** 10:30-11:00: Consuming Version Control at Scale (gps)
*** 2:00-3:00: MozReview and Whistler Wrap Up
* Rooms may change (hopefully not). All sessions will be listed in [https://juneworkweekwhistler2015.sched.org/ Sched]

== PTOs, etc ==
* hal off week after whistler

== Links ==
[https://wiki.mozilla.org/DeveloperServices/Goals-2015Q2 Q2 Goals]

DeveloperServices/TeamMeetings/2015-06-09

2015-06-09T17:18:06Z

Klibby: fubar's stuff

DeveloperServices/TeamMeetings/2015-06-02

2015-06-02T17:52:26Z

Klibby: fubar's stuff

DeveloperServices

2015-05-12T18:01:52Z

Klibby: oncall upate

<section begin=summary />{{TeamSummary
|teamtitle=Developer Services
|teampagelocation=DeveloperServices
|teamlead=Lawrence Mandel
|mailinglist=
|description=The Developer Services team works on version control systems and related tools at Mozilla.
* We work on hg, git, svn, cvs, and bzr.
* We support the try repository.
* We also provide operational support for BMO, MozReview, Treeherder, MXR, and DXR.
}}<section end=summary />

= Oncall for VCS =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Role'''
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''Contact'''
|-
| Primary
| Hal Wine
| hwine
|-
| Backup on call (next week duty)
| Ben Kero
| bkero
|-
| Backup on call
| n/a
| n/a
|-
| Escalation
| Lawrence Mandel
| lmandel
|}
As always with service issues, please indicate urgency and contact information in any page or voice mail. Using Nagios paging is most reliable.

= Roster =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''Contact'''
| style="background:#EFEFEF;" | '''Location'''
| style="background:#EFEFEF;" | '''Project(s)'''
| style="background:#EFEFEF;" | '''Working Hours'''
|-
|Ben Kero
|[[DeveloperServices/Ben Kero|bkero]]
|PDX, OR, USA
|hg, git, github
|PST
|-
|Kendall Libby
|fubar
|Boston, MA, USA
|BMO, Treeherder, Reviewboard, DXR, MXR, hg, git
|EST
|-
|Gregory Szorc
|gps
|Vancouver, BC, Canada
|hg, Reviewboard, build module owner
|PST
|-
|Hal Wine (on loan from RelEng)
|hwine
|San Francisco, CA, USA
|VCSs, releng and IT liaison
|PST
|-
|Lawrence Mandel
|lmandel
|Toronto, ONT, Canada
|Manager
|EST
|}

To contact all of the above, use the list developer-services@mozilla.org

Additional folks work on various modifications and extensions to the version control systems. They can be reached at dev-version-control@lists.mozilla.org.

= Projects =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Project Name'''
| style="background:#EFEFEF;" |'''Description'''
| style="background:#EFEFEF;" | '''Primary Contact'''
|-
| [http://example.com project]
| This project does something
| laura@mozilla.com
|}

= Meetings =
* [[DeveloperServices/TeamMeetings|https://wiki.mozilla.org/DeveloperServices/TeamMeetings]]

= Services =
* [[/Account Recovery]] - how to re-enable account access
* [[/git]] - details of our Git DVCS system
* [[/hg]] - details of our Mercurial DVCS system

DeveloperServices/TeamMeetings/2015-05-12

2015-05-12T17:16:06Z

Klibby: fubar's stuff

DeveloperServices/TeamMeetings/2015-05-05

2015-05-05T18:27:30Z

Klibby: /* PTOs, etc */ adding pto

<small>
[[DeveloperServices/TeamMeetings/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous meeting]] —
[[DeveloperServices/TeamMeetings|index]] –
[[DeveloperServices/TeamMeetings/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]
<sup>[https://wiki.mozilla.org/index.php?title=DeveloperServices/TeamMeetings/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}&action=edit&redlink=1&preload=DeveloperServices/TeamMeetings/Template create?]</sup>
</small>

== Meeting Info ==
* 11 am Pacific Time
* Vidyo room: DeveloperServices
* Backchannel in #vcs

== Hot items ==
* On Call Handoff!!!
** hwine → klibby

* {{bug|1161609}} git.m.o operations needing some love
* fyi - scl3 power outage Wed/Thur 2000-2300 PT {{bug|1160608}}

== Stand-up ==
=== Last week ===
* bkero
** Wrote partial hgweb-from-vct host installation playbook
** scan-build + mozreview
* fubar
** started docs refresh
** BMO PHX→AWS planning started
** test VM for docker builds in SCL3; m-c wrangling
** bzr tarballs (hal?)
* gps
** moved to bay area
** case folding fire drill ({{bug|797962}})
** automatic repository discovery in MozReview ({{bug|1045736}})
** improvements to auto-refreshing containers for MozReview development
** re-cloned some repos on hg.mozilla.org hgweb (upgraded store format for better performance)
** deprecate library_overrides ({{bug|1159099}})
** improvements to Ansible deploy of MozReview
** blog post: http://gregoryszorc.com/blog/2015/05/04/mercurial-3.4-released/
** blog post: http://gregoryszorc.com/blog/2015/05/04/reporting-mercurial-issues/
* hwine
** some progress on CVS
** lots of interrupts about FF 38.0 (l10n issues)
** power cycle planning
* lmandel
** lots of release discussions
** more catchup
* smacleod
** Finished up git diff support in RB core
** Started on MozReview patches to switch us to new diff support
** Ran some basic usage statistics on MozReview

=== Planned for this week ===
* bkero
** Finish hgweb-from-vct playbook
** mozreview+pulse+bots interaction as prereq to implementing scan-build for gecko patches
* fubar
** docs refresh con't
** SVN data
** docker build testing
* gps
** record commit IDs for MozReview
*** pre-req for better tracking of commits, Git support
* hwine
** Intern ramp up - welcome Anhad (irc ffledgling)
** vcs-sync
** scl3 power work
* lmandel
** release work
* smacleod
** Convert MozReview to new diff support.
** Start giving RB commit author information.
** More RB core work around the diff viewer.
** Write some re-usable scripts for generating better MozReview usage stats.

== Other business ==
* (hwine) Gentle reminder - any maintenance work to any of our systems should be coordinated and pre-announced in #moc. Good habit and builds good will(sm).
* (lmandel) bz identified functionality (CVS attic blame) that we (as in Mozilla) have decommissioned without a replacement. From his comments, a Web based way to access blame would make him more productive. Hal has a thread on the mailing list about get {{bug|1155388}} into the dxr backlog.
* (lmandel) We talked about integrating static analysis in the review process. Sylvestre Ledru and I discussed prototyping scanbuild diff results in MozReview. Would be opt-in and look something like:
** dev requests review from scanbuild
** build with patch(es) created automatically, scanbuild run
** diff from scanbuild results with patches compared against latest m-c build or separate build that does not include patches
** diff posted to MozReview
* (lmandel) Do we have best practices docs for using our tools and, more generally, how to work as a Mozilla dev?
* (lmandel) Interested in giving a talk to our interns? Sign up: https://mana.mozilla.org/wiki/pages/viewpage.action?pageId=45125125
* (hwine) With additional task cluster changes, we're starting to see more load & alerts on git.m.o. Seems like a good time to make a tuning push on git.m.o? We have some bug already filed, and the TC team may have input on how their use is ramping.

== PTOs, etc ==
* fubar - 14-29 May

== Links ==
[https://wiki.mozilla.org/DeveloperServices/Goals-2015Q2 Q2 Goals]

DeveloperServices/TeamMeetings/2015-05-05

2015-05-05T17:26:59Z

Klibby: fubar's stuff

<small>
[[DeveloperServices/TeamMeetings/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous meeting]] —
[[DeveloperServices/TeamMeetings|index]] –
[[DeveloperServices/TeamMeetings/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]
<sup>[https://wiki.mozilla.org/index.php?title=DeveloperServices/TeamMeetings/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}&action=edit&redlink=1&preload=DeveloperServices/TeamMeetings/Template create?]</sup>
</small>

== Meeting Info ==
* 11 am Pacific Time
* Vidyo room: DeveloperServices
* Backchannel in #vcs

== Hot items ==
* On Call Handoff!!!
** hwine → bkero

* {{bug|1161609}} git.m.o operations needing some love
* fyi - scl3 power outage Wed/Thur 2000-2300 PT {{bug|1160608}}

== Stand-up ==
=== Last week ===
* bkero
** Wrote partial hgweb-from-vct host installation playbook
** scan-build + mozreview
* fubar
** started docs refresh
** BMO PHX→AWS planning started
** test VM for docker builds in SCL3; m-c wrangling
** bzr tarballs (hal?)
* gps
* hwine
** some progress on CVS
** lots of interrupts about FF 38.0 (l10n issues)
** power cycle planning
* lmandel
* smacleod

=== Planned for this week ===
* bkero
** Finish hgweb-from-vct playbook
** mozreview+pulse+bots interaction as prereq to implementing scan-build for gecko patches
* fubar
** docs refresh con't
** SVN data
** docker build testing
* gps
* hwine
** Intern ramp up - welcome Anhad (irc ffledgling)
** vcs-sync
** scl3 power work
* lmandel
* smacleod

== Other business ==
* (hwine) Gentle reminder - any maintenance work to any of our systems should be coordinated and pre-announced in #moc. Good habit and builds good will(sm).
* (lmandel) bz identified functionality (CVS attic blame) that we (as in Mozilla) have decommissioned without a replacement. From his comments, a Web based way to access blame would make him more productive. Hal has a thread on the mailing list about get {{bug|1155388}} into the dxr backlog.
* (lmandel) We talked about integrating static analysis in the review process. Sylvestre Ledru and I discussed prototyping scanbuild diff results in MozReview. Would be opt-in and look something like:
** dev requests review from scanbuild
** build with patch(es) created automatically, scanbuild run
** diff from scanbuild results with patches compared against latest m-c build or separate build that does not include patches
** diff posted to MozReview
* (lmandel) Do we have best practices docs for using our tools and, more generally, how to work as a Mozilla dev?
* (lmandel) Interested in giving a talk to our interns? Sign up: https://mana.mozilla.org/wiki/pages/viewpage.action?pageId=45125125
* (hwine) With additional task cluster changes, we're starting to see more load & alerts on git.m.o. Seems like a good time to make a tuning push on git.m.o? We have some bug already filed, and the TC team may have input on how their use is ramping.

== PTOs, etc ==

== Links ==
[https://wiki.mozilla.org/DeveloperServices/Goals-2015Q2 Q2 Goals]

DeveloperServices

2015-05-04T14:54:47Z

Klibby: added other services we support

<section begin=summary />{{TeamSummary
|teamtitle=Developer Services
|teampagelocation=DeveloperServices
|teamlead=Lawrence Mandel
|mailinglist=
|description=The Developer Services team works on version control systems and related tools at Mozilla.
* We work on hg, git, svn, cvs, and bzr.
* We support the try repository.
* We also provide operational support for BMO, MozReview, Treeherder, MXR, and DXR.
}}<section end=summary />

= Oncall for VCS =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Role'''
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''Contact'''
|-
| Primary
| Hal Wine
| hwine
|-
| Escalation
| Lawrence Mandel
| lmandel
|}

(Next week: usually rotates through: bkero, fubar, hwine)

= Roster =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''Contact'''
| style="background:#EFEFEF;" | '''Location'''
| style="background:#EFEFEF;" | '''Project(s)'''
| style="background:#EFEFEF;" | '''Working Hours'''
|-
|Ben Kero
|[[DeveloperServices/Ben Kero|bkero]]
|PDX, OR, USA
|hg, git, github
|PST
|-
|Kendall Libby
|fubar
|Boston, MA, USA
|BMO, Treeherder, Reviewboard, DXR, MXR, hg, git
|EST
|-
|Gregory Szorc
|gps
|Vancouver, BC, Canada
|hg, Reviewboard, build module owner
|PST
|-
|Hal Wine (on loan from RelEng)
|hwine
|San Francisco, CA, USA
|VCSs, releng and IT liaison
|PST
|-
|Lawrence Mandel
|lmandel
|Toronto, ONT, Canada
|Manager
|EST
|}

To contact all of the above, use the list developer-services@mozilla.org

Additional folks work on various modifications and extensions to the version control systems. They can be reached at dev-version-control@lists.mozilla.org.

= Projects =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Project Name'''
| style="background:#EFEFEF;" |'''Description'''
| style="background:#EFEFEF;" | '''Primary Contact'''
|-
| [http://example.com project]
| This project does something
| laura@mozilla.com
|}

= Meetings =
* [[DeveloperServices/TeamMeetings|https://wiki.mozilla.org/DeveloperServices/TeamMeetings]]

= Services =
* [[/Account Recovery]] - how to re-enable account access
* [[/git]] - details of our Git DVCS system
* [[/hg]] - details of our Mercurial DVCS system

DeveloperServices

2015-04-29T14:11:05Z

Klibby: oncall upate

<section begin=summary />{{TeamSummary
|teamtitle=Developer Services
|teampagelocation=DeveloperServices
|teamlead=Lawrence Mandel
|mailinglist=
|description=The Developer Services team works on version control systems and related tools at Mozilla.
* We work on hg, git, svn, cvs, and bzr.
* We support the try repository.
* We also provide operational support for ReviewBoard, Treeherder, and DXR.
}}<section end=summary />

= Oncall for VCS =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Role'''
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''Contact'''
|-
| Primary
| Hal Wine
| hwine
|-
| Escalation
| Lawrence Mandel
| lmandel
|}

(Next week: usually rotates through: bkero, fubar, hwine)

= Roster =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Name'''
| style="background:#EFEFEF;" |'''Contact'''
| style="background:#EFEFEF;" | '''Location'''
| style="background:#EFEFEF;" | '''Project(s)'''
| style="background:#EFEFEF;" | '''Working Hours'''
|-
|Ben Kero
|[[DeveloperServices/Ben Kero|bkero]]
|PDX, OR, USA
|hg, git, github
|PST
|-
|Kendall Libby
|fubar
|Boston, MA, USA
|treeherder, Reviewboard, DXR, hg, git
|EST
|-
|Gregory Szorc
|gps
|Vancouver, BC, Canada
|hg, Reviewboard, build module owner
|PST
|-
|Hal Wine (on loan from RelEng)
|hwine
|San Francisco, CA, USA
|VCSs, releng and IT liaison
|PST
|-
|Lawrence Mandel
|lmandel
|Toronto, ONT, Canada
|Manager
|EST
|}

To contact all of the above, use the list developer-services@mozilla.org

Additional folks work on various modification and extensions to the version control systems. They can be reached at dev-version-control@lists.mozilla.org.

= Projects =
{| class="fullwidth-table"
| style="background:#EFEFEF;" |'''Project Name'''
| style="background:#EFEFEF;" |'''Description'''
| style="background:#EFEFEF;" | '''Primary Contact'''
|-
| [http://example.com project]
| This project does something
| laura@mozilla.com
|}

= Meetings =
* [[DeveloperServices/TeamMeetings|https://wiki.mozilla.org/DeveloperServices/TeamMeetings]]

= Services =
* [[/git]] - details of our Git DVCS system
* [[/hg]] - details of our Mercurial DVCS system
* [[/Account Recovery]] - how to re-enable account access

DeveloperServices/TeamMeetings/2015-04-28

2015-04-28T17:31:11Z

Klibby: fubar's stuff

DeveloperServices/TeamMeetings/2015-04-21

2015-04-21T18:05:13Z

Klibby: other biz

DeveloperServices/TeamMeetings/2015-04-21

2015-04-21T17:46:21Z

Klibby: create, fubar's stuff

DeveloperServices/TeamMeetings/2015-04-14

2015-04-14T17:34:37Z

Klibby: fubar's stuff