Wikimedia Discovery/Team/Onboarding

Team page: Search and Discovery

Note that if you are seeing this in a page who's URL ends in /YourName then you should feel free to strike through the steps are you finish them.

= Everyone =
 * NOTE: Some of these tasks can be found by reading the new hire information but I'm making an effort to grab the important bits.
 * Read the Systems Guide for New Hires
 * Google Mail/Calendar
 * Follow the systems guide above to get access to gmail and your calendar.
 * (Optional) In Gmail, enable Settings -> Labs -> Undo Send and press Save Changes. Go back to settings and change the timeout to 30 seconds
 * Add these calendars to your calendar calendars: "WMF Staff Calendar", "WMF Sick/Vacation Tracking Calendar", and "WMF Fun & Learning"
 * The WMF Fun & Learning calendar isn't super useful for remote employees
 * In Calendar go to Settings and tick "Speedy Meetings" and set work hours
 * IRC
 * Get an IRC client. I like Quassel. weechat and irssi are good if you like text interfaces.
 * Connect to Freenode and register your user name.
 * Join #wikimedia-search, #wikimedia, #mediawiki, #wikimedia-operations, #wikimedia-office, #wikimedia-dev
 * Learn about cloaks and request one
 * Once you have a cloak you can join/get invited to #wikimedia-staff and #mediawiki_security <--- note the underscore. It has a history.
 * Verify WMF access to Wikitech (LDAP), Office (SUL), Wikipedia (SUL), and Wikimedia Foundation (SUL)
 * The instructions for these are in the systems guide above
 * Schedule staff photo (just list you name here)
 * Or you can list yourself as not wanting to have your photo up by adding your name under the cloak of invisibility list.

= Apps Software Developer Onboarding (Tech) =
 * Scrummaster (Kristen Lans)
 * Add to relevant calendar invites: Standup, Weekly meetings, etc
 * Add to relevant team page on mw.org
 * Explain team development cycle, project management tools , Trello and/or Phabricator workflow and meeting scheduling (checking individual calendars and room availability, etc)
 * Check-in meeting/agile orientation


 * Product Owner (Jon Katz)
 * Subscribe to mobile-l with Wikimedia email. Default list for all discussions about Mobile.
 * Subscribe to wikitech-l with Wikimedia email. Default list for all tech discussions about MediaWiki in general.
 * Subscribe to mediawiki-api and mediawiki-api-announce with Wikimedia email. Lists for hosted APIs, which the apps use.
 * Introduce to mobile apps team members who haven't met new developer
 * Product overview
 * Testing overview - in house and Specialists Guild
 * Wikimedia project overview - what are our projects and who uses them


 * Manager (Adam Baso)
 * Subscribe to reading-wmf. Use for administrivia (vacation, missed meetings, standup status)
 * Organisational overview - who the teams at the WMF are, and what they do
 * Values / Lessons learned (Analytics and data privacy as example of our values changing the way we have to approach certain problems, also flood-of-emails issue)


 * Designers (Primary: Vibha Bamba, Secondary: Moiz Syed)
 * UX / Design overview


 * Tech Lead
 * Setup IRC . Setup on common wiki channels . Attach an IRC cloak.
 * Setup Gerrit Access. Explore Gerrit workflow. Review Gerrit tutorial . Install "Git review".
 * Apply for access to stat servers (currently stat1002 and stat1003)
 * Apply for event logging access
 * Schedule intro to API meeting
 * Subscribe to the appropriate Gerrit review group(s).


 * Hire
 * Setup your account for Wikitech and Gerrit following How to become a MediaWiki hacker instructions. 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 for the email address to receive Gerrit email notifications.
 * Review HR's onboarding page
 * Fix a small bug. Plenty abound, we can pick one as time gets nearer. Get the patch through Gerrit and get it merged.
 * Fix a couple more small bugs to get a clearer idea of how things are
 * Take up a card for a full feature and implement it
 * Review team norms and values (Team, first retrospective after start date)

= Onboarding (iOS specific) =
 * Architecture overview - AutoLayout, Storyboards, not using 'promises' etc. (Monte)
 * Data objects overview (Brion)
 * Networking objects overview (Monte)
 * Must-haves overview - version compatibility, autosizing text labels, landscape / portrait compatibility, tablet scaling, no text truncation, etc (Monte)

= Onboarding (Android specific) =
 * Architecture overview (Dmitry/Bernd)
 * Libraries used (okhttp, picasso, acra, photoview, etc.)
 * JavaScript bridge
 * Grunt, JavaScript bundle generation
 * Overview of scripts (Dmitry/Bernd)
 * Fetching CSS assets from betalabs and/or vagrant
 * Generating PNG assets from SVGs
 * Building release APKs (beta/production/custom channels)
 * Request access to caesium (to deploy to releases.wikimedia.org)
 * Grant access to Play Store dev console (Adam)
 * Overview of TranslateWiki and our TWN sync process (Bernd)
 * (Optional) Add the Android SDK Search Chromium / Chrome extension.