User:ATomasevich (WMF)/SD Onboarding Draft

This is the tracking page for New Hire's tasks for their onboarding process. To check off an item, add  after the bullet for that item.

Required

 * Read the guide for new hires, including the guide for new engineering staff.
 * Review our guide to the various Wikimedia wikis.
 * Verify access to Gmail (@wikimedia.org), Office (standalone), and Wikipedia / MediaWiki.org (same account via single user login).
 * Create a Wikitech LDAP account (also called a wikitech account). Commonly, the username you use is your internet handle (i.e., not a (WMF) username), but you will want to use your @wikimedia.org email address.
 * Verify that you can log into Phabricator with your Wikitech LDAP account. If you run into any issues, refer to this help document. See generally Phabricator for more documentation and tips.
 * Verify access to Gerrit using your Wikitech LDAP account.
 * Request access to the group ldap/wmf. Create a new task requesting to be added to the ldap/wmf group. Include your LDAP username, SUL username, and wikimedia email address. Assign the task to your manager so they can comment on it with more specifics and with their approval. Add the tag LDAP-Access-Requests to the task.
 * Read Become a MediaWiki hacker
 * Set up Slack, and join any team channel(s) that may be applicable (and some general-interest ones if you like)
 * Set up IRC. Join the #wikimedia-staff (requires invitation), #wikimedia-mobile, and #wikimedia-operations channels (#wikimedia-office is also helpful for some public events). Review other channels for your interests. Attach an IRC cloak. If you don't already have an IRC client, consider using IRCCloud, a web-based client popular among Foundation staff. To get added to the Wikimedia group account for IRCCloud, email techsuppport@wikimedia.org with the email you used to register (your `@wikimedia.org` email).
 * Ping marktraceur on IRC and ask him to add you to #wikimedia-staff
 * Subscribe to the following lists on https://lists.wikimedia.org/ with your Wikimedia email address.
 * mobile-l - Default list for discussions for mobile-related or Readers audience vertical topics.
 * wikitech-l - Default list for tech discussions on Wikimedia and MediaWiki software.
 * mediawiki-api and mediawiki-api-announce - Lists about internet-facing APIs.
 * engineering - Public-facing list for all software engineers. You should already be subscribed to this list. Contact OIT if you still need access.
 * Write up an introduction email for yourself written in the first or third person, and send it to your manager for review, so your manager can share on the internal product wide mailing list and forward to the Foundation-wide optional mailing list.
 * Read about the Movement Strategy.
 * Read the Medium Term Plan.
 * Read the WMF annual plan for FY 2018-2019 (June 2018 - July 2019)
 * Start on making 50 edits on a broad range of user agents, form factors, network conditions, etc. - MediaWiki.org and Office Wiki are simplest for your work account. Remember, your personal edits on project wikis are your personal edits. Some help: Help:Wiki markup, Help:Wikitext examples
 * Review the recommended resources below

Required for some
Verify with your manager which of these apply to you:


 * Request access to one of the data access groups. Consult your manager to figure out the appropriate group(s) and add them to the access request task for approval. This will allow you to access analytics data. Ensure that you have also read the data access guidelines.
 * Apply for beta cluster event logging access for debugging analytics data submission.
 * Request access to OTRS, our system for customer support requests, by emailing [mailto:otrs-admins@lists.wikimedia.org otrs-admins@lists.wikimedia.org].
 * If you will be doing deployment-related work (typically, for web engineering and content services), request "deployment access and operational logs access" when following the steps for shell access.

Strongly recommended

 * Meet with each of your teammates and any other relevant Foundation members to introduce yourself and get to know them. Your manager or onboarding buddy will help make introductions and set these meetings up.
 * Get a crash course from a teammate on the following. Your onboarding buddy can help set these meetings up.
 * Team extensions and current work
 * Mediawiki overview
 * Development process overview (local dev setup, Gerrit and git review processes and n orms, CI, the train, etc.)
 * Anything else you'd like to request
 * Scan the English Wikipedia Village Pumps and Commons Village Pump
 * Read this overview of Structured Data on Commons
 * Read The Wikipedia Revolution

If you like

 * Arrange for a staff photo. It's not required,
 * In Gmail, enable Settings > General (tab) > Undo Send and change the timeout to 30 seconds and press Save Change
 * Watch this video of Joel Spolsky at Wikimedia
 * Subscribe to the following lists on https://lists.wikimedia.org/ with your Wikimedia email address.
 * analytics - List about analytics.
 * newreaders - Public discussion about New Readers.
 * Read some blog posts, like Why it took a long time to build that tiny link preview on Wikipedia.
 * Review recent quarterly check-in decks for Audiences
 * Read about Readers
 * Read Debugging Teams: Better Productivity through Collaboration (Brian W. Fitzpatrick and Ben Collins-Sussman)

Recommended resources

 * General repository for Wikimedia docs
 * Mediawiki core and extensions code search
 * Gerrit tutorial
 * Resource Loader
 * Docs
 * Overview tech talk
 * OOUI
 * Tutorials
 * Demos
 * Docs
 * Localisation
 * Caching
 * Templates
 * Local development environment setup instructions and tips

Members

 * Eric Gardner, Software Engineer - Pacific timezone
 * Ask him ___
 * Mark Holmquist, Engineering Manager - Central timezone
 * Ask him ___
 * Ramsey Isler, Product Manager - Pacific timezone
 * Ask him ___
 * Matthias Mullie, Software Engineer - Central European timezone
 * Ask him ___
 * Cormac Parle, Senior Software Engineer - Western European timezone
 * Ask him ___
 * Keegan Peterzell, Community Relations Specialist - Central timezone
 * Ask him ___
 * Anne Tomasevich, Software Engineer - Eastern timezone
 * Ask her about onboarding because she just did it
 * Ask her about slowly decoding the mystery that is OOUI, component libraries in general, and inclusive design

Meetings

 * Tuesday standup: 15-minute meeting to discuss blockers or any other time-sensitive topics
 * Design:Devs chat: 45-minute fortnightly meeting to touch base on design
 * Retrospective: 45-minute fortnightly meeting to discuss team processes, communication, and anything else that comes up
 * Weekly standing meeting: 60-minute weekly meeting time held in case we need it; will be confirmed or cancelled on Tuesday
 * Office hours: 60-minute weekly informal meeting in the #sd-eng channel in Slack to discuss engineering work or ask questions
 * Manager 1:1: 30-minute weekly meeting with your manager

Out of office

 * 1) Verify the dates you'll be out with your team and your manager.
 * 2) Request time off in Namely.
 * 3) Make an out of office event on your personal calendar that spans the time you'll be out. Ensure "Automatically decline new and existing meetings" is checked.
 * 4) Make an event on your team calendar indicating you’ll be out. Ensure "All-day" is checked and have it span all days you'll be out.
 * 5) Set your Gmail vacation responder with a message that indicates that you're out of office, when you'll return, and contact information of your delegate(s) for urgent issues regarding your work. Ensure that "Only send a response to people in Wikimedia Foundation" is checked.