How do we grow a community of contributors and architecture of participation around Mozilla Webmaker tools?
This post is a synthesis of ideas collectively brainstormed by the Webmaker community in Tuesday’s call. It’s part two of a discussion Mark Surman began with his “Tools for Webmakers” post. The ideas here aren’t mine — they’re everybody’s. :)
Contribution is the goal
We’ve said we want to make contribution the metric that defines all our work. That includes building Webmaker tools like Popcorn, Thimble and the X-Ray Goggles. Popcorn already has a growing community of developers contributing code. OpenNews is creating and sharing great code as well. And Thimble is, of course, just out of the gate, with a question around when and how best to build an architecture of participation.
So as we think about our plan for the rest of year and into 2012, where do we go from here?
Four keys to involving contributors:
- Tasks. Calls to action.
- Documentation. Training
- Celebration. Kudos.
What kinds of contribution are we seeking?
What kinds of contributors do we want to work with and get to know better, over the next 6 – 12 months? We want to grow a community of contributors around building Webmaker tools in particular. And of course also plant seeds and build a community around webmaking in general, with Webmaker as a big tent for lots of different people and groups.
Where do we need to build better on-ramps for participation?
- Code. We know there’s a small group that want to contribute to the “core” library — of a similar order of magnitude as people who submit patches to Firefox, for example.
- Make it easier to submit. Build systems that let contributors submit this type of code without our review or evaluation. Via plug-ins, for example? or something comparable to addons.mozilla.org?
- Avoid bottlenecks. We can easily become a bottleneck to our developer contributors. For example, if they need to conform to our style guide, or review a patch while we’re in the midst of an important release. More and better “remix / fork this project” options?
- One idea: provide easier ways to turn your Popcorn or Thimble project into a template. Like a “save as template” option in the Popcorn and Thimble apps. That way, you could use the Popcorn “Newscast” template, for example, to turn it into a “Call to Action” video for your campaign — then save it as a “Call to Action” template other people could use the same way.
Things we need:
- Better documentation and HOW TOs. “Cook books.” Easy step by step instructions on how to contribute. Better FAQs. We have lots of rough and ready etherpads and raw notes — we need more polished HOW TOs for contribution.
- Great examples. Project galleries, etc.
- Better on-boarding. Clarifying where to go, what channels to use. Setting expectations. Friendly humans with time to help.
Avoiding the “busyness trap”
“We’re too busy to help!” This was a commonly acknowledged problem. When we’re heads down and focused on shipping and meeting the next deadline, it’s easy to feel like you’re “too busy” to be able to bring community members into the fold. We need people to feel like we have time for them. And that they’re actually a priority.
“Should we create ‘20% time’ to focus just on creating systems and documentation for more and better community contribution?”
Get involved: how do we make our current documentation better?
One place to start might be to look at our current contributor documentation for Webmaker tools. Then have you suggest ways it can be improved. Or volunteer to work on it yourself. All of this is going to see dramatic improvements over the coming weeks and months. But let’s start by listing what we’ve got — specifically for contributing to Mozilla Webmaker tools and software.
- Popcorn: https://wiki.mozilla.org/PopcornMaker
- OpenBadges: https://wiki.mozilla.org/Badges/roadmap
- Thimble: https://etherpad.mozilla.org/thimble-roadmap
- Others: please list in the comments.
(This list is incomplete — please help flesh it out in the comments to this post and I’ll update.)