Webmaker/Workweek: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(48 intermediate revisions by 9 users not shown)
Line 1: Line 1:
[[Image:catsworking.gif|right]]
[[Image:catsworking.gif|right]]
* '''Feb 3-7, Toronto'''
* Pocket agenda: http://cl.ly/TdCX
* Bugzilla whiteboard tag: '''[workweek]'''


''' [[https://wiki.mozilla.org/Webmaker/Workweek/giffree Gif free edition]] '''
== Who came? ==
 
link to scrum specific etherpads
 
 
== Who's coming? ==
https://wmprofile-service-production.s3.amazonaws.com/gifs/vXRPSmwqaECZBcqcTaU1bRih.gif https://webmaker.etherpad.mozilla.org/feb2014workweekattending  
https://wmprofile-service-production.s3.amazonaws.com/gifs/vXRPSmwqaECZBcqcTaU1bRih.gif https://webmaker.etherpad.mozilla.org/feb2014workweekattending  


= What we're shipping =
= What we worked on =


[[Image:jpbuck240.gif|right]]
[[Image:jpbuck240.gif|right]]
Line 31: Line 23:


[[Image:progress.gif|left]]
[[Image:progress.gif|left]]
= Progress so far =
= Progress =
Check the [[https://wiki.mozilla.org/Webmaker/Scrumboard Scrumboard!]]
Check the [[https://wiki.mozilla.org/Webmaker/Scrumboard Scrumboard!]]


= Scrums =
= 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.
[[Image:chopwood.jpg|300px|right]]
[[Image:chopwood.jpg|300px|right]]


Line 72: Line 62:
<bugzilla>
<bugzilla>
{
{
"status":"NEW",
"product": "webmaker",
"product": "webmaker",
"whiteboard":"[workweek-weblitux]",
"whiteboard":"[workweek-weblitux]",
Line 82: Line 71:
</onlyinclude>
</onlyinclude>


== [https://etherpad.mozilla.org/WebLitcontent Web Literacy Content] ==
== [https://etherpad.mozilla.org/WebLitcontent Web Literacy Content] (a.k.a. #TeachTheWeb) ==
[[Image:teachtheweb-doge.jpg|300px|right]]
* [https://dajbelshaw.makes.org/thimble/teachtheweb-team-report-out-webmker-workeek-feb-2014 Thimble report out]
* https://etherpad.mozilla.org/WebLitcontent
* https://etherpad.mozilla.org/WebLitcontent
* '''[workweek] [content]'''
* '''[workweek] [content]'''
Line 97: Line 88:


PREP WORK
PREP WORK
* '''Build a Webmaker Curriculum Glossary''' https://bugzilla.mozilla.org/show_bug.cgi?id=965295
SHIPPED
* [https://wiki.mozilla.org/File:TTW_Basic_Wireframes.png '''Platform concepting''' on the wiki]
* [http://i.imgur.com/cQw8Lr1.png '''Platform schematic''']
* '''Gather best Web Literacy curriculum''' in a spreadsheet: https://bugzilla.mozilla.org/show_bug.cgi?id=964277
* '''Gather best Web Literacy curriculum''' in a spreadsheet: https://bugzilla.mozilla.org/show_bug.cgi?id=964277
* '''Build a Webmaker Curriculum Glossary''' https://bugzilla.mozilla.org/show_bug.cgi?id=965295
 


<onlyinclude>
<onlyinclude>
<bugzilla>
<bugzilla>
{
{
"status":"NEW",
"product": "webmaker",
"product": "webmaker",
"whiteboard":"[workweek-content]",
"whiteboard":"[workweek-content]",
Line 115: Line 110:
[[Image:ladder.gif|right]]
[[Image:ladder.gif|right]]


== Webmaker engagement ladder ==
== Engagement Ladder ==
 
* Notes: https://etherpad.mozilla.org/Engagement-Ladder
 
* Wiki: https://wiki.mozilla.org/Webmaker/Get_Involved
 
* bugzilla whiteboard: [workweek][ [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=whiteboard%3A%5Bworkweek-engagement%5D workweek-engagement] ]
* https://wiki.mozilla.org/Webmaker/Get_Involved
* 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.
Line 150: Line 142:
<bugzilla>
<bugzilla>
{
{
"status":"NEW",
"product": "webmaker",
"product": "webmaker",
"whiteboard":"[workweek-engagement]",
"whiteboard":"[workweek-engagement]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</onlyinclude>
== Maker Party  ==
'''Develop the framework and planning for the 2014 MP campaign.'''
* https://teach.etherpad.mozilla.org/2014workweekEVENTS or https://teach.etherpad.mozilla.org/MakerParty2014
* When: '''Wednesday - Friday'''
* Owner: '''Amira'''
Whiteboard tag: '''[workweek-makerparty]'''
'''Scrum tasks: '''
* Document our plan for Maker Party 2014
**  Comms tasks: https://bugzilla.mozilla.org/show_bug.cgi?id=966356
*** 1) Timeline (start/stop dates)
*** 2) Partners/events -- see [https://bugzilla.mozilla.org/show_bug.cgi?id=966313 Bug 966313]
*** 3) Messaging and language
*** 4) Brand and visual assets (digital and physical)
*** 5) Landing page (who builds it, establish scope)
*** 6) Organizing kits & volunteer flow
*** 7) Press and PR strategy
** Update webmaker.org/party including creating the layout and format for the new page: https://bugzilla.mozilla.org/show_bug.cgi?id=966338
** Partners
***  Document our plan for on-boarding and working with partners. I think we do still need something specific for Maker Party: https://bugzilla.mozilla.org/show_bug.cgi?id=966313
*** Ship partner documentation: https://bugzilla.mozilla.org/show_bug.cgi?id=965288
**Engagement Metrics
*** What will we measure? How? Co-ordinate with Metrics and Engagement Ladder track: https://bugzilla.mozilla.org/show_bug.cgi?id=966317
'''Other TODOs:'''
* 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: https://bugzilla.mozilla.org/show_bug.cgi?id=966321
* Method to recruit and engage event partners. Create a way to engage with partners and outline expectation before and leading up to events: https://bugzilla.mozilla.org/show_bug.cgi?id=966313
* Tutorial (guide) for post-event strategy. "Now that your event has happened, here's what you need to know next": https://bugzilla.mozilla.org/show_bug.cgi?id=966327
* Event report backs. Create a standardized system for event hosts to report back on their event: https://bugzilla.mozilla.org/show_bug.cgi?id=966330
<onlyinclude>
<bugzilla>
{
"product": "webmaker",
"whiteboard":"[workweek-makerparty]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"maxrows":"50",
Line 161: Line 196:


== Metrics  ==
== Metrics  ==
=== YOUR INPUT NEEDED ===
==== PLACE YOUR BETS HERE ====
* [https://docs.google.com/a/mozillafoundation.org/forms/d/1anaNEOFxRyUCNMqxb0isIEexYf59DLgEkKYy43jUbDA/viewform Place your bets on our first A/B test]
==== Share your test ideas here ====
* https://etherpad.mozilla.org/webmaker-ideas-for-things-to-test
[[Image:metrics.gif|right]]
[[Image:metrics.gif|right]]
Bugzilla whiteboard: [workweek][workweek-metrics]
* Bugzilla whiteboard: '''[workweek][workweek-metrics]'''
* ''' Owner: Adam '''
* '''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.


* When:   
* When:   
Line 170: Line 214:
** '''Thurs:''' Web Literacy Metrics
** '''Thurs:''' Web Literacy Metrics


'''Goal:'''
''' Scrum tasks '''<br>
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 '''<br>
''' Scrum tasks '''


'''A/B Testing and Optimisation'''<br>
'''A/B Testing and Optimisation'''<br>
Line 229: Line 269:
<bugzilla>
<bugzilla>
{
{
"status":"NEW",
"product": "webmaker",
"product": "webmaker",
"whiteboard":"[workweek-metrics]",
"whiteboard":"[workweek-metrics]",
Line 241: Line 280:
== DevOps:  making  code contributions easier ==
== DevOps:  making  code contributions easier ==
* bugzilla whiteboard: '''[workweek][workweek-devops]'''
* 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.
* 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.
* Owner: JP


 
* '''Scrum tasks'''
* Owner: JP
** Priority 1: Examine http://www.elasticsearch.org/overview/ as a possible graylog replacement, or upgrade to newest preview version of graylog (Currently demo version up)
** Priority 1: Examine http://www.elasticsearch.org/overview/ as a possible graylog replacement, or upgrade to newest preview version of graylog (Currently demo version up)
** 2: Configuration management goes inside repos https://bugzilla.mozilla.org/show_bug.cgi?id=964779
** 2: Configuration management goes inside repos https://bugzilla.mozilla.org/show_bug.cgi?id=964779
Line 267: Line 306:
<bugzilla>
<bugzilla>
{
{
"status":"NEW",
"product": "webmaker",
"product": "webmaker",
"whiteboard":"[workweek-devops]",
"whiteboard":"[workweek-devops]",
Line 278: Line 316:


== Third-party publishing to Webmaker ==
== Third-party publishing to Webmaker ==
* bugzilla whiteboard: [workweek] [workweek-3rdparty] [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=whiteboard%3Aworkweek-3rdparty search]
* '''Improving our platform systems (MakeAPI, Login) so that 3rd party apps can publish to webmaker'''.
* Owners: '''ChrisD, Wex'''


* use bugzilla whiteboard: [workweek] [workweek-3rdparty] [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=whiteboard%3Aworkweek-3rdparty search]
* Scrum Tasks:
'''Improving our platform systems (MakeAPI, Login) so that 3rd party apps can publish to webmaker'''.
 
* Owners: '''ChrisD, Wex'''
* Tasks:
** '''Appmaker can publish to MakeAPI-Prod''' https://bugzilla.mozilla.org/show_bug.cgi?id=965932
** '''Appmaker can publish to MakeAPI-Prod''' https://bugzilla.mozilla.org/show_bug.cgi?id=965932
** '''Appmaker users can log in with their Webmaker ID''' https://bugzilla.mozilla.org/show_bug.cgi?id=965941
** '''Appmaker users can log in with their Webmaker ID''' https://bugzilla.mozilla.org/show_bug.cgi?id=965941
Line 292: Line 329:
<bugzilla>
<bugzilla>
{
{
"status":"NEW",
"product": "webmaker",
"product": "webmaker",
"whiteboard":"[workweek-3rdparty]",
"whiteboard":"[workweek-3rdparty]",
Line 305: Line 341:
[[Image:translation.gif|right]]
[[Image:translation.gif|right]]
'''Goals'''
'''Goals'''
* Understand which new markets, languages, locales are our priority in the short and medium term. Gain wisdom from our Mozilla Japan colleagues.
* '''Understand which new markets, languages, locales are our priority in the short and medium term. Gain wisdom from our Mozilla Japan colleagues'''.
* Plan and process for evaluating the quality of our localized sites. User testing with l10n focus.
* Plan and process for evaluating the quality of our localized sites. User testing with l10n focus.
* Plan, technical strategy and prototype for right-to-left (RTL) locales.   
* Plan, technical strategy and prototype for right-to-left (RTL) locales.   
Line 313: Line 349:
* '''Owners:''' Humph, Ali
* '''Owners:''' Humph, Ali
* '''Scrum tasks'''
* '''Scrum tasks'''
** Right-to-Left (RTL Planning '''(Tues AM)''' https://bugzilla.mozilla.org/show_bug.cgi?id=965406   
** Right-to-Left Planning -- '''(Tues AM)''' https://bugzilla.mozilla.org/show_bug.cgi?id=965406   
** Prioritize Languages/Locales https://bugzilla.mozilla.org/show_bug.cgi?id=965412
** Prioritize Languages/Locales https://bugzilla.mozilla.org/show_bug.cgi?id=965412
** Webmaker and Japan https://bugzilla.mozilla.org/show_bug.cgi?id=965416
** Webmaker and Japan https://bugzilla.mozilla.org/show_bug.cgi?id=965416
** Localization User Testing https://bugzilla.mozilla.org/show_bug.cgi?id=965417
** Localization User Testing 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?
** '''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):'''
*  '''Post Work Week Priorities (individual tasks that could be done or put off):'''
Line 336: Line 372:
<bugzilla>
<bugzilla>
{
{
"status":"NEW",
"product": "webmaker",
"product": "webmaker",
"whiteboard":"[workweek-l10n]",
"whiteboard":"[workweek-l10n]",
Line 346: Line 381:
</onlyinclude>
</onlyinclude>


== Maker Party  ==
== New markets ==
Develop the framework and planning for the 2014 MP campaign.
* https://webmaker.etherpad.mozilla.org/feb2014workweekNewMarkets
* https://teach.etherpad.mozilla.org/2014workweekEVENTS
* https://wiki.mozilla.org/Webmaker/Markets
* When: Wednesday - Friday
* What are they and how will we win?
* Owner: Amira
* Wrangler: Paula
* When: Tues and Wed
* Bugzilla whiteboard: '''[workweek-newmarkets]'''


'''Scrum tasks:'''
* List geographic priorities for 2014. Where are we focusing?
* Documentation for our Brazil Strategy, Mid East Strategy, etc
* Documentation for "Rules of engagement" for these new markets.
** '''Ship all of the above in polished, canonical form to the Webmaker wiki here''': https://wiki.mozilla.org/Webmaker/Markets https://bugzilla.mozilla.org/show_bug.cgi?id=965480
<onlyinclude>
<bugzilla>
{
"product": "webmaker",
"whiteboard":"[workweek-newmarkets]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</onlyinclude>


'''Scrum tasks: '''
= Workshops & Roundatables =
* Document our plan for Maker Party 2014
Fixed sessions that don't span entire week
**  Comms tasks: https://bugzilla.mozilla.org/show_bug.cgi?id=966356
*** 1) Timeline (start/stop dates)
*** 2) Partners/events -- see Bug 966313
*** 3) Messaging and language
*** 4) Brand and visual assets (digital and physical)
*** 5) Landing page (who builds it, establish scope)
*** 6) Organizing kits & volunteer flow
*** 7) Press and PR strategy
** Update webmaker.org/party including creating the layout and format for the new page: https://bugzilla.mozilla.org/show_bug.cgi?id=966338
** Partners
***  Document our plan for on-boarding and working with partners. I think we do still need something specific for Maker Party: https://bugzilla.mozilla.org/show_bug.cgi?id=966313
*** Ship partner documentation: https://bugzilla.mozilla.org/show_bug.cgi?id=965288
**Engagement Metrics
*** What will we measure? How? Co-ordinate with Metrics and Engagement Ladder track: https://bugzilla.mozilla.org/show_bug.cgi?id=966317


OTHER TO DO's:
== Co-Design and User Testing ==
* 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
* https://etherpad.mozilla.org/User-Testing
* Create tutorial for first time event throwers. Lists of best practices and where to find info: https://bugzilla.mozilla.org/show_bug.cgi?id=966321
* bugzilla whiteboard: [workweek-codesign]
* Method to recruit and engage event partners. Create a way to engage with partners and outline expectation before and leading up to events: https://bugzilla.mozilla.org/show_bug.cgi?id=966313
* Methods for user testing/co-design. Ship user testing kits for Webmaker and Appmaker.
* Tutorial (guide) for post-event strategy. "Now that your event has happened, here's what you need to know next": https://bugzilla.mozilla.org/show_bug.cgi?id=966327
* Kat / Karen (note: Karen is off-site Tues morning)
* Event report backs. Create a standardized system for event hosts to report back on their event: https://bugzilla.mozilla.org/show_bug.cgi?id=966330


= Workshops & Roundatables =
'''SCRUM TASKS:'''
Fixed sessions that don't span entire week
* Ship Webmaker and Appmaker Community Testing kits for others to run.
** Appmaker https://bugzilla.mozilla.org/show_bug.cgi?id=959727
** Webmaker https://bugzilla.mozilla.org/show_bug.cgi?id=959389
* Run our first Webmaker or Appmaker test in UserTesting.com  https://bugzilla.mozilla.org/show_bug.cgi?id=965487


== Co-Design and User Testing with communities ==
* Ship plans for a cross MoFo-MoCo UX/User Testing summit in Spring https://bugzilla.mozilla.org/show_bug.cgi?id=965545
* 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
* Work with Localisation to determine how to localise user tests/kits effectively. https://bugzilla.mozilla.org/show_bug.cgi?id=965417


Thursday afternoon.
* User testing session FOR our localization. e.g., have Brazillians tell us if our localization is good. https://bugzilla.mozilla.org/show_bug.cgi?id=965417


* TASKS:
'''ADVANCE READING:'''
** Priority 1: Ship Webmaker and Appmaker Community Testing kits for others to run.
* Building better user testing for Webmaker https://blog.webmaker.org/user_testing
*** Initial plans for Appmaker https://bugzilla.mozilla.org/show_bug.cgi?id=959727
* Appmaker User Testing Plan  http://mzl.la/appmaker_codesign
*** Webmaker https://bugzilla.mozilla.org/show_bug.cgi?id=959389
* Example of Codesign workshop for Telefonica Think Big: https://webmaker.etherpad.mozilla.org/codesign
*** Related: https://etherpad.mozilla.org/User-Testing and https://bugzilla.mozilla.org/show_bug.cgi?id=965487
* Suggested: http://alistapart.com/article/seeing-the-elephant-defragmenting-user-research
** Priority 2: Ship plans for a cross MoFo-MoCo UX/User Testing summit in Spring, to discuss shared data/results.
* Suggested: http://alistapart.com/article/connected-ux
*** Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=965545
*** Related: Read through https://etherpad.mozilla.org/User-Testing esp. line 22: "What are our Main goals?"
** Priority 3, with Localisation guys: Determine how to localise user tests/kits effectively.
*** Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=965417
** I'd also suggest a user testing session FOR our localization, ie, have brazillian people tell us if the localization is any good! (BG)


* ADVANCE READING:
<onlyinclude>
** Building better user testing for Webmaker https://blog.webmaker.org/user_testing
<bugzilla>
** Appmaker User Testing Plan  http://mzl.la/appmaker_codesign
{
** Example of Codesign workshop for Telefonica Think Big: https://webmaker.etherpad.mozilla.org/codesign
"product": "webmaker",
** Suggested: http://alistapart.com/article/seeing-the-elephant-defragmenting-user-research
"whiteboard":"[workweek-codesign]",
** Suggested: http://alistapart.com/article/connected-ux
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</onlyinclude>


== Makerstrap workstop ==
== Makerstrap workstop ==
Line 430: Line 469:
https://pbs.twimg.com/media/BXlVaKBCMAEF6wN.jpg
https://pbs.twimg.com/media/BXlVaKBCMAEF6wN.jpg
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/26_7ipg6.png
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/26_7ipg6.png
-----
[[File:Jp-axe.gif]]

Latest revision as of 12:44, 17 February 2014

Catsworking.gif

Who came?

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

What we worked on

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

Check the [Scrumboard!]

Scrums

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? The objective of this task is to gather all the information / pieces we'll need to be looking at in order to design the "Explore" section.

2) Brainstorm

3) Prototype

4) Refine

Bugzilla query error

Bugzilla API returned an error: 1


Web Literacy Content (a.k.a. #TeachTheWeb)

Teachtheweb-doge.jpg
  • Thimble report out
  • 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.
  • Owners Kat/Doug

TASKS

PREP WORK

SHIPPED


No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


Ladder.gif

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


Bugzilla query error

Bugzilla API returned an error: 1


Maker Party

Develop the framework and planning for the 2014 MP campaign.

Whiteboard tag: [workweek-makerparty]

Scrum tasks:

Other TODOs:


No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


Metrics

YOUR INPUT NEEDED

PLACE YOUR BETS HERE

Share your test ideas here

Metrics.gif
  • Bugzilla whiteboard: [workweek][workweek-metrics]
  • Owner: Adam
  • 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.
  • When:
    • Mon: Testing and Optimisation
    • Tues: Webmaker Dashboard
    • Weds morning: Google Analytics for Developers. Weds aft: Google Analytics for Noobs.
    • Thurs: Web Literacy Metrics

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

Prep work

Requested Reading


No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


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.
  • Owner: JP


No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


Third-party publishing to Webmaker

  • bugzilla whiteboard: [workweek] [workweek-3rdparty] search
  • Improving our platform systems (MakeAPI, Login) so that 3rd party apps can publish to webmaker.
  • Owners: ChrisD, Wex


No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


Localization

Translation.gif

Goals

  • Understand which new markets, languages, locales are our priority in the short and medium term. Gain wisdom from our Mozilla Japan colleagues.
  • Plan and process for evaluating the quality of our localized sites. User testing with l10n focus.
  • Plan, technical strategy and prototype for right-to-left (RTL) locales.
  • Bugzilla whiteboard: [workweek-l10n]
  • 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/)


No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


New markets

Scrum tasks:

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


Workshops & Roundatables

Fixed sessions that don't span entire week

Co-Design and User Testing

  • https://etherpad.mozilla.org/User-Testing
  • bugzilla whiteboard: [workweek-codesign]
  • Methods for user testing/co-design. Ship user testing kits for Webmaker and Appmaker.
  • Kat / Karen (note: Karen is off-site Tues morning)

SCRUM TASKS:

ADVANCE READING:


No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


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.

BXlVaKBCMAEF6wN.jpg 26_7ipg6.png

Jp-axe.gif

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