Mozilla has a goal this year to grow the number of active contributors by 10 times. We’ll be able to achieve this by tapping into several different opportunities that let us connect with new contributors at scale. Some of those are:
70,000+ people (~200/day) will reach out through the Get Involved page this year to let us know they want to contribute
100,000+ people have already taken their first steps on the QA contribution pathway by installing and using Nightly builds
The numbers of people who have reached out to us through those tools is a powerful example of how Mozilla’s mission resonates and gets people excited to want to help.
We can connect these people to Mozilla initiatives—we just need to get better about identifying and sharing out contribution opportunities and making use of the tools above.
If you have information to add about these tools or know of other opportunities to connect with people at scale, please feel free to update this etherpad. We’ll take these notes and make a guide for people interested in building communities around their projects.
Michelle Marovich is preparing to run the Designing for Participation workshop for the People team. She’s looking for some real world examples that can help make the concepts concrete for everyone, so she set up a Contribution Madlib template for people to fill out.
Mine is below. It would be great to see your version of the Madlibs—just replace the underlined sections with information about a project you’ve designed for participation.
I want to create a local Mozilla community in Antarctica, I need several people to help me on it therefore I will write a blog post that syndicates to Planet Mozilla and reach out directly to people that I know are interested in this in order to publicize the work.
Then I start an email thread with people who have responded to the idea and identify a place in IRC where we can continue the discussion in order to engage with the people who are interested. I break the work down into tasks by having a group discussion about what we can do in order to see what emerges and then asking for drivers for the different ideas that were generated.
I communicate those tasks by creating a list of people who want to be a part of this team and writing down who is doing what. So that we can work effectively together, I always make sure that we are continuing the discussions in IRC. I continue to raise awareness of the work by evangelizing what the group is doing by writing more blog posts, posting to Facebook and using other project channels.
I communicate decisions and progress by delegating this to the people on the team who want to drive the project management. When we achieve a milestone, reach a goal, or someone does something amazing I recognize them by thanking them publicly for all of their hard work.
Last week over 50 staff and volunteers got together in San Francisco for a Community Builders meetup. The goal was to create plans for 2014 for how to support all community building efforts across Mozilla.
We organized around a set of tracks for systems and data, pathways, education and culture, recognition, and events. Each track focused on creating concrete action plans for next year and then we shared this out through a brown bag at the end of the week.
Many people worked hard to make this a success and I’d like to thank everyone who planned for this event and thank everyone who took part. In particular, I’d like to thank people who took part remotely and dialed in from all over the world during all sorts of different local times.
It was a great experience for me to help get the Fairs set up and I really enjoyed the experience of visiting all the booths.
I have to admit that when I was doing that though, I wasn’t very good about taking pictures and instead grabbed some of the great swag that some booths were offering.
Seeing how local communities adapt parts of Mozilla and make it their own is fascinating and I picked up cool stickers from Mozilla Romania, Mozilla Ukraine, Mozilla Taiwan, Mozilla Hong Kong and Mozilla Indonesia.
If you have pictures from your experience at the Summit Fairs, feel free to post them on the wiki to document all of the great stuff that happened there.
Austin describes a journey where he progressed from being a user to a supporter promoting our products and then to a contributor hacking on Mozilla code. It was only when he had reached a core contributor position that he considered himself a Mozillian.
At that point, he definitely met the criteria of belief, action and interaction that came out of the Summit sessions. It’s great to honor anyone who has reached that point, but we should also be honoring people when they begin their journey in Mozilla.
I think we should extend the meaning of ‘Mozillian’ to cover anyone on their journey of believing in our mission, taking action to support it and interacting with other community members—even if they’ve only just started on their path.
This means we will probably need to identify specific milestones on the journey and call those out. That seems like something that other movements do too—for instance, the Girl Scouts have many levels of involvement but everyone involved is a Girl Scout.
I realize this changes the current use of applying this word to people who have progressed through much of that journey. To include a million more Mozillians in our community though we’ll need to be more intentional about finding and honoring people who are starting their journey.
I’ve been thinking about Gerv’s recent summary of the What Does ‘Mozillian’ Mean? sessions from the Summit. The three criteria that came out of those sessions seem useful to me:
Belief in the mission
Action to support the mission
Interaction with other community members
One way these criteria could be used is to clarify the community definitions we created a couple years ago that describe how Mozilla is made up of users, supporters, casual contributors, active contributors and core contributors.
The definitions we’ve been using are a little vague. For instance, a casual contributor is someone who has volunteered small amounts of time. But how much time is that? How does that differ from a supporter who also donates time to Mozilla?
Using these criteria can give us clearer definitions. Casual contributors and supporters both give something to help the project, but casual contributors interact with other community members (eg, going to a Bug Day) and supporters don’t (eg, making a donation).
It’s not clear though if these criteria define a Mozillian or if they define something else, such as who a Mozilla contributor is. We talked about this at last week’s Grow Mozilla discussion and there were two different thoughts.
One was that the word ‘Mozillian’ should be reserved for people who met all three criteria. Others thought that this doesn’t capture the important part of our culture that allows people to self-identify with our mission and they thought ‘Mozillian’ worked better as something inclusive that anyone could use.
I think we want words to describe both sets of people. Knowing who meets these criteria lets us do things such as figure out who we want at a Summit. Knowing who identifies with our mission lets us establish relationships with people who can become more deeply involved with the project.
I’m interested to hear what other people think. How would you define ‘Mozillian’?
I’m looking forward to the discussion at the Summit about What Would A Million Mozillians Do? To help me and the other organizers think through this session, I wanted to post some thoughts to get feedback.
As a starting place, it makes sense to highlight that a million is a big number—it’s almost 2 Luxembourg’s worth of Mozillians. Although it’s a big number, it’s something we could do.
The question then is what would all of those people do? We can begin to answer this by looking at how far we can deepen existing contribution opportunities and then look at how far we could broaden opportunities to new areas.
There are all sorts of questions that come out of this, so in the session we could have interesting breakouts to discuss what the contribution opportunities could be, figure out how we could logistically and culturally grow to this size, and identify who else is building communities of this size that we can learn from.
If this sounds interesting to you, join us for the session on Saturday at 1:30pm and also comment here with any thoughts or suggestions.