What we're working on this Heartbeat

Mozilla

3 responses


Transparency. Agililty. Radical participation. That’s how we want to work on Webmaker this year. We’ve got a long way to go, but we’re building concrete improvements and momentum — every two weeks.
We work mostly in two-week sprints or “Heartbeats.” Here’s the priorities we’ve set together for the current Heartbeat ending January 30.
Questions? Want to get involved? Ask questions in any of the tickets linked below, say hello in #webmaker IRC, or get in touch with @OpenMatt.

What we’re working on now

See it all (always up to date): http://build.webmaker.org/now
Or access the work broken down by:

Learning Networks

  • Design & test new teach.webmaker.org wireframes
  • Get the first Webmaker Club curriculum module ready for testing
  • Finalize our documentation for Badges / Credentialing
  • Document our Q1 / Q2 plan for Training

Learning Products

Desktop / Tablet:

  • Improve user on-boarding (Phase II)
  • Improve our email communications after users sign up
  • Create better moderation functionality for webmaker.org/explore (formerly known as “the gallery”)
  • Build a unified tool prototype (Phase II)

Mobile

  • Draft demo script and plan our marketing activities for Mobile World Congress
  • Make localization improvements to the Webmaker App
  • Build and ship device integrations and a screenshot service for Webmaker App
  • Distribute the first draft of our Kenya Field Report

Engagement

  • Prep and execute Data Privacy Day campaign (Jan 28)
  • Prep for Net Neutrality Campaign (Feb 5)
  • Draft a branding plan for Learning Products and Learning Networks
  • Design a splash page for Mobile World Congress

Planning & Process

  • Design and execute a communications plan on our overall 2015 plan
  • Document all our Q1 goals and KPIs in one spot
  • Add those quarterly goals to our dashboard
  • Ship updated documentation to build.webmaker.org (including: “How we do Heartbeats” & “How to use Git Hub Issues”)

 
 

3 responses

  1. Brett Gaylor wrote on :

    Amazing!
    One thing I wanted to mention as we watch this “working open” work progress – often times when you get a few links in to the planning documents, you’ll find a google doc where you have to request permission to view.
    Most people are unlikely to want to request that access – could be worth the team always trying to make those docs open. I wonder if there’s a google doc setting to default to open……

    1. Matt Thompson wrote on :

      Great point, Brett. I’ll look into the “default Gdocs” to open route. Maybe even more directly: we’re going to try and spin up an etherpad instance that’s so good, people will prefer using it over Google Docs. Working on that with JP here: https://github.com/MozillaFoundation/mofo-lightsaber/issues
      Etherpad has a lot of plug-ins and tweaks that can actually make it pretty comparable — without the hassle of log-in, permissions, or crummy URLs.

  2. Greg wrote on :

    I run into the request access link all the time when hitting a Google Doc and figured to documents are deliberately open to employees on that specific project. Figured it was some corporate policy.
    I never request access when prompted.