Taskcluster/Deprecated/Participation: Difference between revisions

Taskcluster/Deprecated/Participation (view source)

Revision as of 22:23, 22 February 2017

2,685 bytes added , 22 February 2017

no edit summary

Djmitche

canmove, Confirmed users

1,394

edits

@@ Line 1: / Line 1: @@
-Welcoming New Contributors
+TaskCluster welcomes contributions from anyone who would like to participate.  As a part of Mozilla, and because we individually feel it is important, we strive to do our work in the open, and as much as possible to make it possible for anyone to be a part of the team - whether employed by Mozilla or not.
+This page is where we organize ourselves to make sure we do a good job.
+== Links ==
+* [https://www.mozilla.org/en-US/about/governance/policies/participation/ Mozilla Community Participation Guidelines] - covering:
+** Diversity and inclusion - who is welcome at Mozilla (spoiler: everybody)
+** Interaction style - how to work with other people
+=== 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.
-Once they have had a few bits of interaction, or a patch reviewed – shown at least a little commitment – add them to the list below. Please try to keep all of the person's identifiers 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.
-When it becomes clear the person is interested in sticking around (they ask "what next", for example), invite them to a video chat with some team members.  Topics:
+The first time someone new arrives on the project, welcome them to the team as quickly as possible, and help them get started.
-Welcome – you're part of the team, and we want to hear your input.
-Interests – what brings them to Mozilla, to TaskCluster, etc.
+* 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.
-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.  etc.
+* 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:
-Needs – how can we help support their interests?
+** A [http://www.joshmatthews.net/bugsahoy/?taskcluster=1&simple=1 good first bug]
-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
+** Setting up a personal github project such as a blog with taskcluster-github
-At first, encourage contributors to learn about how services are used and figure out their own improvements to work on
-Later, give them more control over the service (add as collaborator, etc.)
+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.
-Team Meetings – invite the contributor to our weekly team meetings
+=== 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 Contribution ===
+As the contributor continues their involvement,