|
|
| Line 8: |
Line 8: |
| ** Diversity and inclusion - who is welcome at Mozilla (spoiler: everybody) | | ** Diversity and inclusion - who is welcome at Mozilla (spoiler: everybody) |
| ** Interaction style - how to work with other people | | ** Interaction style - how to work with other people |
| | | * [https://mana.mozilla.org/wiki/display/TAS/Contributor+Funnel Contributor Funnel] (guidelines for staff in welcoming contributors) |
| === TODO ===
| |
| | |
| * good first bug guidelines | |
| * list of carrots on mana, linked from here
| |
| | |
| == Contributor Funnel ==
| |
| | |
| People come to TaskCluster in a variety of ways. We want to gradually get them more involved in the project. We do that by moving them through the contributor funnel. The sections below outline the stages of this funnel.
| |
| | |
| === First Contact ===
| |
| | |
| So a new contributor has appeared and is hacking on a bug. We want to be able to recognize their work, share the context for it so we can answer questions, and encourage more engagement with the project and team.
| |
| | |
| The first time someone new arrives on the project, welcome them to the team as quickly as possible, and help them get started.
| |
| | |
| * If they have commented on a good-first-bug in bugzilla or github, answer the questions and help them to get started, assign the bug, and suggest asking any questions in #tc-contributors.
| |
| * If they have appeared in channel, talk briefly about what they are interested in, or what has drawn them to TaskCluster, and then find a good task for them to work on:
| |
| ** A [http://www.joshmatthews.net/bugsahoy/?taskcluster=1&simple=1 good first bug]
| |
| ** Setting up a personal github project such as a blog with taskcluster-github
| |
| | |
| Lots of contributors *only* ever make first contact, so try to balance your time against being welcoming: give them a single next step, and hold off on further investment until that step is complete.
| |
| | |
| === First Success ===
| |
| | |
| Once they have had a few bits of interaction, or a patch reviewed – shown at least a little commitment – add them to the list of "Contributor Reference" document in google docs. Please try to keep all of the person's names (irc, email, bugzilla) in the title so they are easy to find in the table of contents. Link to the projects they're hacking on and any other notes about interests or skills. This helps the whole team to share context about a contributor. Don't put anything too personal in there!
| |
| | |
| Include your name as the "mentor". This doesn't mean you have to answer all of their questions -- it just means you're responsible for trying to keep them engaged, following up when you haven't heard from them; and that you can help other team members get introduced.
| |
| | |
| === Video Introduction ===
| |
| | |
| When it becomes clear the person is interested in sticking around (they ask "what next", for example), invite them to a video chat (google hangouts or skype) with one or two team members. This both shows our commitment, and helps us to get to know the contributor better. Record some notes in the google document. Topics include:
| |
| | |
| * Welcome – you're part of the team, and we want to hear your input.
| |
| * Interests – what brings them to Mozilla, to TaskCluster, etc.
| |
| ** Examples: "I'm looking for experience with the OSS development process." "I want practice with specific kinds of software development." "I want to support Mozilla." "I want to help other developers." "I want experience maintaining an OSS project."
| |
| * Needs – how can we help support their interests?
| |
| * Working in Public - asking questions in channel or on bugs/issues, instead of emails and PM's
| |
| * Questions - ask me anything!
| |
| * What is TaskCluster? - from someone outside of Mozilla, it's hard to even understand the basics
| |
| * Ownership – TC is structured as a bunch of small services, and each needs someone to look after it, making bug fixes and deciding on new features. They could own a component!
| |
| * Next steps - find something for the contributor to work on that fits their needs and interests
| |
| | |
| === Ongoing Contributions ===
| |
| | |
| ==== Follow-Up ====
| |
| | |
| As the contributor continues their involvement, keep up to date with them. If you haven't heard from them in a while, send an email. It's normal for things to change, but we'd like to know when that happens. A simple "Hi, I haven't seen any updates from you in a while. How's it going? Anything I can do to help?" can often jump-start things.
| |
| | |
| ==== Team Members ====
| |
| | |
| We want contributors to feel like they are part of the TC team, and that means not only interacting with staff, but with other contributors. Look for opportunities to connect people working on related projects, perhaps doing reviews or working together to solve a problem.
| |
| | |
| ==== Rewards ====
| |
| | |
| We have a long list of rewards and ways of saying thank-you. Use these liberally, but strategically: encourage further contribution and team membership. Make notes of what rewards have been given in the google doc.
| |
| | |
| * Invite to the weekly team meeting (especially to show of some cool new feature)
| |
| * Vouch for them on Mozillians
| |
| * Thank them in the WeeklyUpdates meeting as a friend of the tree (and tell them so they can watch!)
| |
| * Add their blog to the [https://planet.mozilla.org/taskcluster/ Taskcluster Planet] blog aggregation
| |
| * Add their name to [https://dxr.mozilla.org/mozilla-central/source/AUTHORS AUTHORS] (anyone who has contributed patches to the Gecko tree is eligible)
| |
| * Thank them with the [https://docs.google.com/a/mozilla.com/forms/d/e/1FAIpQLScJ_U1uUrDKRXK4U3gUMInpRvEt3I1c9uBSpu0c54UX8KgZig/viewform?c=0&w=1 Release & Productivity Recognition & Thanks program] (yes, it's open to anyone!)
| |
| * Offer to send a team T-shirt or stickers (check availability first, and note that sending T-shirts across borders is stupidly expensive, but stickers fit in an airmail envelope)
| |
| * Depending on location, invite them to a conference you or someone else on the team are attending
| |
| * Invite to an all-hands (note that this is reserved for strong contributors who will be able to contribute substantially more having attended; it's not a reward, per se)
| |
| * Invite to give a [https://public.etherpad-mozilla.org/p/jonasfj-tech-topics tech topic]
| |