Wikimedia Discovery/Team/Analyst onboarding

Setting computers up, setting accounts up and getting known

 * Generate two SSH keys (see this article on GitHub for instructions): one for our analytics machines and one for labs ("Wikitech") access.
 * Create a Wikitech account. Go to Preferences → OpenStack and include the public part of a newly-generated SSH key. Get Oliver to give you access to the relevant machines.
 * Use the Wikitech account to create a Phabricator account. Get Mikhail to sign you up to all the appropriate boards (e.g. Analysis Sprint BoardDandiscovery Board) and walk you through the process of working with cards.
 * File a Phabricator ticket in the Ops-Access queue, CC-ing Tomasz and Mikhail, containing the public part of a newly-generated SSH key, asking for access to stat1002, stat1003, and fluorine. Don't worry about what those names mean just yet.
 * Get an IRC client. Join irc.freenode.net and #wikimedia-discovery. Welcome to our team live chat!
 * Learn about cloaks and request one. (It can take a few days for the cloak stuff to be resolved.)
 * Additional channels to join: : #wikimedia-search, #wikimedia-analytics, #wikimedia-research, #wikimedia-ai, #wikimedia-operations
 * Schedule staff photo (just list your 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.
 * Add yourself to the team page—twice: in the info box at the top of the page, and under the section "The Team | Members".
 * Subscribe to some mailing lists using your @wikimedia.org account
 * The public search list
 * The private search list
 * Introduce yourself on wikimedia-search.
 * Setup your SSH configuration (get Mikhail to email you his config)
 * In Terminal on OS X, go to Preferences → Profiles → Shell. Check Run command and type in:  and check Run inside shell.

Meeting interesting people

 * You should sit down with Tomasz Finc – Director of Discovery – and discuss the department's goals and get an overview of the various teams.
 * You should sit down with Dan Garry – our Product Manager and probably your Line Manager – to talk about our team's goals and relationship with other teams.
 * You should sit down with Deborah Tankersley – Product Manager for Wikipedia Portal (wikipedia.org) – to about how Discovery Analytics supports her team.
 * You should speak to Kevin Smith about the team's processes for tracking work.
 * Grab Trey Jones, a wicked-smaht text processing specialist, linguist, and our relevance engineer.
 * Grab Erik Bernhardson, who knows far too much about our search systems and event logging.
 * Talk to Chris Koerner (Discovery's Community Liaison) about the community!
 * Talk to Aaron Halfaker about research in the context of Wikipedia users, and Ellery Wulczyn to chat about data analysis at the Foundation.
 * Talk to Michelle Paulson from legal about privacy and data sources.
 * Make sure Mikhail has added you to the research group meetings.
 * Attend the Community Liaison Cabal meeting to ask questions and hear about the way people interact with our community.

Working on projects

 * Go through the Dashboarding & Testing presentation Oliver and Mikhail gave at All Hands 2016. Make a list of questions. Try to answer as many of them as you can by reading through our Employee Operations Manual on Meta. This is less a test for you and more of a test for the thoroughness of the EOM :) Mikhail will answer whatever questions you can't find an answer to.
 * See if you can run this presentation written in RMarkdown.
 * Pick a small (low point value) task from Phabricator. Work on it! Reach out to Mikhail if you run into any issues or it requires specific domain knowledge.
 * Talk through big upcoming projects with Mikhail and how you fit into them.