Webmaker/Get Involved

From MozillaWiki
Jump to navigation Jump to search

Webmaker Engagement Ladder

Webmaker Engagement Ladder.jpg

  • This is the canonical home for the Mozilla Webmaker engagement ladder. Plus metrics for measuring against it.

Contributors

WEBMAKER CONTRIBUTORS do three things:

  • TEACH, BUILD and ORGANIZE

Teaching

P1

  • Teaching. Teach web literacy with our stuff. In classrooms, informal spaces and at events.

P2

  • Assessment. Review and critique learners' and mentors' work (e.g., to review and issue Webmaker badges)
  • Curation. Gather resources that help others learn and teach the web. Organize community-contributed content.
  • Support. Help with documentation and Webmaker product support.
  • Advocacy. Advance web literacy. Tell the story. Recruit more contributors.

METRICS

  • # of Webmaker mentor badges issued
  • + other good ways to measure teaching?
    • Key design challenge: other ways to fully measure teaching
      • Relying solely on badges issued here risks under-reporting our actual numbers and impact.
      • We may also need ways people to self-report. Or easily indicate: "I did this."
      • Sample use cases we want to measure: "I spent an hour teaching Web Literacy in my middle school classroom." "I taught this at home with my kids."

Building

P1

  • Content. Create curriculum and content for Web Literacy Map. Teaching kits, activities and resources.
  • Code. Submit patches to Webmaker tools. Experiment in new areas like Appmaker.
  • Localization. Remix, translate and localize content and tools.

P2

  • QA and User Testing. Ensure the quality and diversity of Webmaker offerings. Participate in live and asynchronous testing.
  • MakeAPI. Integrate with and build on top of the MakeAPI.

METRICS

  • # of content contributors. Users who tag items using web literacy map on webmaker.org.
  • # of patch submitters. Users who submit a patch (not just file a bug) on Bugzilla or Git Hub.
  • # of localizers. Users who make a significant contribution to localizing through Transifex.

Organizing

P1

  • Events. Host an aligned event (for Maker Party or Hive) or session (MozFest, DML, etc.)
  • Local networks. Grow existing Hive networks and establish new ones.

P2

  • Campaigns. Participate in and partner with Maker Party. Organize local campaigns and outreach.
  • Training. Train other trainers, teachers, organizers and mentors.
  • Partnerships. 'Bulk recruiting' contributors via like minded orgs and networks.

METRICS

  • # of event hosts on webmaker.org
    • Note: this metric also serves as a measure of Hive activity as well

Supporters

  • coming soon

Users

  • coming soon

Building a dashboard

  • What do we need to build and wire up to capture this data? (draft only)

ugwxv3jd.png

Who is our community?

Our community members seek to:

  • level up their web literacy
  • build and share tools for teaching
  • gain peers and networks of practice
  • participate in coordinated actions
  • identify with a movement that's globally leveraged and locally contextualized

Below is a graph of our “lead users”. These are the types of community members who are most invested in the project. The graph is merely illustrative, not exhaustive. Its purpose is to sample the motivations of our community members and visualize how those compare to one another.

Webmaker community lead users.png


Webmaker-four-key-audience-segments.003.jpg