Webmaker/Workweek: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 83: Line 83:
== Webmaker engagement ladder ==
== Webmaker engagement ladder ==
* https://wiki.mozilla.org/Webmaker/Get_Involved
* https://wiki.mozilla.org/Webmaker/Get_Involved
* bugzilla whiteboard: [workweek][workweek-engagement]
* bugzilla whiteboard: [workweek][workweek-engagement] [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=whiteboard%3A%5Bworkweek-engagement%5D search]
'''Goals'''
'''Goals'''
* Tickets for quick wins that make it easier for people to climb the ladder.
* Tickets for quick wins that make it easier for people to climb the ladder.

Revision as of 00:47, 31 January 2014

Webmaker Workweek

  • Feb 3-7, Toronto
  • Pocket agenda: http://cl.ly/TdCX
  • Bugzilla whiteboard tag: [workweek]

risz-2v8.png

Who's coming?

vXRPSmwqaECZBcqcTaU1bRih.gif https://webmaker.etherpad.mozilla.org/feb2014workweekattending

What we're shipping

jpbuck240.gif

  • Engagement Ladder. Quick wins that make it easier for people to climb the ladder. Plus a dashboard for measuring contribution.
  • A contributor metrics service. Prototype for "MakerMind," a new Webmaker.org service that listens for contributor activity to feed it into a dashboard, BadgeKit, etc.
  • Web Literacy UX. Prototype user experience for the Web Literacy Map.
  • Content. Fill the Web Literacy Map with our best current content. Make a punchlist of gaps. Prep a pilot for a community content sprint to fill them.
  • "Teach the Web" training. Polished packaging and a schedule for our online course and training.
  • Maker Party. A documented plan for what we're doing this year. Tickets for shipping better events UX.
  • Metrics. Knowledge transfer. Best practises for building metrics into all of our software. Running data analysis, A/B tests, and campaigns. A website metrics dashboard.
  • New markets. A plan for which new locales and communities will webmaker engage with in 2014
  • Localization. Planning and technical strategy for "right-to-left languages."
  • User testing and co-design. Kits that make it easy for community to run user testing events.
  • Code contribution. New approaches for making code contribution easier.
  • Firefox integration. Demos of new approaches for integrating Webmaker within Firefox.
  • Skillshares. Bootcamps and demos. For Front End best practices, MakerStrap, DevOps, working with Bugzilla and Github, how to develop in Webmaker, + more.

Scrums

Our week will be divided into groups of tasks we call scrums. Participants at work week will undertake tasks from a variety of scrums. The week is focused on outcomes and specific work that Webmaker team has identified.

IMG_6028.jpeg


Web Literacy UX

When?

  • Mon - Content review. Teaching Kits. User types & paths. Brainstorming.
  • Tues - Refine designs. Wireframes. Begin building.
  • Wed - Continue building prototype. Create image assets.
  • Thurs - Supporting functionality (eg, tagging). Copy.
  • Fri - Final prototype

Tasks

1) Content Review

  • Consider new approaches for teaching kits. How will badges work into the flow? UX for new kits.

2) Brainstorm

3) Prototype

4) Refine

Web Literacy Content

  • https://etherpad.mozilla.org/WebLitcontent
  • [workweek] [content]
  • Fill the Web Literacy Map with initial content. Collect the best existing teaching kits and resources. Tag them. Then invite community to review, fill gaps, and flesh out further. Develop a pilot for a community sprint.
  • Owner Kat

TASKS

PREP WORK


Webmaker engagement ladder

Goals

  • Tickets for quick wins that make it easier for people to climb the ladder.
  • MakerMind prototype.
  • A dashboard for measuring contribution.

Owners: Michelle / Jbuck

Scrum Tasks

  • 1) Prototype MakerMind: a service for counting contributors across Webmaker.
    • Finalize what actions count as contributions that MakerMind should track bug
    • Create a module to send user actions from each server to MakerMind bug
  • 2) Build an MVP contribution dashboard
    • Build some prototype dashboards in Kibana bug
  • 3) Identify UX improvements to Webmaker.org that will funnel people towards contribution. File as tickets. Include plan for testing & measuring results.
    • e.g., Re-vamped welcome email.
    • "Explore" button goes nowhere. <--being fixed in web lit ux track
  • 4) Optimize our use of email.
    • Document email actions. For each rung of the ladder.
    • Then: Write copy for email actions.
    • Updating Webmaker.org welcome email: https://bugzilla.mozilla.org/show_bug.cgi?id=948637
    • Cross-over with l10n: we need to think about localizing these emails we send out
  • 5) Simplify and optimize communications channels. Simplify, combine and operationalize social and other channels (eg combine @webmaker + @mozteach, tumblr vs blog. what to keep and how to use to leverage the following) https://bugzilla.mozilla.org/show_bug.cgi?id=965473
    • Document our plan for Webmaker mentors badges.
    • Establish Baseline contributor #s from last year. Publish them on the Webmaker wiki. [michelle to ticket]
    • Create an engagement timeline that will attract and onboard new contributors.
    • Prospect lists for engagement outreach. Work out system(s) to flag up potential contributors for individual outreach.
      • e.g. list of all GitHub users who have forked a webmaker project, but haven't contributed yet.
    • Document Webmaker's "1M Mozillians plan". Publish a text / blog post on how Mozilla Webmaker engagement contributes to 1M Mozillians
  • Platform tasks
    • Move postal service from integrated into each app into a separate service that feeds from the makermind
      • This would be an excellent stretch goal for the work week
    • Have something (a node app, most likely) sitting in front of the ELK stack that can filter/prevent anyone from adding random events
      • We don't need to worry about this, as we'll be using redis to transport events from app server -> logstash. Protect redis with firewalls and a password, and we're good!
    • Use ELK (elasticsearch, logstash, kibana) stack set up by JP
      • He did this the week before. Go JP!
    • Discover if Logstash can do transformation/aggregation for us
      • It cannot

METRICS

Bugzilla whiteboard: [workweek][workweek-metrics]

  • When:
    • Mon: Testing and Optimisation
    • Tues: Webmaker Dashboard
    • Weds morning: Google Analytics for Developers. Weds aft: Google Analytics for Noobs.
    • Thurs: Web Literacy Metrics

Goal: Knowledge transfer and establish working processes. Best practises for building metrics into all of our software. Running data analysis, A/B tests, and campaigns.

Owner: Adam
Scrum tasks

  • Testing and Optimisation: Set up an A/B test for Webmaker.org
  • See some of the tests MoCo have been running on Mozilla.org
  • Add Optimizely tracking tag to webmaker
    • TICKET: [link]
  • Agree on process for setting up, recording and sharing A/B tests
    • TICKET for shipping this documentation: [link]
  • Set up an A/B (or MVT) test somewhere on webmaker
    • TICKET: [link]
  • BOOTCAMP: Google Analytics for Developers
  • BOOTCAMP: Google Analytics for Noobs
  • Ticket additional tracking we want to implement
    • TICKET: [link]
  • Ticket tests we want to run based on our insight
    • TICKET: [link]
  • Webmaker Dashboard
    • Update the site metrics dashboard for Webmaker.org.
      • Which metrics are currently used to make decisions? KPIs vs FYIs.
      • TICKET: [link]
    • Ship a public metrics dashboard for Webmaker.org. Drawing on the Webmaker engagement ladder https://wiki.mozilla.org/Webmaker/Get_Involved
      • blocker / design challenge: understanding & documenting the Webmaker "user" and "supporter" conversion points. Work with Engagement Ladder track on this.
      • TICKET: [link]
  • Literacy Metrics
    • Ship a draft definition of the metrics that indicate someone is becoming more web literate
      • TICKET: [link]
    • Ship a plan/tickets on how we can test this theory and implement extra tracking we may need
      • TICKET: [link]

For Discussion:

  • Other tools we want to explore / existing tools we should use more
  • Investigate Mozilla's Tableau infrastructure and decide:
    • What is it good for, for webmaker?
    • Next actions to make use of it

Prep work

Requested Reading

DevOps: making code contributions easier

  • bugzilla whiteboard: [workweek][workweek-devops]

Figure out ways we can improve our current processes, from provisioning of development environments easier to ways we can minimize effort and time required for pushing/testing.


Third-party publishing to Webmaker

Improving our platform systems (MakeAPI, Login) so that 3rd party apps can publish to webmaker.

Localization

Goals

  • Understanding which new markets, languages, locales are our priority in the short and medium term, especially trying to gain wisdom about Japan from our Mozilla Japan colleages joining the work week
  • Make sure we have a plan and process for evaluating the quality of our localized sites (user testing with l10n focus).
  • Build a plan and technical strategy for right-to-left (RTL) locales. Try and prototype one of our sites/tools for RTL.
  • Bugzilla whiteboard: [workweek-l10n]
  • Owners: Humph, Ali
  • Scrum tasks
    • Right-to-Left (RTL) Planning: what's our strategy/architecture for doing this? We need a technical arcitecture for doing the CSS and Layout so it works LTR and RTL. This will involve our front-end gurus. https://bugzilla.mozilla.org/show_bug.cgi?id=965406 (Tues AM)
    • Priority of Languages/Locales: decide which languages/locales we want to focus on (i.e., go to market strategy for that locale). Maybe lang/locale tiers? What is the process for turning new langs/locales 'on' on production. If one of our tools is 100% in lang XX, do we turn it on? https://bugzilla.mozilla.org/show_bug.cgi?id=965412
    • Webmaker and Japan: what needs to be done specifically for Webmaker and Japan, any specific things for us to know, etc. Knowledge transfer between Webmaker team and Moz Japan folks joining work week. https://bugzilla.mozilla.org/show_bug.cgi?id=965416
    • Localization User Testing: how good are our translations in each locale/lang we ship? We need a process to determine this and fix. https://bugzilla.mozilla.org/show_bug.cgi?id=965417
    • Community Managment of our Transifex community: do we need to do anything? How should we share the management of this beyond Ali?
  • Post Work Week Priorities (individual tasks that could be done or put off):
    • Make language setting per-user vs. per-site (user setting, per session, ???)
    • UX for MakeAPI for localized searches
    • Localized Emails, especially auto-generated
    • Site banner/CTA to indicate lang/locale is not complete, and links to help translate, etc.
    • Automation to auto-upload translation files to Transifex when something changes in en-US
    • Can we co-ordinate with MDN for details we share with them (e.g., HTML and CSS info in Goggles/Thimble)?
    • Locale file info in healthcheck, to show how recently l10n translations where downloaded
    • Improve L10N Responsiveness of our Tools: we need to audit for things like widths/height. We've fixed in webmaker.org, but missed a lot in our tools.
    • Localization of Teaching Kits and other Makes. We don't have any automated/Transifex way of doing this now.
    • Need to educate people on using Tutorials vs. inline HTML comments in Thimble--this makes localization much easier.
    • Prompt users for locale on publish
    • Display appropriate locales on Webmaker.org locale (ie pt-br content on webmaker.org/pt-br/)

Maker Party

Develop the framework and planning for the 2014 MP campaign.


Scrum tasks:

  • Document our plan for Maker Party 2014
    • Comms tasks
      • Narrative. Document how we're fitting MP into the overall MoFo comms arc. Including how we're tieing to MozFest. How do we give MP a start and finish, while also saying "it goes all year!" erikad will ticket
      • Themes. Discuss and document potential themes for this year
      • Build a comms calendar for Maker Party. Including comms channels needed. How long the campaign will run.erikad will ticket
      • Roles. Document roles and responsibilities: who will own what?
    • Partners
    • Engagement Metrics
      • What will we measure? How? Co-ordinate with Metrics and Engagement Ladder track

OTHER TO DO's:

  • Update event guides. Figure out where they should live going forward. And how they should be packaged. https://bugzilla.mozilla.org/show_bug.cgi?id=957989
  • Create tutorial for first time event throwers. Lists of best practices and where to find info
  • Method to recruit and engage event partners. Create a way to engage with partners and outline expectation before and leading up to events (MP)
  • Tutorial (guide) for post-event strategy. "Now that your event has happened, here's what you need to know next"
  • Event report backs. Create a standardized system for event hosts to report back on their event

Workshops & Roundatables

Co-Design and User Testing with communities

  • bugzilla whiteboard: workweek-codesign
  • Shipping a shared understanding about what methods to use for user testing/co-design, and how to get the community involved in this process across teams/regional areas.
  • owner: Karen

Schedule it Wednesday aft.


Arrival Times + Evening Plans

Plus arrival times: https://fdn.etherpad.mozilla.org/feb2014workweek

Goal

Not too look like this at end of week:


26_7ipg6.png

Retrieved from "https://wiki.allizom.org/index.php?title=Webmaker/Workweek&oldid=911451"