I’d like to share some thoughts on a “Webmaker Special Interest Group” for the Mozilla Reps program.
This conversation owes a lot to many Reps and Webmakers so far; in particular, a huge thanks to Henrik Mitsch, William Quiviger, and Pierros Papadeas for supporting the idea and for your thoughts to propelling it forward.
What is a Special Interest Group (SIG)?
Firstly, what is this SIG jargon?
A Special Interest Group is a group within the Mozilla Reps program that has a particular interest in a specific area of the Mozilla project. These groups are created to help Reps to sharpen specific skills and work more closely with Mozilla staff responsible for those projects. SIGs are also key drives of participation and new volunteer opportunities.
Currently, Mozilla Reps has 10 SIGs. A very successful one is the Evangelism SIG, mentored by Christian Heilmann and Shezmeen Prasad. It skills up Reps as public speakers and open web evangelists. This SIG offers a number of valuable things, including in-person trainings, mentorship, toolkits, budgets, and events.
How did the Webmaker SIG conversation start?
1. Summer Code Party participation
One of the strongest indications towards a Webmaker SIG was the amazing leadership and participation by Reps during the Summer Code Party. We recently ran an event campaign, encouraging people to grab their friends and a laptop and hack together over the summer. 44 Reps organized events, and they were by far and away some of the most inspiring and impressive events around the globe. From Argentina to Switzerland, Romania, India, the Philippines, Kenya, Nigeria, and beyond, Reps led the way with some of the best documentation and turnouts at Summer Code Parties.
What’s more, they were also involved in shaping the campaign from the beginning, betatesting the event formats and even building Thimble projects (thanks, Fuzzy, for the zombies!). It was clear from #mozparty that Reps operate at a profound level of participation, knowledge and willingness to experiment.
2. Conversations with Reps
Building on the momentum from the Summer Code Party, a number of us on the Webmaker team chated with Reps about the ways to weave together the ReMo program with Webmaker projects and methods.
Some of these ideas were shared on the Webmaker and Reps-General mailing list, and other came about on community calls or quick IRC chats. The ReMoCamp2012 kindly invited me to discuss the latest Webmaker initiatives and invite Reps to get involved.
3. Mozcamp Europe session
From there, it seemed there was enough general interest from the Reps community to pursue the Webmaker SIG more fully.
We put in a proposal at Mozcamp Europe to run a session with Reps to hear about what they want out of this program and how it could take shape.
About 40 Reps joined in the conversation, with many more saying online they’d participate if they had been in Warsaw. The feedback was incredibly positive.
Most Promising Opportunities
This is a summary from our Mozcamp Europe session. You can check out the full notes on the etherpad and add to them.
- Lead peer learning and mentoring, including teaching people how to run Webmaker events. A great example of this is Mozilla Rep Gauthamraj from Erode, India who’s teaching a young webmaker to how to hack the web and even organize her own events with friends.
- Organize outreach and trainings, especially for local schools and instructors. Design local learning campaigns tailored to their area. We can see some great beginnings to this approach, led by Reps in Pune, India and Victoria, Canada.
- Online support for anyone running events and using Webmaker projects.
- Write, improve and localize documentation for people learning the web. This could perhaps build upon the newly launched Web Platform Docs, adapting it to make accessible for beginners. There’s also the excellent Mozilla Developer Network (MDN) full of documentation which could be extended, simplified and otherwise customized for webmaking.
- Spearhead the Webmaker localization process and infrastructure. At the moment, Webmaker is very weak on localization. We know this is one of the most important things to get right, and Reps could really help us learn how to set up the right processes and tools to make it sustainable and effective.
- Craft new learning missions. These could be built on existing Mozilla tools, like Thimble and Popcorn Maker, or even around other great learning tools, like App Inventor.
- Push innovation on the edges. As Henrik Mitsch described it, Reps are also in a perfect position to explore “Grenzwissenschaften”, the science on the edges. As skilled web developers who think creatively and with the community in mind, Reps can lead the way with code contributions. This could be coding directly with tools like Popcorn.js, OpenNews’ Source, Thimble, etc. or shaping new things.
- Collaborate with coder communities. Reps are often well-networked with local and global developer communities. It’s a great opportunity to hack with these broader groups and innovate together around projects that teach and push the web forward.
- Identify and hack on much-needed features. There are loads of features we’d love to ship. Having Reps help identify, design and develop these features would be a huge win. Offline Thimble, anyone?
I think these three categories, mentorship, documentation and code are very useful to start thinking of how to structure a Webmaker SIG to foster contribution in these areas.
To move forward, there are still a few open questions. We should tackle them on the mailing lists and IRC.
Membership criteria. Do you have to be a Rep to join the Webmaker SIG? Some SIGs are open to non-Reps, which is a powerful way to recruit new people who may not have heard about the Reps program before. On the other hand, there are huge benefits to working more concertedly with Reps, since the ReMo “standard operating procedures” (SOPs) ensure a level of quality and impact. What do you think? Should members of the Webmaker SIG be Reps?
Target instructors. The Webmaker program is looking at three instructor types. Which ones fit as target for Reps to focus on? i) Already teaching “web making”; ii) Already teaching, maybe not web making. (eg: camp instructor); iii) Second-generation teachers: people we could teach how to teach, and then they might. (ie: the learners becoming the teachers); iv) Other?
Coordination. Some SIGs have staff dedicating a good amount of time developing their programs. What’s the ideal scope of a staffer’s involvement, and what sort of time commitment would it require? This is an important resourcing question for the Mozilla Foundation, and by knowing how much time is needed and by whom, it could help push the SIG forward, quickly and effectively. What have you learned about the staff’s role in the other SIGs and how would you see a staffer/staffers contributing to the Webmaker SIG?
I hope this has been a useful summary.
It’s a mad time at the moment because of Mozfest, but here’s a proposal for next steps. It’s all hackable, so please chime in.
- Share proposal on Tuesday, October 23 on the Webmaker community call. Cross-post to the Reps-general list for discussion.
- Start fortnightly IRC meetings with anyone interested in developing the proposal. These can kick off on October 30, one week after the community call.
- Fine-tune the SIG in-person at Mozfest and Mozcamp Asia.
Keen to hear your thoughts! ^_^