Wikimedia Release Engineering Team/Onboarding

Copy/paste into onboarding task
This is your primary onboarding document for the team.

You --- [ ] Get access to your `@wikimedia.org` email (should happen before your first day). [ ] IRC [ ] Follow the IRC guide on meta wiki [ ] If you choose to use IRCCloud  (recommended if you are unfamiliar with IRC), get added to the Wikimedia group account by emailing techsupport@wikimedia.org with the email you used to register (your `@wikimedia.org` email). [ ] Join public IRC channels (`#wikimedia-releng`, `#wikimedia-operations`, `#wikimedia-pipeline`, `#wikimedia-cloud`, `#wikimedia-cloud-admin` ). [ ] Note the channel descriptions. [ ] Skim the full list of Wikimedia channels [ ] Private message `thcipriani` when the above is complete. [ ] Mailing lists and Google Groups ( descriptions of the lists ) [ ] Subscribe to ops@ [ ] Subscribe to wikitech-l@ [ ] Verify you are subscribed to Foundation Official and tech-all Google Groups. You may need to ask for assistance from Tyler for Foundation Official, or verify with someone in IT Services when you talk to them about comms. If you are not subscribed to tech-all, send email to techsupport@wikimedia.org to request addition. [ ] Development accounts [ ] If you do not yet have one, request a YubiKey from IT Services. [ ] Create a Wikimedia developer account  (aka: "LDAP account" or "wikitech account"). Follow the "VPS and General users" process. [ ] Add 2factor  to your Wikimedia developer account [ ] Generate two ssh keys. One for production and one for your Wikimedia developer account. [ ] Ensure your "~/.ssh/config" is setup  correctly [ ] Add the "wmfdev" ssh public key  to your Wikimedia developer account. [ ] Register in Phabricator  using your Wikimedia developer account. [ ] Associate your Wikimedia wiki account (created by ITS at https://meta.wikimedia.org/) with your Phabricator user account on https://phabricator.wikimedia.org/settings/panel/external/ [ ] Add 2factor to Phabricator login  at https://phabricator.wikimedia.org/settings/panel/multifactor/ [ ] Add the `wmfdev` ssh public key to Phabricator. [ ] Follow the Gerrit tutorial. Add your `wmfdev` ssh key in Gerrit. [ ] If you have a GitHub user, request access to the Release Engineering team  in the  Wikimedia Foundation organization. [ ] Server access [ ] Request access to production servers  in these groups: `deployment`, `contint-admins`, and `contint-docker`. Use your `wmfprod` ssh public key. [ ] Add that request task as a subtask to this one. [ ] Shared password management [ ] Create GPG key  for use with  our pwstore  (if you don't already have one). [ ] Ask Tyler to setup a team signing party. [ ] Monitoring [ ] Once added to `wmf` LDAP group, make sure you can access  Logstash. [ ] Bookmark: logstash,  grafana ,  icinga ,  SAL [ ] Add yourself to the Contact List on officewiki. [ ] Bookmark the contact List on officewiki  — you'll use it a whole lot [ ] Understand that you will be asked in the first team meeting (and, likely, other subsequent meetings) to "tell us a bit about yourself" and prepare mentally and emotionally for that [ ] Read the readings. [ ] Meet the rest of the team individually.

Somebody else (default: Tyler)

[ ] Add to weekly team meeting as soon as the Google account is created [ ] Have first day meeting with Tyler [ ] Schedule weekly 1:1 with Tyler [ ] Add to releng@ private team mailing list [ ] Add to engprod@ private team mailing list [ ] IRC [ ] Add to team related IRC access lists. [ ] Request addition to the other private IRC channels (`#wikimedia-staff`, `#mediawiki_security`) [ ] Tyler schedules 1:1s with everyone on the team. [ ] Add to relevant Team Drives in Google Drive: RelEng,  Pipeline ,  Code Health [ ] File an LDAP-Access-Requests for `wmf`, `releng`, `ciadmin` (link as subtask) [ ] Add to RelEng's Gerrit group (which gives Administrator and wmf-deployments by inheritance) [ ] Phabricator [ ] Add to Phabricator groups: #WMF-NDA, #trusted-contributors, #acl_releng, #acl_repository-admins, #acl_project-admins, #acl_phabricator [ ] Add to the kanban board's sidebar [ ] Add to kanban Herald rule: H229 [ ] Request addition to #Security phabricator group  (link as subtask) [ ] Add to our Cloud VPS projects : `deployment-prep` and `integration` [ ] Setup a keysigning party [ ] Add GPG key to our pwstore [ ] Add to team page on mediawiki.org  (team members and timezone).

// Source: https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Onboarding //

SSH keys generation
Generate two new SSH keys, be sure to use a memorable passphrase.

ssh-keygen -f ~/.ssh/id_ed25519.wmfdev -t ed25519 -C "your_email@youremail.com"
 * For your WIkimedia developer account use:

ssh-keygen -f ~/.ssh/id_ed25519.wmfprod -t ed25519 -C "your_email@youremail.com"
 * For your production account use:

You will now have 4 files in your  directory as follows: id_ed25519.wmfdev - Wikimedia developer account private key id_ed25519.wmfdev.pub - Wikimedia developer account public key id_ed25519.wmfprod - Wikimedia production account private key id_ed25519.wmfprod.pub - Wikimedia production account public key

We have a recommended .ssh/config to use.

Generating a GPG key

 * Run  and follow the prompts. Defaults are usually good, but use a 4096 bit length.
 * Then uploads public key to key server
 * Submit a patch for our PGP public key repo including only your public key


 * Reach out to Tyler to see about getting it signed. Requires two signatures.

Mailing lists descriptions

 * releng@lists.wikimedia.org - Private release engineering subteam list
 * engprod@lists.wikimedia.org - Private engineering productivity team list
 * ops@lists.wikimedia.org - Private ops list, includes all deployers
 * qa@lists.wikimedia.org - public list
 * security@wikimedia.org - (if appropriate) private alias for security issue reporting and follow-up
 * wikitech-l@wikimedia.org - public list for all things Wikimedia development

IRC Channel descriptions

 * #wikimedia-releng - team channel with task, code review, and monitoring bot announcements
 * #wikimedia-staff - private WMF staff and contractors only channel, useful backchannel for staff-only meetings
 * #wikimedia-engprod-team - private team IRC channel
 * #wikimedia-operations - most production server discussion happens here
 * #wikimedia-pipeline - focused on the cross-team Deployment Pipeline project
 * #wikimedia-tech - general Wikimedia tech discussion
 * #wikimedia-dev - Wikimedia dev related bot announcements (tasks and code review)
 * #wikimedia-cloud and #wikimedia-cloud-admin - Cloud VPS (much of our CI infrastructure depends on Wikimedia Cloud VPS)

Team-related IRC access additions

 * Prerequisite: the user's nick must be registered with nick enforcement set to .  They should follow the IRC tutorial on meta.
 * Add the user to the access list for our private team channel using the  template:
 * Then add to invite list (so they don't have to invite themselves each time):
 * Give the user +v (voice) in #wikimedia-releng
 * Give the user +v (voice) in #wikimedia-releng
 * Give the user +v (voice) in #wikimedia-releng

= People to meet and things to do with them = The goal is to meet your team mates and learn how the team fits together. Hopefully you'll talk to everyone on the team one on one for about thirty minutes over the first week or two. Bookmark the contact list on officewiki — you will use it a lot :)

First day

 * Tyler Cipriani, manager of the Release Engineering team. He is normally in the US Mountain timezone.
 * Tell him everything is going great and that the instructions are easy to follow but you are still overwhelmed by the reading you have to do.
 * Tell him that you found some errors in the instruction and fixed the template. :P
 * Ask him to give you an overview of how the foundation is organized, what teams do what, and all that.
 * Make sure he adds you to any relevant team meetings.
 * He'll want to talk to you one on one a few times in the first week.

First couple of weeks
Meet the whole team:


 * Antoine Musso - Central European timezone
 * Ask him to tell you the origin story of our Continuous Integration infrastructure, including Beta Cluster.
 * Ask him all about French cooking and why it's the best country to live in.
 * Brennen Bearnes - Mountain timezone
 * Ask him about error logs, Vim, or docker-compose.
 * Dan Duvall - Pacific timezone
 * Ask him about the Deployment Pipeline.
 * Ask him about maintaining the infrastructure for a website that got 99% of it's traffic in one month.
 * Jeena Huneidi
 * Ask her about Kubernetes or tea.
 * Lars Wirzenius - Eastern European timezone
 * Ask him about being the other new person on the team.
 * Ask him about his obsession with backups.
 * Mukunda Modell - Central timezone
 * Ask him about Phabricator and why it's a game.
 * Ask him about his RX7.

More widely, Release Engineering is part of Engineering Productivity:


 * Engineering Productivity
 * Greg Grossmeier - Pacific timezone (Director of Engineering)
 * Quality & Test Engineering
 * Jean-Rene Branaa - Pacific timezone (Engineer Manager)
 * Ask him about Code Health and what it means here.
 * Ask him to tell you all about gaming.
 * Zeljko Filipin - Central European timezone
 * Ask him about Selenium, continuous integration, MediaWiki-Vagrant, SWAT, train deploys.
 * Ask him about daylight saving time, juggling, Rubik's Cube, ukulele, Pareto principle, lightning talks, open space.
 * Others
 * Performance Engineering
 * Gilles Dubuc - Central European timezone (Engineering Manager)
 * Others

= Readings =

Check these out, bring any questions you have to Tyler or your onboarding buddy.


 * https://office.wikimedia.org/wiki/New_tech_employee_orientation <-- important
 * https://office.wikimedia.org/wiki/Technical_onboarding_for_new_hires
 * https://office.wikimedia.org/wiki/New_Hire_Orientation_Videos
 * From SRE:
 * Life of a request presentation
 * Application layer deeper dive presentation
 * The "Kubernetes" (2018-11-16) presentation from https://office.wikimedia.org/wiki/Operations/Ops_sessions
 * https://media.ccc.de/v/36c3-73-infrastructure-of-wikipedia
 * http://www.aosabook.org/en/mediawiki.html <-- lower priority, but interesting