Webmaker/Workweek: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 113: Line 113:
* '''4) Optimize our use of email.''' https://bugzilla.mozilla.org/show_bug.cgi?id=966288
* '''4) Optimize our use of email.''' https://bugzilla.mozilla.org/show_bug.cgi?id=966288
* '''5) Simplify and optimize communications channels.''' Simplify, combine and operationalize social and other channels  https://bugzilla.mozilla.org/show_bug.cgi?id=965473
* '''5) Simplify and optimize communications channels.''' Simplify, combine and operationalize social and other channels  https://bugzilla.mozilla.org/show_bug.cgi?id=965473
** Document our plan for Webmaker mentors badges https://bugzilla.mozilla.org/show_bug.cgi?id=966289
** Establish Baseline contributor #s from last year. Publish them on the Webmaker wiki. https://bugzilla.mozilla.org/show_bug.cgi?id=966290
** 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


* '''Stretch goal'''
'''Stretch goals'''
** Move postal service from integrated into each app into a separate service that feeds from the makermind
* Document our plan for Webmaker mentors badges https://bugzilla.mozilla.org/show_bug.cgi?id=966289
* Establish Baseline contributor #s from last year. Publish them on the Webmaker wiki. https://bugzilla.mozilla.org/show_bug.cgi?id=966290
* Create an engagement timeline that will attract and onboard new contributors https://bugzilla.mozilla.org/show_bug.cgi?id=966329
* Create prospect lists for engagement outreach. https://bugzilla.mozilla.org/show_bug.cgi?id=966331
* Document Webmaker's "1M Mozillians plan". https://bugzilla.mozilla.org/show_bug.cgi?id=966333
* Move postal service from integrated into each app into a separate service https://bugzilla.mozilla.org/show_bug.cgi?id=966336


== METRICS  ==
== METRICS  ==

Revision as of 17:35, 31 January 2014

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

[Gif free edition]

link to scrum specific etherpads


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.
Progress.gif

Progress so far

Check the [Scrumboard!]


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.

Chopwood.jpg

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


Ladder.gif

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

Stretch goals

METRICS

Metrics.gif

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

A/B Testing and Optimisation
PAD: https://etherpad.mozilla.org/webmaker-workweek-metrics-testing


Webmaker Dashboard
PAD: https://etherpad.mozilla.org/webmaker-workweek-metrics-dashboard

Google Analytics
PAD: https://etherpad.mozilla.org/webmaker-workweek-metrics-ga

Literacy Metrics
PAD: https://etherpad.mozilla.org/webmaker-workweek-metrics-literacy

Open Discussions:
PAD: https://etherpad.mozilla.org/webmaker-workweek-metrics-open-discussions

  • 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

Translation.gif

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

OTHER TO DO's:

Workshops & Roundatables

Fixed sessions that don't span entire week

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

Thursday afternoon.

Makerstrap workstop

Learn the basics of using Makerstrap to creating basic pages that align with the living styleguide, using Thimble or your own tools. Owner: Kate

How to Install and Develop Webmaker.org

Pomax shows folks who have not yet committed code to Webmaker how to do that

Front End Roundtable

Webmaker crew + Engagement / Service shop crew share knowledge Session on frontend best practices across MoFo that should include Cassie, Gavin, Kate, Mavis, Sabrina, and possibly Atul, & other interested folks. Space for us to get together to share resources and tackle hurdles would help cement a kickass frontend/UX culture. Will include a report out that shares our process and how others can get frontend stuff accomplished quickly and effectively (e.g., setting up a website, design, code review, etc).

Webmaker in Firefox - exploring browser extensions

Humph, Cassie + Gavin have been working on a skunkworks project to bring Webmaker into your browser. They'll show us how they're doing


Arrival Times + Evening Plans

https://fdn.etherpad.mozilla.org/feb2014workweek

Goal

Leave it all on the field. 120% percent.


26_7ipg6.png

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