= Readings =
As you would expect from a part of the Wikimedia movement, we have a sprawling mass of documentation. Here are some key pieces to get familiar with.
== Foundation generalities ==
[] our [staff handbook](https://office.wikimedia.org/wiki/Staff_handbook) on Office wiki. This is the official guide to organizational policies, principles, and benefits.
[] the [guide for new hires](https://office.wikimedia.org/wiki/Guide_for_new_hires) on Office wiki. Edit this if you figure out something important is missing or outdated!
[] the [staff and contractors page](https://wikimediafoundation.org/wiki/Staff_and_contractors) on the Foundation website. You probably already know about this.
[] our [internal contact list](https://office.wikimedia.org/wiki/Contact_list) on Office wiki.
[] watch [[ https://docs.google.com/file/d/0BxiTHaqH0xCRS2ZjMHNvV0hxRms/edit | a video on transitioning from volunteering to being on staff ]]. It's a few years old, but has some good nuggets.
[] The [Wikimedia 2030 strategic direction](https://meta.wikimedia.org/wiki/Strategy/Wikimedia_movement/2017/Direction).
[] The [Foundation's current annual plan](https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2018-2019/Final). This includes Audiences's work, but at a very general level.
== Audiences specifics ==
[] The [Audiences annual plan](https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2018-2019/Audiences). This has the specifics projects the whole department (almost) will be working on for next 11 months, as well as the metrics we've picked to measure them. The main focus is on contribution tools (which means "the Readers team" is no longer an accurate name, although we haven't changed it), and the secondary focus is on better use of data, so there's //plenty// to keep us busy! 馃槢
[] The Community Health Initiative's [separate annual plan](https://meta.wikimedia.org/wiki/Community_health_initiative/Annual_plan_FY18-19). The [Community Health Initiative](https://meta.wikimedia.org/wiki/Community_health_initiative) is a cross-departmental program of Community Tech's Anti-Harassment Tools team, which you'll be working with, and Community Engagement's [Trust and Safety](https://meta.wikimedia.org/wiki/Trust_and_Safety) team.
[] Marshall Miller's research and recommendations around the better use of data program ("the Marshall Plan"). There's an email out to him asking for the best links.
== Other team specifics ==
Read about [Analytics Engineering](https://wikitech.wikimedia.org/wiki/Analytics)'s annual plan work
[] [Smart tools for better data program](https://www.mediawiki.org/wiki/Wikimedia_Technology/Annual_Plans/FY2019/TEC14:_Smart_Tools_for_Better_Data)
[] [Modern event platform program](https://www.mediawiki.org/wiki/Wikimedia_Technology/Annual_Plans/FY2019/TEC2:_Modern_Event_Platform)
= Accounts and communications =
[x] Confirm your access to your staff SUL wiki account鈥擮ffice IT will create the account for you, so you should receive a password reset email. They will probably name the account "MWang (WMF)", but if you want something else, like "Nettrom (WMF)", [Trust and Safety](https://office.wikimedia.org/wiki/Trust_and_Safety) can rename it for you. You can contact them at ca@wikimedia.org.
[x] Edit your staff account's CSS and/or JS so that it's easily distinguished from your personal account. (Might I suggest the version from [my global JS](https://meta.wikimedia.org/wiki/User:Neil_P._Quinn-WMF/global.js)? 馃榿)
[] Confirm your access to your [Office wiki](https://office.wikimedia.org/) account.鈥擮ffice IT will also create this for you.
[] Confirm your access to the [Product Analytics team drive](https://drive.google.com/drive/folders/0AOfflhB7kgNjUk9PVA). This access
[] Consider creating a staff Phabricator account. This isn't required, but you may want to distinguish your staff and volunteer activity.
== Email ==
Join the following lists (see [office:Mailing lists](https://office.wikimedia.org/wiki/Mailing_lists) for instructions if necessary):
[] analytics@lists.wikimedia.org
[] contributors-internal@wikimedia.org
[] research-internal@lists.wikimedia.org
You //may// also want to join wikitech-l@lists.wikimedia.org, which is a public list for general discussion of Wikimedia engineering. It's focused on software development, so it's not highly relevant to our work, but it can be helpful in keeping abreast of which engineering projects are underway.
Verify that you're subscribed to:
[] wmfall@lists.wikimedia.org
[] wmfreqs@lists.wikimedia.org
[] product-analytics@wikimedia.org
Lists ending in @wikimedia.org are Google Groups, so go to [https://groups.google.com/] with your staff email account to see your subscriptions. Lists ending in @lists.wikimedia.org are Mailman lists, so go to [https://lists.wikimedia.org/mailman/listinfo/{{listname}}] and enter your email address under "change your settings or unsubscribe" to check.
[] Set up email filters so that mail from most mailing lists bypasses your inbox and goes to a folder which you can check occasionally. You don't want to skip this ;)
== Calendar ==
[x] Set up your Google Calendar so that meetings you create are modifiable by other attendees by default. This is found under settings > event settings > default guest permissions.
== Instant messaging ==
[] Get familiar with [Hangouts Chat](https://chat.google.com/)
[] Join the appropriate [IRC channels](https://office.wikimedia.org/wiki/IRC). The only private one I know of is #wikimedia-staff鈥攊nstructions for getting added are on that wiki page. Product Analytics doesn't use IRC, but many in Audiences and Technology prefer it.
= Profiles =
[] Add a profile photo to your staff G Suite account.
[] Set up a Meta-wiki user page for your staff account. You don't need to do it on any other projects; the one on Meta will already be mirrored to other projects.
[] Add yourself to [our team page](https://www.mediawiki.org/wiki/Product_Analytics#Who's_on_the_team?)
[] Add yourself to the [Office wiki contact list](https://office.wikimedia.org/wiki/Contact_list). This is a good resource when you need to urgently contact other staff.
= Meetings and team integration =
The following is a list of people you should meet with to get to know them (if you don't already) and to hear about their work and their current priorities. It's up to you how long to schedule these for鈥擨'd generally recommend an hour so you can have a comfortable conversation, but 30 minutes could work too if they're busy. This will add up to a significant chunk of time, so you can space these out over the next several weeks or a month: there's no rush. I've batched some of these together, but feel free to tweak that if you see a better way.
=== Product Analytics ==
[] Set up your weekly 1-on-1 with Jon Katz
You'll definitely see a lot of us other analysts during team meetings (which I'll invite you to), but at some point you should have a one-on-one conversation with each of us so we can discuss our skills, interests, and current projects and get to know each other personally.
[] Neil Quinn
[] Mikhail Popov
[] Chelsy Xie
[] Tilman Bayer
=== Growth ===
You are embedded in the [Growth team](https://www.mediawiki.org/wiki/Growth), which means you'll form part of the team on a day-to-day level. That also means you should prioritize these meetings (Marshall has probably already scheduled his) so you can get started on that work at the same time you work through this list.
[] Get added to their standups
[] Get added to their mailing lists, chat channels, and so forth
You should set up one-on-one meetings to get to know the following people:
[] Marshall Miller, product manager
[] Jazmin Tanner, program manager
[] Ryan Kaldari, engineering manager
[] Beno卯t Evellin, community relations specialist
[] Roan Kattouw, lead engineer
=== Community Tech ===
You're also assigned to [Community Tech](https://www.mediawiki.org/wiki/Community_Tech), which means you're on call for reactive support. You should decide with the team what that means (e.g. which recurring meetings will you attend? which communication channels will you follow?).
Have introductory meetings with:
[] Joe Matazzoni, product manager
[] Niharika Kohli, product manager
[] Trevor Bolliger, anti-harassment tools product manager
[] Moriel Schottlender, lead engineer
== Others ==
The other Contributors product managers:
[] Dan Garry, [Editing](https://www.mediawiki.org/wiki/Editing_team)'s product manager
[] Pau Giner, Runa Bhattacharjee, and Amir Aharoni, the [Language](https://www.mediawiki.org/wiki/Wikimedia_Language_engineering) leadership triumvirate
[] Danny Horn, director of product
Some key people in Research and Analytics:
[] Nuria Ruiz, analytics manager
[] Andrew Otto and Dan Andreescu, engineers
[] Dario Taraborelli
Key people from [Community Relations](https://meta.wikimedia.org/wiki/Community_Relations), formerly known as
[] Erica Litrenta, manager
[] Sherry Snyder and Nick Wilson, community relations specialists