MozillaWiki - User contributions [en]

WeeklyUpdates/2016-06-27

2016-06-27T17:36:32Z

Brett Gaylor: Added link to slides

{{WeeklyUpdateNav}}
* Every Monday @ 11:00am Pacific Time (19:00 UTC)
* http://air.mozilla.org/ to watch and listen
* join irc.mozilla.org #airmozilla for backchannel discussion
* Presenters only: Vidyo room "Brownbags". Do '''not''' use this room if you're not planning to speak.
{{conf|8600}}
** If you plan on presenting, please join the Vidyo BrownBags 20 minutes prior to the start of the meeting and announce to the A/V Technicians that you will be speaking so that they can confirm your Audio and Video.

__TOC__

= All-hands Status Meeting Agenda =

Items in this section will be shared during the live all-hand status meeting.

== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==
* All the 106 volunteers that attended All Hands from 32 different countries from all over the globe!
* Firefox Dev Tools code contributor and new Mozilla Hacks author Jarda Snajdr, who wrote [https://hacks.mozilla.org/2016/06/developer-edition-49-network-request-stack-traces-and-more/ Developer Edition 49: Network Request Stack Traces and more] earlier this month, while many of us were in transit.
*Big thanks to [https://blog.mozilla.org/addons/2016/06/22/friend-of-add-ons-yuki-hiroshi/ Yuki Hiroshi, aka Piro (pronounced "Peer-oh")], who is our newest Friend of Add-ons! Piro is a longtime add-on developer who is helping his fellow developers through the transition to WebExtensions.

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===
* [https://quality.mozilla.org/event/bug-triage-day-116/ Weekly Bug Triage Day]

=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===

=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===
* [https://quality.mozilla.org/event/bug-verification-day-123/ Weekly Bug Verification Day]

* '''[https://indiewebcamp.com/events/2016-06-29-homebrew-website-club Homebrew Website Club Meetup]''' (every other Wednesday — fortnightly) Be a part of the open web with your own website.
** '''Brighton ENGLAND''', '''Göteborg SWEDEN''', '''Portland''' (OR), '''San Francisco''' (at [[SF|MozSF 1st floor]], host: [[Tantek Çelik]]), and '''Bellingham''' (WA)
** 17:30-18:30 Quiet Writing Hour, finish that blog post, wiki edit, etc.!
** 18:30-19:30 IndieWeb meetup, demos, & hack night <blockquote>Create or update your personal web site! Share what you've gotten working, ask the experts questions.Join a community with like-minded interests. Bring friends that want a personal site!</blockquote> Any questions? See '''[https://indiewebcamp.com/events/2016-06-29-homebrew-website-club the wiki page for details]''' or join IRC: http://indiewebcamp.com/irc/today?beta#bottom

=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===

=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===

=== Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===

=== Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===

=== Next Week ===

== Speakers ==

The limit is '''3 minutes per topic'''. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week. The meeting is streamed in a 4:3 format in order to allow for split screen. If your slides are 16:9 "widescreen" format, please indicate in the "Sharing" column below.

{| class="fullwidth-table wikitable"
|-
! [https://mozillians.org/u/USERNAME Presenter]
! Title
! Topic
! Location
! Sharing
! Media
! More Details
|-
| Brett Gaylor / Jordan Gushwa
| Mozilla Advocacy
| Codemoji! Mozilla's new browser-based educational game for teaching the basics of encryption. Send messages encoded in emoji.
| Remotely and Portland
| Yes
| [https://docs.google.com/presentation/d/1bhTHN2I59GaCpJOrGk4SBsnYXm2PYPZw-8ARAUobhPo/edit?ts=577160c9#slide=id.g150c7d43a1_0_11 slides here]
| [http://learning.mozilla.org/codemoji learning.mozilla.org/codemoji]
|-
| Maura Tuohy
| Mozilla Open Mic - Social Team
| #TheArtofCoding: social campaign to bring awareness to digital literacy *and* to teach simple lines of code in a visual way
| SF Office
| Yes
| [https://docs.google.com/a/mozilla.com/presentation/d/10ynQGBjc1EQ8xDYux5a0uVGqN9OabS8Lio5UbAYXS_U/edit?usp=sharing slides here]
|
|-
| Erik Rose
| Machine Learning Team
| A DXR update
| Remote
| No
|
| https://dxr.mozilla.org/
|
|-
|Janis Greenspan / Tim Murray
| Mozilla Brand Team
| Mozilla Open Design update
| San Francisco
| No
| https://docs.google.com/a/mozilla.com/presentation/d/1_E-7SJQ6Pao32uMc9cu_lJ4pZXWHlkLymgJCHfiFfwc/edit?usp=sharing
| video
| https://blog.mozilla.org/opendesign
|-
| Asa Dotzler
| Firefox Roadmap
| Firefox Update
| MTV
| No
|
|
|-
|}

= Welcome! =

Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.

== Introducing New Volunteers ==
{| class="fullwidth-table wikitable"
|-
! [https://mozillians.org/u/USERNAME New Volunteer]
! [https://mozillians.org/u/USERNAME Introduced by]
! Speaker location
! New Volunteer location
! Will be working on
|-
| ''Who is the new volunteer?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be contributing from?''
| ''What will the new person be working on?''
|-

|-
|}

== Introducing New Hires ==
{| class="fullwidth-table wikitable"
|-
! New Hire
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new hire?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-

|-
| Brandon Myers [:pwnbus]
| Jeff Bryner
| Portland
| Chicago/Remote
| MozDef: The Mozilla Defense Platform
|-
|-
| Tristan Weir [:weir]
| Jeff Bryner
| Portland
| Wash D.C./Remote
| Security Program Manager
|-
|-
| Michele Warther
| Chad Weiner
| SFO
| Portland
| Lifecycle Marketing
|-
|}

== Introducing New Interns ==
{| class="fullwidth-table wikitable"
|-
! New Intern
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new intern?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-

|-
| Miko Mynttinen
| Jet Villegas
| SF
| SF
| Platform Rendering
|-
| Anthony Miyaguchi
| Jordan Lund
| YVR
| SF
| Release Engineering
|-
|}

= <meta> =

Notes and non-voice status updates that aren't part of the live meeting go here.

== Status Updates By Team (*non-voice* updates) ==

=== Firefox ===

=== Platform ===

=== Messaging ===

=== Mobile ===

=== IT ===

=== Connected Devices ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== Web QA ====

==== QA Community ====

=== Engineering Productivity (Automation & Tools) ===

=== Security ===

==== Developer Relations ====

* We've opened the application process for Mozilla Tech Speakers Program Phase 2 - summer pilot - (A 10 week series of MasterClasses & Labs) :
** an initiative for Mozillians who are already out in their communities speaking with developers, designers and web builders, and who want to work on developing skills and confidence as technical presenters and evangelists in local developer communities.
**[http://bit.ly/mts2-apply Apply here]
** More details: https://discourse.mozilla-community.org/t/tech-speakers-phase-2-pilot-opening-now/9399

=== Engagement ===

* [https://docs.google.com/a/mozilla.com/spreadsheets/d/1X5kUBkEAicEe2unDaaLGTYzAJbphWFoaJYBTasHrcHQ/edit#gid=1764494528 Engagement's Active Project Dashboard]

==== PR ====

==== Events ====

==== Social Support ====

[[Category:Weekly Updates]]
[[Category:Meeting Notes]]

Netpolicy/advocacy/openwebfellows

2015-10-02T13:27:34Z

Brett Gaylor: /* Gem Barrett, Open Technology Institute */

The [https://advocacy.mozilla.org/open-web-fellows/ '''Ford-Mozilla Open Web Fellows Program'''] — a collaboration between the Ford Foundation and Mozilla — is an international leadership initiative that brings together the best emerging technology talent and civil society organizations to protect the open Web. The program fills a critical niche: it provides an ecosystem for the next generation of open Web advocates to make an early impact. As threats to digital freedom proliferate, it’s critical to have capable leaders.

Each year, Fellows spend 10 months embedded at leading advocacy organizations to safeguard the Internet as a global public resource. The 2015 host organizations are:
* American Civil Liberties Union, Massachusetts
* Amnesty International
* Association for Progressive Communications
* Free Press
* Open Technology Institute
* Public Knowledge

= [https://advocacy.mozilla.org/open-web-fellows/ 2015 Fellows]=
==Paola Villarreal, American Civil Liberties Union, Massachusetts==
Data for Justice is a data-driven advocacy tool that visualizes information critical for eliminating injustice in communities.

Read more on the project's Knight News Challenge application
https://www.newschallenge.org/challenge/data/entries/the-data-for-justice-project

==Tim Sammut, Amnesty International==
[https://teamsammut.com Website], [https://twitter.com/t1msammut @t1msammut], [https://teamsammut.com/pages/contact.html Contact Info]

===Fellowship projects===

* '''Secure Communications Framework''': An approachable framework for human rights researchers that helps them understand how to communicate with contacts around the world safely in the context of varying threats and information sensitivity.
* '''Community Incident Response''': Help human rights organizations in Amnesty's worldwide network access technical assistance during active digital attacks.

===Personal projects===

* ThunderSec: DKIM, SPF, DNSBL plug-in for Mozilla Thunderbird, [https://addons.mozilla.org/en-US/thunderbird/addon/thundersec/ addons.mozilla.org], [https://github.com/itemir/thundersec GitHub]
* [https://atlas.torproject.org/#search/teamsammut Operate Tor Nodes]
* [https://teamsammut.com/blog/2015/09/apple-macbook-pro-linux-issue-tracking.html Making Linux on the Macbook Pro Retina Less Terrible]

===Things created===

* 1 October 2015, Blog post, '''[https://teamsammut.com/blog/2015/10/three-steps-against-mass-surveillance.html Three Steps Against Mass Surveillance, For Other People ]'''
* 20 September 2015, Blog post, '''[https://teamsammut.com/blog/2015/09/human-rights-education-threat-modeling.html Human Rights Education Threat Modeling]'''
* 12 September 2015, Conference proposal, '''[https://teamsammut.com/blog/2015/09/mozfest-promoting-freedom-of-expression-with-tor.html Promoting Freedom of Expression with Tor]'''
* 14 August 2015, Blog post, '''[https://teamsammut.com/blog/2015/08/tor-hidden-service-for-teamsammut.com.html Tor Hidden Service for teamsammut.com ]'''
* 11 August 2015, Slides, '''Tor vs. VPNs and Proxies''', [https://teamsammut.com/files/presentations/Proxies%20VPNs%20and%20Tor%20v20150715c.pdf PDF], [https://teamsammut.com/files/presentations/Proxies%20VPNs%20and%20Tor%20v20150715c.odp ODF]
* 23 July 2015, Blog post, '''[https://teamsammut.com/blog/2015/07/the-rights-enabling-internet-wont-continue-by-accident.html The Internet that enables human rights won't continue by accident ]'''
* 23 July 2015, Blog post, '''[https://teamsammut.com/blog/2015/06/what-is-the-open-web.html What is the Open Web? ]'''
==Andrea Del Rio, Association for Progressive Communications==
Many of the bad things that happen offline are also true online: for example violence against women, discrimination against LGBT people, hate crimes, inequality of access to basic services or censorship. The project I am working on right now called The Feminist Principles of the Internet aims to inspire people not only to imagine a Feminist Internet but actually build one that is fair, inclusive, empowering and safe for everyone.

Month two blog post:
https://medium.com/@andreadelrio/ford-mozilla-open-web-fellowship-apc-month-2-65aab25f9402

==Drew Wilson, Free Press==
Drew is embedded in Free Press' Internet2016 campaign and is building tools that internet rights advocates can use to bootstrap their own activism projects.

https://internet2016.net/

==Gem Barrett, Open Technology Institute==
Gem is a member of the MLab team at OTI, helping to build the largest collection of open Internet performance data on the planet.

http://www.measurementlab.net/

==Tennyson Holloway, Public Knowledge==
Tennyson is working on projects that inspire and educate future web advocates. "What can i do for the internet.org" is a website that represents a vision of a story based platform that educates, inspires, and assists users to join the open web movement. His other projects involve creating web games that explain tech policy Washington issues, such as copyright and patent trolls.

Netpolicy/advocacy/openwebfellows

2015-10-02T13:25:36Z

Brett Gaylor: /* Drew Wilson, Free Press */

The [https://advocacy.mozilla.org/open-web-fellows/ '''Ford-Mozilla Open Web Fellows Program'''] — a collaboration between the Ford Foundation and Mozilla — is an international leadership initiative that brings together the best emerging technology talent and civil society organizations to protect the open Web. The program fills a critical niche: it provides an ecosystem for the next generation of open Web advocates to make an early impact. As threats to digital freedom proliferate, it’s critical to have capable leaders.

Each year, Fellows spend 10 months embedded at leading advocacy organizations to safeguard the Internet as a global public resource. The 2015 host organizations are:
* American Civil Liberties Union, Massachusetts
* Amnesty International
* Association for Progressive Communications
* Free Press
* Open Technology Institute
* Public Knowledge

= [https://advocacy.mozilla.org/open-web-fellows/ 2015 Fellows]=
==Paola Villarreal, American Civil Liberties Union, Massachusetts==
Data for Justice is a data-driven advocacy tool that visualizes information critical for eliminating injustice in communities.

Read more on the project's Knight News Challenge application
https://www.newschallenge.org/challenge/data/entries/the-data-for-justice-project

==Tim Sammut, Amnesty International==
[https://teamsammut.com Website], [https://twitter.com/t1msammut @t1msammut], [https://teamsammut.com/pages/contact.html Contact Info]

===Fellowship projects===

* '''Secure Communications Framework''': An approachable framework for human rights researchers that helps them understand how to communicate with contacts around the world safely in the context of varying threats and information sensitivity.
* '''Community Incident Response''': Help human rights organizations in Amnesty's worldwide network access technical assistance during active digital attacks.

===Personal projects===

* ThunderSec: DKIM, SPF, DNSBL plug-in for Mozilla Thunderbird, [https://addons.mozilla.org/en-US/thunderbird/addon/thundersec/ addons.mozilla.org], [https://github.com/itemir/thundersec GitHub]
* [https://atlas.torproject.org/#search/teamsammut Operate Tor Nodes]
* [https://teamsammut.com/blog/2015/09/apple-macbook-pro-linux-issue-tracking.html Making Linux on the Macbook Pro Retina Less Terrible]

===Things created===

* 1 October 2015, Blog post, '''[https://teamsammut.com/blog/2015/10/three-steps-against-mass-surveillance.html Three Steps Against Mass Surveillance, For Other People ]'''
* 20 September 2015, Blog post, '''[https://teamsammut.com/blog/2015/09/human-rights-education-threat-modeling.html Human Rights Education Threat Modeling]'''
* 12 September 2015, Conference proposal, '''[https://teamsammut.com/blog/2015/09/mozfest-promoting-freedom-of-expression-with-tor.html Promoting Freedom of Expression with Tor]'''
* 14 August 2015, Blog post, '''[https://teamsammut.com/blog/2015/08/tor-hidden-service-for-teamsammut.com.html Tor Hidden Service for teamsammut.com ]'''
* 11 August 2015, Slides, '''Tor vs. VPNs and Proxies''', [https://teamsammut.com/files/presentations/Proxies%20VPNs%20and%20Tor%20v20150715c.pdf PDF], [https://teamsammut.com/files/presentations/Proxies%20VPNs%20and%20Tor%20v20150715c.odp ODF]
* 23 July 2015, Blog post, '''[https://teamsammut.com/blog/2015/07/the-rights-enabling-internet-wont-continue-by-accident.html The Internet that enables human rights won't continue by accident ]'''
* 23 July 2015, Blog post, '''[https://teamsammut.com/blog/2015/06/what-is-the-open-web.html What is the Open Web? ]'''
==Andrea Del Rio, Association for Progressive Communications==
Many of the bad things that happen offline are also true online: for example violence against women, discrimination against LGBT people, hate crimes, inequality of access to basic services or censorship. The project I am working on right now called The Feminist Principles of the Internet aims to inspire people not only to imagine a Feminist Internet but actually build one that is fair, inclusive, empowering and safe for everyone.

Month two blog post:
https://medium.com/@andreadelrio/ford-mozilla-open-web-fellowship-apc-month-2-65aab25f9402

==Drew Wilson, Free Press==
Drew is embedded in Free Press' Internet2016 campaign and is building tools that internet rights advocates can use to bootstrap their own activism projects.

https://internet2016.net/

==Gem Barrett, Open Technology Institute==

==Tennyson Holloway, Public Knowledge==
Tennyson is working on projects that inspire and educate future web advocates. "What can i do for the internet.org" is a website that represents a vision of a story based platform that educates, inspires, and assists users to join the open web movement. His other projects involve creating web games that explain tech policy Washington issues, such as copyright and patent trolls.

Netpolicy/advocacy/openwebfellows

2015-10-02T13:24:35Z

Brett Gaylor: /* Tennyson Holloway, Public Knowledge */

The [https://advocacy.mozilla.org/open-web-fellows/ '''Ford-Mozilla Open Web Fellows Program'''] — a collaboration between the Ford Foundation and Mozilla — is an international leadership initiative that brings together the best emerging technology talent and civil society organizations to protect the open Web. The program fills a critical niche: it provides an ecosystem for the next generation of open Web advocates to make an early impact. As threats to digital freedom proliferate, it’s critical to have capable leaders.

Each year, Fellows spend 10 months embedded at leading advocacy organizations to safeguard the Internet as a global public resource. The 2015 host organizations are:
* American Civil Liberties Union, Massachusetts
* Amnesty International
* Association for Progressive Communications
* Free Press
* Open Technology Institute
* Public Knowledge

= [https://advocacy.mozilla.org/open-web-fellows/ 2015 Fellows]=
==Paola Villarreal, American Civil Liberties Union, Massachusetts==
Data for Justice is a data-driven advocacy tool that visualizes information critical for eliminating injustice in communities.

Read more on the project's Knight News Challenge application
https://www.newschallenge.org/challenge/data/entries/the-data-for-justice-project

==Tim Sammut, Amnesty International==
[https://teamsammut.com Website], [https://twitter.com/t1msammut @t1msammut], [https://teamsammut.com/pages/contact.html Contact Info]

===Fellowship projects===

* '''Secure Communications Framework''': An approachable framework for human rights researchers that helps them understand how to communicate with contacts around the world safely in the context of varying threats and information sensitivity.
* '''Community Incident Response''': Help human rights organizations in Amnesty's worldwide network access technical assistance during active digital attacks.

===Personal projects===

* ThunderSec: DKIM, SPF, DNSBL plug-in for Mozilla Thunderbird, [https://addons.mozilla.org/en-US/thunderbird/addon/thundersec/ addons.mozilla.org], [https://github.com/itemir/thundersec GitHub]
* [https://atlas.torproject.org/#search/teamsammut Operate Tor Nodes]
* [https://teamsammut.com/blog/2015/09/apple-macbook-pro-linux-issue-tracking.html Making Linux on the Macbook Pro Retina Less Terrible]

===Things created===

* 1 October 2015, Blog post, '''[https://teamsammut.com/blog/2015/10/three-steps-against-mass-surveillance.html Three Steps Against Mass Surveillance, For Other People ]'''
* 20 September 2015, Blog post, '''[https://teamsammut.com/blog/2015/09/human-rights-education-threat-modeling.html Human Rights Education Threat Modeling]'''
* 12 September 2015, Conference proposal, '''[https://teamsammut.com/blog/2015/09/mozfest-promoting-freedom-of-expression-with-tor.html Promoting Freedom of Expression with Tor]'''
* 14 August 2015, Blog post, '''[https://teamsammut.com/blog/2015/08/tor-hidden-service-for-teamsammut.com.html Tor Hidden Service for teamsammut.com ]'''
* 11 August 2015, Slides, '''Tor vs. VPNs and Proxies''', [https://teamsammut.com/files/presentations/Proxies%20VPNs%20and%20Tor%20v20150715c.pdf PDF], [https://teamsammut.com/files/presentations/Proxies%20VPNs%20and%20Tor%20v20150715c.odp ODF]
* 23 July 2015, Blog post, '''[https://teamsammut.com/blog/2015/07/the-rights-enabling-internet-wont-continue-by-accident.html The Internet that enables human rights won't continue by accident ]'''
* 23 July 2015, Blog post, '''[https://teamsammut.com/blog/2015/06/what-is-the-open-web.html What is the Open Web? ]'''
==Andrea Del Rio, Association for Progressive Communications==
Many of the bad things that happen offline are also true online: for example violence against women, discrimination against LGBT people, hate crimes, inequality of access to basic services or censorship. The project I am working on right now called The Feminist Principles of the Internet aims to inspire people not only to imagine a Feminist Internet but actually build one that is fair, inclusive, empowering and safe for everyone.

Month two blog post:
https://medium.com/@andreadelrio/ford-mozilla-open-web-fellowship-apc-month-2-65aab25f9402

==Drew Wilson, Free Press==

==Gem Barrett, Open Technology Institute==

==Tennyson Holloway, Public Knowledge==
Tennyson is working on projects that inspire and educate future web advocates. "What can i do for the internet.org" is a website that represents a vision of a story based platform that educates, inspires, and assists users to join the open web movement. His other projects involve creating web games that explain tech policy Washington issues, such as copyright and patent trolls.

Netpolicy/advocacy/openwebfellows

2015-10-02T13:23:53Z

Brett Gaylor: /* Paola Villarreal, American Civil Liberties Union, Massachusetts */

The [https://advocacy.mozilla.org/open-web-fellows/ '''Ford-Mozilla Open Web Fellows Program'''] — a collaboration between the Ford Foundation and Mozilla — is an international leadership initiative that brings together the best emerging technology talent and civil society organizations to protect the open Web. The program fills a critical niche: it provides an ecosystem for the next generation of open Web advocates to make an early impact. As threats to digital freedom proliferate, it’s critical to have capable leaders.

Each year, Fellows spend 10 months embedded at leading advocacy organizations to safeguard the Internet as a global public resource. The 2015 host organizations are:
* American Civil Liberties Union, Massachusetts
* Amnesty International
* Association for Progressive Communications
* Free Press
* Open Technology Institute
* Public Knowledge

= [https://advocacy.mozilla.org/open-web-fellows/ 2015 Fellows]=
==Paola Villarreal, American Civil Liberties Union, Massachusetts==
Data for Justice is a data-driven advocacy tool that visualizes information critical for eliminating injustice in communities.

Read more on the project's Knight News Challenge application
https://www.newschallenge.org/challenge/data/entries/the-data-for-justice-project

==Tim Sammut, Amnesty International==
[https://teamsammut.com Website], [https://twitter.com/t1msammut @t1msammut], [https://teamsammut.com/pages/contact.html Contact Info]

===Fellowship projects===

* '''Secure Communications Framework''': An approachable framework for human rights researchers that helps them understand how to communicate with contacts around the world safely in the context of varying threats and information sensitivity.
* '''Community Incident Response''': Help human rights organizations in Amnesty's worldwide network access technical assistance during active digital attacks.

===Personal projects===

* ThunderSec: DKIM, SPF, DNSBL plug-in for Mozilla Thunderbird, [https://addons.mozilla.org/en-US/thunderbird/addon/thundersec/ addons.mozilla.org], [https://github.com/itemir/thundersec GitHub]
* [https://atlas.torproject.org/#search/teamsammut Operate Tor Nodes]
* [https://teamsammut.com/blog/2015/09/apple-macbook-pro-linux-issue-tracking.html Making Linux on the Macbook Pro Retina Less Terrible]

===Things created===

* 1 October 2015, Blog post, '''[https://teamsammut.com/blog/2015/10/three-steps-against-mass-surveillance.html Three Steps Against Mass Surveillance, For Other People ]'''
* 20 September 2015, Blog post, '''[https://teamsammut.com/blog/2015/09/human-rights-education-threat-modeling.html Human Rights Education Threat Modeling]'''
* 12 September 2015, Conference proposal, '''[https://teamsammut.com/blog/2015/09/mozfest-promoting-freedom-of-expression-with-tor.html Promoting Freedom of Expression with Tor]'''
* 14 August 2015, Blog post, '''[https://teamsammut.com/blog/2015/08/tor-hidden-service-for-teamsammut.com.html Tor Hidden Service for teamsammut.com ]'''
* 11 August 2015, Slides, '''Tor vs. VPNs and Proxies''', [https://teamsammut.com/files/presentations/Proxies%20VPNs%20and%20Tor%20v20150715c.pdf PDF], [https://teamsammut.com/files/presentations/Proxies%20VPNs%20and%20Tor%20v20150715c.odp ODF]
* 23 July 2015, Blog post, '''[https://teamsammut.com/blog/2015/07/the-rights-enabling-internet-wont-continue-by-accident.html The Internet that enables human rights won't continue by accident ]'''
* 23 July 2015, Blog post, '''[https://teamsammut.com/blog/2015/06/what-is-the-open-web.html What is the Open Web? ]'''
==Andrea Del Rio, Association for Progressive Communications==
Many of the bad things that happen offline are also true online: for example violence against women, discrimination against LGBT people, hate crimes, inequality of access to basic services or censorship. The project I am working on right now called The Feminist Principles of the Internet aims to inspire people not only to imagine a Feminist Internet but actually build one that is fair, inclusive, empowering and safe for everyone.

Month two blog post:
https://medium.com/@andreadelrio/ford-mozilla-open-web-fellowship-apc-month-2-65aab25f9402

==Drew Wilson, Free Press==

==Gem Barrett, Open Technology Institute==

==Tennyson Holloway, Public Knowledge==

Netpolicy/advocacy/openwebfellows

2015-10-02T13:21:51Z

Brett Gaylor: /* Andrea Del Rio, Association for Progressive Communications */

The [https://advocacy.mozilla.org/open-web-fellows/ '''Ford-Mozilla Open Web Fellows Program'''] — a collaboration between the Ford Foundation and Mozilla — is an international leadership initiative that brings together the best emerging technology talent and civil society organizations to protect the open Web. The program fills a critical niche: it provides an ecosystem for the next generation of open Web advocates to make an early impact. As threats to digital freedom proliferate, it’s critical to have capable leaders.

Each year, Fellows spend 10 months embedded at leading advocacy organizations to safeguard the Internet as a global public resource. The 2015 host organizations are:
* American Civil Liberties Union, Massachusetts
* Amnesty International
* Association for Progressive Communications
* Free Press
* Open Technology Institute
* Public Knowledge

= [https://advocacy.mozilla.org/open-web-fellows/ 2015 Fellows]=
==Paola Villarreal, American Civil Liberties Union, Massachusetts==

==Tim Sammut, Amnesty International==
[https://teamsammut.com Website], [https://twitter.com/t1msammut @t1msammut], [https://teamsammut.com/pages/contact.html Contact Info]

===Fellowship projects===

* '''Secure Communications Framework''': An approachable framework for human rights researchers that helps them understand how to communicate with contacts around the world safely in the context of varying threats and information sensitivity.
* '''Community Incident Response''': Help human rights organizations in Amnesty's worldwide network access technical assistance during active digital attacks.

===Personal projects===

* ThunderSec: DKIM, SPF, DNSBL plug-in for Mozilla Thunderbird, [https://addons.mozilla.org/en-US/thunderbird/addon/thundersec/ addons.mozilla.org], [https://github.com/itemir/thundersec GitHub]
* [https://atlas.torproject.org/#search/teamsammut Operate Tor Nodes]
* [https://teamsammut.com/blog/2015/09/apple-macbook-pro-linux-issue-tracking.html Making Linux on the Macbook Pro Retina Less Terrible]

===Things created===

* 1 October 2015, Blog post, '''[https://teamsammut.com/blog/2015/10/three-steps-against-mass-surveillance.html Three Steps Against Mass Surveillance, For Other People ]'''
* 20 September 2015, Blog post, '''[https://teamsammut.com/blog/2015/09/human-rights-education-threat-modeling.html Human Rights Education Threat Modeling]'''
* 12 September 2015, Conference proposal, '''[https://teamsammut.com/blog/2015/09/mozfest-promoting-freedom-of-expression-with-tor.html Promoting Freedom of Expression with Tor]'''
* 14 August 2015, Blog post, '''[https://teamsammut.com/blog/2015/08/tor-hidden-service-for-teamsammut.com.html Tor Hidden Service for teamsammut.com ]'''
* 11 August 2015, Slides, '''Tor vs. VPNs and Proxies''', [https://teamsammut.com/files/presentations/Proxies%20VPNs%20and%20Tor%20v20150715c.pdf PDF], [https://teamsammut.com/files/presentations/Proxies%20VPNs%20and%20Tor%20v20150715c.odp ODF]
* 23 July 2015, Blog post, '''[https://teamsammut.com/blog/2015/07/the-rights-enabling-internet-wont-continue-by-accident.html The Internet that enables human rights won't continue by accident ]'''
* 23 July 2015, Blog post, '''[https://teamsammut.com/blog/2015/06/what-is-the-open-web.html What is the Open Web? ]'''
==Andrea Del Rio, Association for Progressive Communications==
Many of the bad things that happen offline are also true online: for example violence against women, discrimination against LGBT people, hate crimes, inequality of access to basic services or censorship. The project I am working on right now called The Feminist Principles of the Internet aims to inspire people not only to imagine a Feminist Internet but actually build one that is fair, inclusive, empowering and safe for everyone.

Month two blog post:
https://medium.com/@andreadelrio/ford-mozilla-open-web-fellowship-apc-month-2-65aab25f9402

==Drew Wilson, Free Press==

==Gem Barrett, Open Technology Institute==

==Tennyson Holloway, Public Knowledge==

WeeklyUpdates/2014-09-08

2014-09-08T17:55:51Z

Brett Gaylor: /* Webmaker */

{{WeeklyUpdateNav}}
{{conf|8600}}

__TOC__

= All-hands Status Meeting Agenda =

Items in this section will be shared during the live all-hand status meeting.

== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==
A huge "spaceba" to Max Zhilyaev for marketing tag line translations for the Russian activations directory. "Domo Arigato Gozaimasu" to Manabu Ito for marketing tag line translations for the Japanese activations directory. "Děkuji" to Michal Stanke for localization of the Czech activations directory.

Jorge Aparicio (japaric) created the [http://www.reddit.com/r/rust/comments/2f3nf3/project_euler_benchmarks/ Eulermark] benchmark from the Project Euler problems, demonstrating that Rust compares favorably to C++ in many cases.

Thank you to Bob Reyes for wrangling the Mozilla Philippines community work last week!

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===

Please send your contribution opportunities for the Community Newsletter to jhalperin@mozilla.com

=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===
3pm-3.30pm BST: [https://air.mozilla.org/introduction-to-web-audio/ Introduction to Web Audio] - live from Mozilla London!

12pm - 1pm PT: reddit AMA on net neutrality with Dave Steer and Chris Riley. Please participate [https://www.reddit.com/r/IAmA/ here].

'''Intern Presentations!'''
*1:00PM 1:00- Filipe Gonçalves, "Coping with memory addiction: tricking Firefox OS for fun and profit" SF
*1:30PM 1:30- Bernardo Rittmeyer, "TBD" SF
*2:00PM 2:00- John Zeller, "TBD" SF
*2:30PM 2:30- Chance Zibolski, "Heka, the "Swiss Army Knife" of Data" SF

'''Bi-weekly [https://wiki.mozilla.org/Marketplace/Community/Meetings Markeplace Community Meeting]:''' [http://www.worldtimebuddy.com/?qm=1&lid=1850147,5375480,2643743,1277333&h=5375480&date=2014-8-11&sln=10-10.5 10am Pacific]. It's getting easier to plug into this project, so come and see how you can make an impact this month.

=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===
A Day of Action to protect net neutrality (read about Mozilla's involvement [https://blog.mozilla.org/netpolicy/2014/09/04/a-day-of-action-to-protect-net-neutrality/ here])

'''[http://indiewebcamp.com/events/2014-09-10-homebrew-website-club Homebrew Website Club Meetup]'''
* Chicago, Minneapolis, Portland (@[[MozPDX]]), and San Francisco (@[[MozSF]])!
* 17:30-18:30 Writing Hour
* 18:30-19:30 IndieWeb discussions and hack night
<blockquote>Are you creating your own website? Indie reader? Personal publishing web app? Or some other digital magic-cloud proxy?If so (or you want to!), come on by and join a gathering of people with like-minded interests. Bring your friends that want to start a personal web site. Exchange information, swap ideas, talk shop, help work on a project...</blockquote> Any questions? See '''[http://indiewebcamp.com/events/2014-09-10-homebrew-website-club the wiki page for details]''' or join IRC: http://indiewebcamp.com/irc/today

'''Mozpub'''
*Mozfest Volunteer social in the common space at Mozilla LDN from 18:30- 21:00
*Sign up [https://sendto.mozilla.org/page/s/10th-sept-2014-mozpub '''here'''] to attend

'''Intern Presentations!'''
*1:00- Sylvain Cleymans, "Better, faster, lighter: improving the mobile web experience with the Janus proxy" MV
*1:30- Dean Johnson, "TBD" MV
*2:00- Ian Kronquist, "TBD" MV
*2:30- Tyler Smith, "TBD" MV

=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===

'''Intern Presentations'''
*1:00- Robert Bindar, "Hacking through notifications" SF
*1:30- Sean Bolton, "Why We Build How We Build" SF
*2:00- Roshan Vid, "TBD" SF
*2:30- Laleh Aghababaie Beni, "TBD" SF

=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===
'''RemoCamp in Berlin''', until Sept 14th.

More info on the wiki: https://wiki.mozilla.org/ReMo/Council/ReMo_Camp_2014

=== Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===

=== Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===

=== Next Week ===

== Project Status Updates (voice updates) ==

=== Firefox ===
''Speaker Location:''
* Growth team update - Winston Bowden (remote)

=== Firefox OS ===
''Speaker Location: Faramarz Rashed / Chris Lee - Mountain View''

''Speaker Location: Asa Dotzler in Mountain View''
* [https://mozillians.org/en-US/u/arvin0731/ Arvin Huang] is a grad student at National Cheng Kung University in Taipei, and he fixed his first 2 Firefox OS bugs this week, a pair of [good first bug][mentor-lang=zh] Gaia Build jshint error bugs.
* Last tuesday, Mozilla branched Firefox OS 2.1/Gecko 34 and opened OS 2.2 development. (Also, mozilla-b2g28_v1_3 has been shut down.)
* Over the last week, ~130 Mozillians contributed code to resolve ~300 Firefox OS issues.

* The top three contributors by volume were
** [https://mozillians.org/en-US/u/mnjul/ John Lu] in Taipei, who worked heavily on Lockscreen and Keyboard
** [https://mozillians.org/en-US/u/crh/ Arthur Chen], also in Taipei, brought us some serious new feature work on APN
** and [https://mozillians.org/en-US/u/kevining/ Keven Grandon], out of San Francisco, landed lots of improvements to Rocketbar/Homescreen, and browsing.

* Foxtrot program is delayed while we wait on proper nightly builds from our partner. An email to this effect will go out this week. While we don't yet have a definite date, it's our hope to get things moving in weeks, not months.

* Mozilla Flame stock nearly exhausted. We're ordering more Flames to give away to our community of contributors. If Firefox OS is your job and you don't have a Flame to work on, please let me know ASAP (asa@mozilla.com)

* VIA Vixen tablets on the way. We'll open a second round of tablet applications, similar to first round. Vixen contributors will work within the larger [https://wiki.mozilla.org/FirefoxOS/TCP Tablet Contribution Program] to further the development of Firefox OS for larger form factors.

      A taste of recent Firefox OS changes:<div style="margin-left: 1.5em; margin-right: 4em; height:14em; overflow:auto; border: 1px solid #088">
* {{bug|1057578}} - New overscroll effect. Scrollable content is stretched uniformly along the overscrolled axis
* {{bug|1033549}} - Data tracking on a per app basis.
* {{bug|903683}} - Support for user configurable 24 hour time format
* {{bug|1032631}} - EU roaming APN support
* {{bug|1026685}} - CMAS Alert channel support. Location-based messaging for governments
* {{bug|1011738}} - Theme support for b2g/gaia
* {{bug|1060081}} - Support for Flame Kitkat (KK) builds
* {{bug|1060879}} - Fixes first tap on keyboard being inaudible
* {{bug|1046336}} - New homescreen unlock and keyboard sounds.
* {{bug|985334}} - Long press on a key, the first choice should be the key that is pressed.
* {{bug|1054184}} - Keyboard 2.1 often misses first keystroke
* {{bug|1061439}} - Prevent IMEngine from touching layouts when inputcontext is gone
* {{bug|1048792}} - Keyboard should not autocorrect words with different char count than input
* {{bug|1048869}} - Keyboard autosuggest nearby keys algorithm doesn't value vertical alignment enough
* {{bug|1016184}} - Enable touch caret on B2G and fix the existing test case failures
* {{bug|1029943}} - Enable selection carets on B2G and fix the existing test case failures
* {{bug|1042713}} - Remove notification icons from status bar now that we have ambient notifications
* {{bug|1035250}} - Show cell and wifi status indicators as users progress through First Time Experience
* {{bug|1054352}} - New videos in FTE tutorial for Vertical Scroll, Sheets, Universal Search, Notifications
* {{bug|1038723}} - Visual refresh of the utility tray and ambient notifications.
* {{bug|1056969}} - Prettifies the data connection indicators in the statusbar
* {{bug|1030925}} - Visual Refresh in Messaging
* {{bug|1041765}} - Messaging thread view redesign
* {{bug|1048845}} - Messaging Compose Panel refresh (subject behavior change)
* {{bug|1048362}} - Messaging Compose Panel refresh (highlight actionable part)
* {{bug|1043177}} - Contacts App: The current Contact edit page is quite messy
* {{bug|885110 }} - Email App: Switch to whiteout-io email.js libraries
* {{bug|1019816}} - Developer option to store logcat to sdcard by shaking the phone
</div>

=== Cloud Services ===
''Speaker Location:''

=== Content Services ===
[[File:Directory-tiles-new-tab-page-screenshot.png|thumbnail]]
''Speaker Location:''
* Bryan Clark - YVR
* Please check out Darren's [https://air.mozilla.org/town-hall-sustainability-3-shifting-the-advertising-industry/ Town Hall on Shifting the Ad Industry]
* [[Tiles]]
** Tiles team (Bryan, Ed, Aaron, Sean) had their Town Hall on the product, features and status last week. [https://air.mozilla.org/mozillians-town-hall-2014-goals-sustainability-series-tiles/ Check out the video here]
** Tiles merged into Beta 33 en-US builds last week

=== Webmaker ===
Brett Gaylor, remote from Victoria BC
* A few images from the Maker Party to whet your appetite for our final retrospective

=== Mozilla Communities ===
''Speaker Location: non-verbal / Surman''

* As noted last meeting, we're actively looking for new ways community can have impact on topline goals in Q3/Q4.

* We've developed a tentative set of goals for this time frame, which are:
** Maintain momentum on our community goal (Q3/4)
** Start new community initiatives / challenges that interest volunteers and have positive impact on our product goals (Q3/4)
** Involve leadership from across the project and within regional communities (Q3/4)
** Design an even more ambitious plan for 2015+ (Q4)

* We'll be discussing these goals and short term community 'challenges' tied to products at ReMo camp in Berlin next weekend.
** A list of possible challenges is here: https://cbt.etherpad.mozilla.org/contribution-challenges
** If you have ideas to add to this list, reach out to Kirstin Baird and David Boswell.

* Full update from Mitchell / Surman coming on this topic next week. Non-verbal for today.

=== Web Compat ===
''Speaker Location: Vidyo (miketaylr)''

'''FYI:''' Our team is doing some work to clean up the Tech Evangelism component, moving valid issues to the Desktop product. Going forward, please use that rather than language specific products.

Recent bug fixes:

*[https://bugzilla.mozilla.org/show_bug.cgi?id=1051511 Searchbar is skinny in Google sites] fixed. Huge thanks to Daniel Hobert and Tab Atkins for getting this fixed so quickly.
*[https://bugzilla.mozilla.org/show_bug.cgi?id=754754 Modern Google Docs] served to Firefox for Android (now with less infinite redirect loops!)
*[https://bugzilla.mozilla.org/show_bug.cgi?id=1009462 Flickr no longer sending Firefox OS useres to to iPhone app install page]

On the webcompat.com front, a million thanks to:
* Karl Dubost for his [https://github.com/webcompat/webcompat.com/pull/254 recent contributions on our CONTRIBUTING.md document], making it easier for people to get a dev env set up.
* Guillaume Demesy for his tireless work to [https://github.com/webcompat/webcompat.com/pull/249 remove our Twitter Bootstrap dependency] (essentailly, re-writing all the CSS).

Bugs wanted: [http://webcompat.com/ http://webcompat.com/]

== Speakers ==

The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week.

{| class="fullwidth-table wikitable"
|-
! [https://mozillians.org/u/USERNAME Presenter]
! Title
! Topic
! Location
! Share?
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, other info)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
| Dave Steer
| Director of Advocacy
| Net neutrality Day of Action + reddit AMA
| SF
| no
|
| https://blog.mozilla.org/netpolicy/2014/09/04/a-day-of-action-to-protect-net-neutrality/, https://www.reddit.com/r/IAmA/, http://mzl.la/nnpetition
|-
| Anthony Duignan-Cabrera
| Editor in Chief of the Site-Formerly-Called-Mozilla-Voices
| The NEW name for Mozilla Voices is...
| NYC
| no
|
| https://blog.mozilla.org/community/2014/09/04/mozilla-voices-has-a-new-name/
|-
| Lukas Blakk, Kronda Adair, Debbie Cohen, Dino Anderson, and the awesome, trailblazing cohort
| ASCEND Project
| The Ascend Project is a 6 week, full time training program that provides financial support, equipment, meals, transit, and childcare reimbursement in order to remove many of the barriers to immersive learning in Open Source technology.
| Portland in da haus
| No
| No
| [http://ascendproject.org/about/index.html ASCEND Project]
|}

= Roundtable =

Do you have a question about a Mozilla Project or initiative? Let us know by Friday- we'll do our best to get you an answer.

Please note that we may not always be able to get to every item on this list, but we will try!

{| class="fullwidth-table"
|-
! Who are you?
! Area of question
! Question
|-
| ''What's your name? What do you work on?''
| ''Is your question about policy, a product, a Foundation initiative, etc.''
| ''What would you like to know?''

|-
|}

= Welcome! =

Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.

== Introducing New Volunteers ==
{| class="fullwidth-table"
|-
! New Volunteer(s)
! Introduced by
! Speaker location
! New Volunteer location
! Will be working on
|-
| ''Who is the new volunteer(s)?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where is the new person based?''
| ''What will the new person be doing?''
|-

|-
|}

== Introducing New Hires ==
{| class="fullwidth-table wikitable"
|-
! New Hire
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new hire?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-

|-
| Tom Tromey
| Jordan Santell
| SF Office
| US Remote
| Firefox Content Tools
|-
| Matt Rosenberg
| ADC Duignan-Cabrera
| New York Office
| US Remote
| Marketing Communications
|-
| Brittany Storoz
| Fred Wenzel
| Portland Office
| NYC
| Apps Engineering
|-
| Alberto Pastor
| Michael Henretty
| San Francisco Office
| Barcelona
| Firefox OS
|-
|}

== Introducing New Interns ==
{| class="fullwidth-table wikitable"
|-
! New Intern
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new intern?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-

|-
|}

= <meta> =

Notes and non-voice status updates that aren't part of the live meeting go here.

== Status Updates By Team (*non-voice* updates) ==

=== Firefox ===

=== Platform ===

=== Cloud Services ===

=== Messaging ===

=== Mobile ===

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== WebQA ====

==== QA Community ====

=== Automation & Tools ===
==== bugzilla.mozilla.org ====
Notable changes to [https://bugzilla.mozilla.org/ bugzilla.mozilla.org] during the last week:
* {{bug|1056162}} Bugzilla can now create short URLs for bug searches (using bit.ly)
[[BMO/Recent_Changes|All changes]].

=== Security ===

=== Engagement ===

* [https://docs.google.com/a/mozilla.com/spreadsheets/d/1X5kUBkEAicEe2unDaaLGTYzAJbphWFoaJYBTasHrcHQ/edit#gid=1764494528 Engagement's Active Project Dashboard]

==== PR ====

==== Events ====

==== Social Support ====

WeeklyUpdates/2014-08-18

2014-08-18T17:57:26Z

Brett Gaylor: /* Webmaker */

{{WeeklyUpdateNav}}
{{conf|8600}}

__TOC__

= All-hands Status Meeting Agenda =

Items in this section will be shared during the live all-hand status meeting.

== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===

* If you have any time-bound contribution activities for the Mozilla community, please email Jennie at jhalperin@mozilla.com. Your opportunities will be featured in the next issue of [https://blog.mozilla.org/about_mozilla/ about:Mozilla]!

=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===

=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===
* Mozillians Town Hall - Shifting the Advertising Industry (Sustainability #3)
** Air Mozilla - https://air.mozilla.org/town-hall-sustainability-3-shifting-the-advertising-industry/
** 10:00am - 11:00am PT Cyberspace only (not in SF or MV Commons).
* [http://braziljs.com.br/en/ BrazilJS 2014]
** Check out the [https://wiki.mozilla.org/Engagement/Brand_Engagement/Events_Team/Big_5_2014/BrazilJS2014 Wiki landing page] for details on Mozilla's presence at BrazilJS
** Conference is Aug 21 & 22, Mozilla activities begin Aug 20.
** Second of the Big 5 series of events for the Apps & Marketplace, Dev Rel, and Dev Tools Teams.

=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===

* 10:00 AM Pacific / 17:00 UTC: Grow Mozilla discussion -- a forum for discussing community building at Mozilla
** [[Grow/Meeting_08_21_14|Agenda and dial-in information]] (feel free to add items to the agenda)

=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===

=== Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===

=== Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===

=== Next Week ===

== Project Status Updates (voice updates) ==

=== Firefox ===
''Speaker Location: Toronto (johnath)''
* Go watch last week's [http://mzl.la/1riKJux town hall] if you missed it
* Growth team comin' atcha

=== Firefox OS ===
''Speaker Location:''
* Li Gong in Mountain View

=== Cloud Services ===
''Speaker Location:''

=== Content Services ===
''Speaker Location:''
* Darren Herman in New York
*TILES
** Town Hall!
* UP
**Continue to develop the Personal Interest Dashboard add-on and running experiments with personalized newsfeeds
**UP Wiki https://intranet.mozilla.org/UP
*Subscribe to Web
**Wiki page is live! https://intranet.mozilla.org/Subscribe2Web
**Pilot1 is planned for Q4 2014 in Poland and Sweden
**Scheduling a Brown Bag in the next couple of weeks

=== Webmaker ===
''Speaker Location:Brett Gaylor - Remote''
* Maker Party continues to roll out -- going well
** Contributors: 5552 (2% increase from last week’s 5441)
** Webmaker accounts: 124K (17% increase from last week’s 106.3K)
** Events: 1799 (50% jump from last week’s 1199)
** Hosts: 493 (10% increase from last week’s 450)
** Expected attendees: 76,200 (23% increase from 61,910)
** Cities: 362 (40% increase from 260)
** http://hannahgrams.com/2014/08/17/maker-party-engagement-week-5/
** http://openmatt.org/2014/08/18/data_tells_us/
* Big step forward with Mobile Appmaker last week
** One of our goals with Webmaker this year is to add a focus on apps
** As part of this, released Appmaker for Desktop in beta for Maker party
** Over the last few weeks we've made progress on the next step: app made on a mobile device
** At a workweek in Portland last week, the team settled on a product strategy for the next couple months
** They are now sprinting towards the first prototype to be shown in Dhaka, Bangladesh next week
** Note: brief presentation on this later in the meeting

=== Mozilla Communities ===
''Speaker Location: Mark Surman Remote''

* Headline: we're looking for new ways community can contribute to top line goals
** This year, Mozilla has a goal to 'enable communities that have impact'
** https://wiki.mozilla.org/2014#Enable_Communities_that_have_Impact
*** Much of the focus so far has been on growth, and we're making some progress
** We need to shift our focus towards quality and impact that contributors can have
** Over the coming weeks: community building teams are actively looking for new ways community can have an impact on top line goals
** E.g. are there creative ways that community can help get Firefox on a growth trajectory?
** Mark (MoFo), Mary Ellen (Engagement), Mitchell (chair) are helping the community teams with this
** If you have ideas, reach out to David Boswell or one of the exec team working this
** Expect more reports in coming weeks

== Speakers ==

The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week.

{| class="fullwidth-table wikitable"
|-
! [https://mozillians.org/u/USERNAME Presenter]
! Title
! Topic
! Location
! Share?
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, other info)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
| Andrew Sliwinski and Simon Wex
| WebMaker
| Mobile Appmaker work week
| Portland/Remote
| Yes
| [https://www.dropbox.com/s/rqihc9kpl2kic4e/demo_20140818_00.pdf Slides]
| Import / Export API for Apps [https://bugzilla.mozilla.org/show_bug.cgi?id=982874] // App for Import/Export of Apps via SD Card [https://bugzilla.mozilla.org/show_bug.cgi?id=1001704] // Device-to-Device App Transfer via NFC [https://bugzilla.mozilla.org/show_bug.cgi?id=969939]
|-
| Andrea Wood
| Digital Fundraising & Advocacy (mofo)
| Community Indiegogo Campaigns // Maker Party Snippet
| My house (Oakland CA)
| No
| na
| Find Indiegogo campaign info [https://wiki.mozilla.org/Foundation/Indiegogo here] // [https://brianloveswords.github.io/webmaker-firefox-snippet/ Click here] to preview and try out the Interactive Snippet - and you can read [http://jessicaklein.blogspot.com/2014/08/remix-hack-firefox-home-page-no-really.html a blog post] by the lead designer
|
|-
| Karen Ward
| Program Management
| Scaling Firefox OS device production & delivery - Firefox OS Mobile Partner Site
| Remote (My house)
| No
| https://mobilepartners.mozilla.org/
| https://mobilepartners.mozilla.org/
|}

= Roundtable =

Do you have a question about a Mozilla Project or initiative? Let us know by Friday- we'll do our best to get you an answer.

Please note that we may not always be able to get to every item on this list, but we will try!

{| class="fullwidth-table"
|-
! Who are you?
! Area of question
! Question
|-
| ''What's your name? What do you work on?''
| ''Is your question about policy, a product, a Foundation initiative, etc.''
| ''What would you like to know?''

|-
|}

= Welcome! =

Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.

== Introducing New Volunteers ==
{| class="fullwidth-table"
|-
! New Volunteer(s)
! Introduced by
! Speaker location
! New Volunteer location
! Will be working on
|-
| ''Who is the new volunteer(s)?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where is the new person based?''
| ''What will the new person be doing?''
|-

|-
|}

== Introducing New Hires ==
{| class="fullwidth-table wikitable"
|-
! New Hire
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new hire?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-

|-
| Justin Terry
| Darren Herman
| New York Office
| New York Office
| Content Partnerships, Partner Success & Content Platform Operations
|}

== Introducing New Interns ==
{| class="fullwidth-table wikitable"
|-
! New Intern
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new intern?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-

|-
|}

= <meta> =

Notes and non-voice status updates that aren't part of the live meeting go here.

== Status Updates By Team (*non-voice* updates) ==

=== Firefox ===

=== Platform ===

=== Cloud Services ===

=== Messaging ===

=== Mobile ===

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== WebQA ====

==== QA Community ====

=== Automation & Tools ===
==== bugzilla.mozilla.org ====
Notable changes to [https://bugzilla.mozilla.org/ bugzilla.mozilla.org] during the last week:
* {{bug|1041964}} Added an indication that a comment is required when setting some tracking flag values
[[BMO/Recent_Changes|All changes]].

=== Security ===

=== Engagement ===

* [https://docs.google.com/a/mozilla.com/spreadsheets/d/1X5kUBkEAicEe2unDaaLGTYzAJbphWFoaJYBTasHrcHQ/edit#gid=1764494528 Engagement's Active Project Dashboard]

==== PR ====

==== Events ====

==== Social Support ====

=== Apps & Marketplace ===

* [https://hacks.mozilla.org/2014/08/time-to-get-hacking-introducing-rec-room/ recroom toolchain "released" via a blog post on Hacks Blog] -- a set of framework+tools for writing awesome Firefox OS apps. Targets intermediate developers, which feels like a gap in our tools right now.

WeeklyUpdates/2014-08-11

2014-08-11T17:48:35Z

Brett Gaylor:

{{WeeklyUpdateNav}}
{{conf|8600}}

__TOC__

= All-hands Status Meeting Agenda =

Items in this section will be shared during the live all-hand status meeting.

== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==
* Interns Anhad Singh and Ian Connolly, for working to open up Release Engineering. Ian and Anhad have been creating useful [[ReleaseEngineering/Contribute|wiki content for contributors]], getting Release Engineering on [http://whatcanidoformozilla.org/ http://whatcanidoformozilla.org/] and [http://www.joshmatthews.net/bugsahoy http://www.joshmatthews.net/bugsahoy] and putting useful whiteboard tags in bugs. Also, new Release Engineering contributors Sergio Butero and Harsimran Singh, who made their first contributions as a result of Anhad and Ian's efforts!

* Luis Antonio Sánchez Romero from Mexico has been helping us test Payments in Mexico by acquiring local SIMs and running tests for us. Payments team thanks him for all his efforts!

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===
* The latest edition of [https://wiki.mozilla.org/Engagement/Developer_Engagement/DevPulse DevPulse] is [https://wiki.mozilla.org/Engagement/Developer_Engagement/DevPulse/August2014 up] - have a read and see how you can get involved with Mozillians supporting developers worldwide!

* Join us at [http://www.worldtimebuddy.com/?qm=1&lid=1850147,5375480,2643743,1277333&h=5375480&date=2014-8-11&sln=14-14.5 2pm Pacific] for the bi-weekly [https://wiki.mozilla.org/Marketplace/Community/Meetings Marketplace community meeting]. This week, we'll talk about the new proposed format for Marketplace contributions, and a new community curation program for the feed feature.

=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===

=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===
'''Mozillians Town Hall - Get Firefox on a Growth Trajectory'''
* Time: 10:00am - 11:00am
* Air Mozilla: https://air.mozilla.org/mozillians-town-hall-2014-goals-getting-firefox-on-a-growth-trajectory/
* Questions: https://moderator.paas.allizom.org/e/town-hall-2014-goals-firefox-13-aug
'''Intern Presentations'''
* 1:00- Susanna Bowen, "Improving Support for CSS Ruby" SF
* 1:30- Jonathan Morton, "WebGL in Web Workers" SF
* 2:00- Julian Hector, "IPC, supervisor and FirefoxOS" SF
* 2:30- James Hobin, "A Cake Filled With Rainbows, Smiles, and JavaScript" SF
'''js13kGames 2014 Competition'''
* JavaScript coding competition for HTML5 game developers that takes place online Aug 13 through Sept 13
* Run by Mozillian Andrzej "Captain Rogers" Mazur, Mozillian Jason Weathersby is a competition judge
* [http://js13kgames.com/ Competition homepage]

=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===
'''Intern Presentations'''
* 1:00- Guptha Rajagopal, "SpiderMonkey - More Strings, More Class" MV
* 1:30- Jeremy Poulin, "Predictor: Because Witches Are Scary" MV
* 2:00- Sathyanarayanan Gunasekaran, "Games, games and more games" MV
* 2:30- Basar Koc, "Ringing Artifacts in Data Compression" MV

=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===
* [[Webdev/Beer_And_Tell/August2014|Webdev Beer and Tell]] - 2PM Pacific in the Webdev vidyo room
** Web developers across the project show off their side projects. Open to the public! (Airmo link will be on the wiki page)

=== Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===
* [http://opennews.org/fellowships/apply.html Application to apply] to become a 2015 Knight-Mozilla Fellow closes at MIDNIGHT eastern!

=== Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===

=== Next Week ===
* Mozillians Town Hall - Disrupting the Advertising Industry
** More information coming soon

== Project Status Updates (voice updates) ==

=== Firefox ===
* Johnathan Nightingale - Toronto

=== Firefox OS ===

* Li Gong from London (Vidyo)

=== Cloud Services ===
''Speaker Location:''

=== Content Services ===

* Darren Herman / Sean Bohan - NYC Office
* Tiles - We are NOT doing a Brown Bag this week, but we have scheduled a Town Hall discussion next Monday Aug 18
* Subscribe2Web - updating the wiki this week and scheduling a Brown Bag session for the week of August 25
* UP - The User Personalization team is working on introducing personalization to Firefox users, starting with data transparency. We are planning on surfacing this through the Personal Interest Dashboard (working name). This will be initially released as an add-on with the objective of providing the user the ability to 1) analyze their categorized interests based on their history and 2) discover new content that's related to their interests

=== Webmaker ===
''Speaker Location: Brett Gaylor, remote''
* We're just about half way through with Maker Party and we have over 1200 events in 261 cities, with an estimated 62,000 attendees!
* We passed a significant milestone - 5000 contributors to Mozilla Foundation activities!

=== Knight-Mozilla OpenNews ===
''Speaker Location: Dan Sinker, remote''
* The application to apply to become a 2015 Knight-Mozilla Fellow closes THIS Saturday at midnight!
** application form: http://opennews.org/fellowships/apply.html
* Fellowships offer creative coders an opportunity to be embedded in newsrooms around the world, working in the open and solving complex problems.
** [http://dansinker.com/post/93888022860/opennews-2015partners our host newsrooms make their pitch]
* The Knight-Mozilla Fellowship is also about community-building and, well, fellowship.
** [http://dansinker.com/post/93906688160/opennews-so-what-is-the-fellowship-experience-like our current fellows talk about their experiences]
* You (yes you!) know great people that should apply. Send them our way!
** example tweets, program description for copy/pasting, and more: https://etherpad.mozilla.org/opennews-fellowships-share

=== Mozilla Communities ===
''Speaker Location:''

=== Marketplace ===
* Non verbal.
* We are trying out a new development environment for the Marketplace using Docker. If you'd like to try it out [https://etherpad.mozilla.org/mkt-docker-dev-env-instructions instructions are here].
* We are also looking for app developers who'd like to try out the [https://wiki.mozilla.org/Marketplace/InAppPayments new hosted in-app payment system] and give us feedback.

== Speakers ==

The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week.

{| class="fullwidth-table"
|-
! [https://mozillians.org/u/USERNAME Presenter]
! Title
! Topic
! Location
! Share?
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, other info)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
| Tyler Downer
| Project Manager, User Advocacy Team
| Firefox Updates Hotfix
| Home Office Vidyo
| No
| (https://docs.google.com/a/mozilla.com/presentation/d/15ehWmUsyzzMWcOnuvwr0N5KXKBw36HEXCLWgNlhLD54/edit?usp=sharing)
| https://blog.mozilla.org/useradvocacy/2014/07/30/helping-our-users-experience-the-modern-web/
|-
| Mary Ellen Muckerman
| Brand (Engagement)
| Two new initiatives (Voices + Mozilla identity)
| San Francisco
| No
| No
|
|-
| Anthony Duignan-Cabrera
| Editor in Chief, Mozilla Voices
| Mozilla Voices
| NYC Office
| No
| No
| https://wiki.mozilla.org/Mozilla_Voices
|-
| Sean Martell
| Art Director
| Mozilla identity
| Toronto home office
| No
| No
|
|-
| Karen Ward
| Senior Project Manager, Operator Launch Team
| FxOS Launch Roadmap (Operators and Retail/Open Market devices)
| Home Office Vidyo
| No
| https://mana.mozilla.org/wiki/display/PM/Firefox+OS+Wave+Launch+Cross+Functional+View
| https://mana.mozilla.org/wiki/display/PM/Firefox+OS+Wave+Launch+Cross+Functional+View
|-

| Jorge Villalobos
| Add-ons Developer Relations Lead
| Add-on Compatibility
| Home Office Vidyo
| No
| [https://slidebean.com/p/5jiyNzH68e/How-we-manage-Add-on-Compatibility Slides]
| [https://blog.mozilla.org/addons/ Add-ons Blog]
|-

|-
| Brett Gaylor
| VP, Webmaker
| Webmaker - the party is getting out of control
| Victoria BC
| Yes
| https://dl.dropboxusercontent.com/u/7968133/Webmaker%20-%20aug%2011%20maker%20party%20update.pdf
| https://dl.dropboxusercontent.com/u/7968133/Webmaker%20-%20aug%2011%20maker%20party%20update.pdf
|-

|}

= Roundtable =

Do you have a question about a Mozilla Project or initiative? Let us know by Friday- we'll do our best to get you an answer.

Please note that we may not always be able to get to every item on this list, but we will try!

{| class="fullwidth-table"
|-
! Who are you?
! Area of question
! Question
|-
| ''What's your name? What do you work on?''
| ''Is your question about policy, a product, a Foundation initiative, etc.''
| ''What would you like to know?''

|-
|}

= Welcome! =

Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.

== Introducing New Volunteers ==
{| class="fullwidth-table"
|-
! New Volunteer(s)
! Introduced by
! Speaker location
! New Volunteer location
! Will be working on
|-
| ''Who is the new volunteer(s)?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where is the new person based?''
| ''What will the new person be doing?''
|-

|-
|}

== Introducing New Hires ==
{| class="fullwidth-table"
|-
! New Hire
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new hire?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-

|-
|}

== Introducing New Interns ==
{| class="fullwidth-table"
|-
! New Intern
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new intern?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-

|-
| Mihai Tabără
| Rail Aliiev
| Mountain View
| San Francisco
| Release Engineering
|-
| Tomasz Kołodziejski
| Drew Willcoxon
| Mountain View
| Mountain View
| FFX Engineering
|-
|}

= <meta> =

Notes and non-voice status updates that aren't part of the live meeting go here.

== Status Updates By Team (*non-voice* updates) ==

=== Firefox ===

=== Platform ===

=== Cloud Services ===

=== Messaging ===

=== Mobile ===

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== WebQA ====

==== QA Community ====

=== Automation & Tools ===
==== bugzilla.mozilla.org ====
Notable changes to [https://bugzilla.mozilla.org/ bugzilla.mozilla.org] during the last week:
* {{bug|938272}} The "User Story" field is now visible on all products
[[BMO/Recent_Changes|All changes]].

=== Security ===

=== Engagement ===

* [https://docs.google.com/a/mozilla.com/spreadsheets/d/1X5kUBkEAicEe2unDaaLGTYzAJbphWFoaJYBTasHrcHQ/edit#gid=1764494528 Engagement's Active Project Dashboard]

==== PR ====

==== Events ====

==== Social Support ====

WeeklyUpdates/2014-08-11

2014-08-11T17:31:37Z

Brett Gaylor:

{{WeeklyUpdateNav}}
{{conf|8600}}

__TOC__

= All-hands Status Meeting Agenda =

Items in this section will be shared during the live all-hand status meeting.

== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==
* Interns Anhad Singh and Ian Connolly, for working to open up Release Engineering. Ian and Anhad have been creating useful [[ReleaseEngineering/Contribute|wiki content for contributors]], getting Release Engineering on [http://whatcanidoformozilla.org/ http://whatcanidoformozilla.org/] and [http://www.joshmatthews.net/bugsahoy http://www.joshmatthews.net/bugsahoy] and putting useful whiteboard tags in bugs. Also, new Release Engineering contributors Sergio Butero and Harsimran Singh, who made their first contributions as a result of Anhad and Ian's efforts!

* Luis Antonio Sánchez Romero from Mexico has been helping us test Payments in Mexico by acquiring local SIMs and running tests for us. Payments team thanks him for all his efforts!

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===
* The latest edition of [https://wiki.mozilla.org/Engagement/Developer_Engagement/DevPulse DevPulse] is [https://wiki.mozilla.org/Engagement/Developer_Engagement/DevPulse/August2014 up] - have a read and see how you can get involved with Mozillians supporting developers worldwide!

* Join us at [http://www.worldtimebuddy.com/?qm=1&lid=1850147,5375480,2643743,1277333&h=5375480&date=2014-8-11&sln=14-14.5 2pm Pacific] for the bi-weekly [https://wiki.mozilla.org/Marketplace/Community/Meetings Marketplace community meeting]. This week, we'll talk about the new proposed format for Marketplace contributions, and a new community curation program for the feed feature.

=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===

=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===
'''Mozillians Town Hall - Get Firefox on a Growth Trajectory'''
* Time: 10:00am - 11:00am
* Air Mozilla: https://air.mozilla.org/mozillians-town-hall-2014-goals-getting-firefox-on-a-growth-trajectory/
* Questions: https://moderator.paas.allizom.org/e/town-hall-2014-goals-firefox-13-aug
'''Intern Presentations'''
* 1:00- Susanna Bowen, "Improving Support for CSS Ruby" SF
* 1:30- Jonathan Morton, "WebGL in Web Workers" SF
* 2:00- Julian Hector, "IPC, supervisor and FirefoxOS" SF
* 2:30- James Hobin, "A Cake Filled With Rainbows, Smiles, and JavaScript" SF
'''js13kGames 2014 Competition'''
* JavaScript coding competition for HTML5 game developers that takes place online Aug 13 through Sept 13
* Run by Mozillian Andrzej "Captain Rogers" Mazur, Mozillian Jason Weathersby is a competition judge
* [http://js13kgames.com/ Competition homepage]

=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===
'''Intern Presentations'''
* 1:00- Guptha Rajagopal, "SpiderMonkey - More Strings, More Class" MV
* 1:30- Jeremy Poulin, "Predictor: Because Witches Are Scary" MV
* 2:00- Sathyanarayanan Gunasekaran, "Games, games and more games" MV
* 2:30- Basar Koc, "Ringing Artifacts in Data Compression" MV

=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===
* [[Webdev/Beer_And_Tell/August2014|Webdev Beer and Tell]] - 2PM Pacific in the Webdev vidyo room
** Web developers across the project show off their side projects. Open to the public! (Airmo link will be on the wiki page)

=== Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===
* [http://opennews.org/fellowships/apply.html Application to apply] to become a 2015 Knight-Mozilla Fellow closes at MIDNIGHT eastern!

=== Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===

=== Next Week ===
* Mozillians Town Hall - Disrupting the Advertising Industry
** More information coming soon

== Project Status Updates (voice updates) ==

=== Firefox ===
* Johnathan Nightingale - Toronto

=== Firefox OS ===

* Li Gong from London (Vidyo)

=== Cloud Services ===
''Speaker Location:''

=== Content Services ===

* Darren Herman / Sean Bohan - NYC Office
* Tiles - We are NOT doing a Brown Bag this week, but we have scheduled a Town Hall discussion next Monday Aug 18
* Subscribe2Web - updating the wiki this week and scheduling a Brown Bag session for the week of August 25
* UP - The User Personalization team is working on introducing personalization to Firefox users, starting with data transparency. We are planning on surfacing this through the Personal Interest Dashboard (working name). This will be initially released as an add-on with the objective of providing the user the ability to 1) analyze their categorized interests based on their history and 2) discover new content that's related to their interests

=== Webmaker ===
''Speaker Location: Brett Gaylor, remote''
* We're just about half way through with Maker Party and we have over 1200 events in 261 cities, with an estimated 62,000 attendees!
* We passed a significant milestone - 5000 contributors to Mozilla Foundation activities!

=== Knight-Mozilla OpenNews ===
''Speaker Location: Dan Sinker, remote''
* The application to apply to become a 2015 Knight-Mozilla Fellow closes THIS Saturday at midnight!
** application form: http://opennews.org/fellowships/apply.html
* Fellowships offer creative coders an opportunity to be embedded in newsrooms around the world, working in the open and solving complex problems.
** [http://dansinker.com/post/93888022860/opennews-2015partners our host newsrooms make their pitch]
* The Knight-Mozilla Fellowship is also about community-building and, well, fellowship.
** [http://dansinker.com/post/93906688160/opennews-so-what-is-the-fellowship-experience-like our current fellows talk about their experiences]
* You (yes you!) know great people that should apply. Send them our way!
** example tweets, program description for copy/pasting, and more: https://etherpad.mozilla.org/opennews-fellowships-share

=== Mozilla Communities ===
''Speaker Location:''

=== Marketplace ===
* Non verbal.
* We are trying out a new development environment for the Marketplace using Docker. If you'd like to try it out [https://etherpad.mozilla.org/mkt-docker-dev-env-instructions instructions are here].
* We are also looking for app developers who'd like to try out the [https://wiki.mozilla.org/Marketplace/InAppPayments new hosted in-app payment system] and give us feedback.

== Speakers ==

The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week.

{| class="fullwidth-table"
|-
! [https://mozillians.org/u/USERNAME Presenter]
! Title
! Topic
! Location
! Share?
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, other info)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
| Tyler Downer
| Project Manager, User Advocacy Team
| Firefox Updates Hotfix
| Home Office Vidyo
| No
| (https://docs.google.com/a/mozilla.com/presentation/d/15ehWmUsyzzMWcOnuvwr0N5KXKBw36HEXCLWgNlhLD54/edit?usp=sharing)
| https://blog.mozilla.org/useradvocacy/2014/07/30/helping-our-users-experience-the-modern-web/
|-
| Mary Ellen Muckerman
| Brand (Engagement)
| Two new initiatives (Voices + Mozilla identity)
| San Francisco
| No
| No
|
|-
| Anthony Duignan-Cabrera
| Editor in Chief, Mozilla Voices
| Mozilla Voices
| NYC Office
| No
| No
| https://wiki.mozilla.org/Mozilla_Voices
|-
| Sean Martell
| Art Director
| Mozilla identity
| Toronto Office
| No
| No
|
|-
| Karen Ward
| Senior Project Manager, Operator Launch Team
| FxOS Launch Roadmap (Operators and Retail/Open Market devices)
| Home Office Vidyo
| No
| https://mana.mozilla.org/wiki/display/PM/Firefox+OS+Wave+Launch+Cross+Functional+View
| https://mana.mozilla.org/wiki/display/PM/Firefox+OS+Wave+Launch+Cross+Functional+View
|-

| Jorge Villalobos
| Add-ons Developer Relations Lead
| Add-on Compatibility
| Home Office Vidyo
| No
| [https://slidebean.com/p/5jiyNzH68e/How-we-manage-Add-on-Compatibility Slides]
| [https://blog.mozilla.org/addons/ Add-ons Blog]
|-

|-
| Brett Gaylor
| VP, Webmaker
| Webmaker - the party is getting out of control
| Victoria BC
| Yes
|
|
|-

|}

= Roundtable =

Do you have a question about a Mozilla Project or initiative? Let us know by Friday- we'll do our best to get you an answer.

Please note that we may not always be able to get to every item on this list, but we will try!

{| class="fullwidth-table"
|-
! Who are you?
! Area of question
! Question
|-
| ''What's your name? What do you work on?''
| ''Is your question about policy, a product, a Foundation initiative, etc.''
| ''What would you like to know?''

|-
|}

= Welcome! =

Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.

== Introducing New Volunteers ==
{| class="fullwidth-table"
|-
! New Volunteer(s)
! Introduced by
! Speaker location
! New Volunteer location
! Will be working on
|-
| ''Who is the new volunteer(s)?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where is the new person based?''
| ''What will the new person be doing?''
|-

|-
|}

== Introducing New Hires ==
{| class="fullwidth-table"
|-
! New Hire
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new hire?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-

|-
|}

== Introducing New Interns ==
{| class="fullwidth-table"
|-
! New Intern
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new intern?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-

|-
| Mihai Tabără
| Rail Aliiev
| Mountain View
| San Francisco
| Release Engineering
|-
| Tomasz Kołodziejski
| Drew Willcoxon
| Mountain View
| Mountain View
| FFX Engineering
|-
|}

= <meta> =

Notes and non-voice status updates that aren't part of the live meeting go here.

== Status Updates By Team (*non-voice* updates) ==

=== Firefox ===

=== Platform ===

=== Cloud Services ===

=== Messaging ===

=== Mobile ===

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== WebQA ====

==== QA Community ====

=== Automation & Tools ===
==== bugzilla.mozilla.org ====
Notable changes to [https://bugzilla.mozilla.org/ bugzilla.mozilla.org] during the last week:
* {{bug|938272}} The "User Story" field is now visible on all products
[[BMO/Recent_Changes|All changes]].

=== Security ===

=== Engagement ===

* [https://docs.google.com/a/mozilla.com/spreadsheets/d/1X5kUBkEAicEe2unDaaLGTYzAJbphWFoaJYBTasHrcHQ/edit#gid=1764494528 Engagement's Active Project Dashboard]

==== PR ====

==== Events ====

==== Social Support ====

Webmaker/moduleRFC

2014-06-12T23:44:51Z

Brett Gaylor:

{{Module
|name=Webmaker
|description=Tools, Curriculum and Community to teach the world the web
|owner=Brett Gaylor
|peers=Michelle Thorne, David Humphrey, Chris Lawrence, David Ascher, Cassie McDaniel, Jon Buckley, Kate Hudson
|url=http://wiki.mozilla.org/Webmaker
|bugzilla product=Webmaker
}}

=== Submodules of Webmaker ===
{{Module
|name=Webmaker.org
|description=Primary user experience for Webmaker; Landing pages, user profiles, identity system, login
|owner=Cassie McDaniel
|peers=Kate Hudson
|group=
|source_dirs=
|url=
|components=
}}

{{Module
|name=Webmaker Tools
|description=Publishing tools that encourage users to create the web
|owner=Simon Wex
|peers=Michael Kammermans, Scott Downe, Bobby Richter, Luke Pacholski
|group=
|source_dirs=
|url=
|components=
}}

{{Module
|name=Software architecture
|description=API Design, frameworks
|owner=Simon Wex
|peers=David Humphrey
|group=
|source_dirs=
|url=
|components=
}}

{{Module
|name=User Experience + Brand
|description=The user's experience and expectations of Webmaker
|owner=Cassie McDaniel
|peers=
|group=
|source_dirs=
|url=
|components=
}}

{{Module
|name=Webmaker Curriculum
|description=Content for teachers and learners
|owner=Chris Lawrence
|peers=
|group=
|source_dirs=
|url=
|components=
}}

{{Module
|name=Webmaker Mentor program
|description=Webmaker's contributor engine and grassroots membership program
|owner=Michelle Thorne
|peers=
|group=
|source_dirs=
|url=
|components=
}}

{{Module
|name=Web Literacy Map
|description=
|owner=Doug Belshaw
|peers=
|group=
|source_dirs=
|url=
|components=
}}

Webmaker/moduleRFC

2014-06-12T00:20:38Z

Brett Gaylor:

{{Module
|name=Webmaker
|description=Tools, Curriculum and Community to teach the world the web
|owner=Brett Gaylor
|peers=Michelle Thorne, David Humphrey, Chris Lawrence, David Ascher, Cassie McDaniel, Jon Buckley, Kate Hudson
|url=http://wiki.mozilla.org/Webmaker
|bugzilla product=Webmaker
}}

=== Submodules of Webmaker ===
{{Module
|name=Webmaker.org
|description=Primary user experience for Webmaker; Landing pages, user profiles, identity system, login
|owner=Cassie McDaniel
|peers=Kate Hudson
|group=
|source_dirs=
|url=
|components=
}}

{{Module
|name=Webmaker Tools
|description=Publishing tools that encourage users to create the web
|owner=Simon Wex
|peers=Michael Kammermans, Scott Downe, Bobby Richter, Luke Pacholski
|group=
|source_dirs=
|url=
|components=
}}

{{Module
|name=Webmaker Curriculum
|description=Content for teachers and learners
|owner=Chris Lawrence
|peers=Jess Klein, Atul Varma
|group=
|source_dirs=
|url=
|components=
}}

{{Module
|name=Webmaker Mentor program
|description=Webmaker's contributor engine and grassroots
|owner=Michelle Thorne
|peers=Laura Hilliger, Doug Belshaw
|group=
|source_dirs=
|url=
|components=
}}

Webmaker/moduleRFC

2014-06-12T00:20:13Z

Brett Gaylor: Created page with " {{Module |name=Webmaker |description=Tools, Curriculum and Community to teach the world the web |owner=Brett Gaylor |peers=Michelle Thorne, David Humphrey, Chris Lawrence, Da..."

{{Module
|name=Webmaker
|description=Tools, Curriculum and Community to teach the world the web
|owner=Brett Gaylor
|peers=Michelle Thorne, David Humphrey, Chris Lawrence, David Ascher, Cassie McDaniel, Jon Buckley, Kate Hudson
|url=http://wiki.mozilla.org/Webmaker
|bugzilla product=Webmaker
}}

=== Submodules of Webmaker ===
{{Module
|name=Webmaker.org
|description=Primary user experience for Webmaker; Landing pages, user profiles, identity system, login
|owner=Cassie McDaniel
|peers=Kate Hudson
|group=
|source_dirs=
|url=
|components=
}}

{{Module
|name=Webmaker Tools
|description=Publishing tools that encourage users to create the web
|owner=Simon Wex
|peers=Michael Kammermans, Scott Downe, Bobby Richter, Luke Pacholski
|group=
|source_dirs=
|url=
|components=
}}

{{Module
|name=Webmaker Curriculum
|description=Content for teachers and learners
|owner=Chris Lawrence
|peers=Jess Klein, Atul Varma
|group=
|source_dirs=
|url=
|components=
}}

{{Module
|name=Webmaker Mentor program
|description=Webmaker's contributor engine and grassroots
|owner=Michelle Thorne
|peers=Laura Hilliger, Doug Belshaw
|group=
|source_dirs=
|url=
|components=
}}

Webmaker/Textbook

2014-05-08T20:02:46Z

Brett Gaylor:

__NOTOC__
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/v0h9d5rl.png
=Toward Web Lit Textbook 1.0=
* '''Schedule & Logistics''': https://etherpad.mozilla.org/book-sprint

==Links==
* '''Notes''': https://etherpad.mozilla.org/Textbook

'''Prototypes'''
* '''Sample page copy''': The "Credibility" page. 2nd draft copy: https://etherpad.mozilla.org/credibility
* Webmaker.org "Explore" prototype: https://webmaker.mofostaging.net/explore

'''Good sources for activities and kits'''
* Web Lit Mapper. A good source of resources and activities, tagged by competency http://weblitmapper.webmakerprototypes.org/
* Top 100 resources (many are outside OERs). http://mzl.la/top100
* "Best in Show" -- our most updated list of OERs/Kits per competency. https://teach.etherpad.mozilla.org/best-in-show
* Teaching Kit production queue. Kits in progress. Burn down list: http://mzl.la/kit_list

'''Documentation'''
* "How to create a good teaching kit." Documentation on SUMO [link] (needs to be updated, using copy here https://wiki.mozilla.org/Webmaker/Teaching_Kits and the SUMO page)
* Style guide for writing these pages. Starting a draft here: https://etherpad.mozilla.org/style_guide
* Community engagement plan. https://teach.etherpad.mozilla.org/featureseries
* Quarterly Curation Sprint Plan https://etherpad.mozilla.org/style-guide-editorial

Experimental:
** '''Kit Builder'''. Fuzzy's new [http://fuzzyfox.github.io/webmaker-kits-builder kit builder prototype] + [https://fuzzyfox.github.io/webmaker-kits-builder/README.md documentation]
** '''Gallery Maker.''' aka Cade's "makeLister." New tool for creating Webmaker.org galleries. [https://bugzilla.mozilla.org/show_bug.cgi?id=1005905 Blocked on this]
** '''Web Lit Map visual redesign ideas '''[https://www.dropbox.com/s/kzl0xa0rj3yoe1c/webliteracymap_sngconcepts.pdf A few basic sketches from Sabrina ]

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/qur82k-2.png

= Competency Page directory=
*[https://etherpad.mozilla.org/composing Composing]
*[https://etherpad.mozilla.org/codingscripting Coding/Scripting]
*[https://etherpad.mozilla.org/remix Remix]
*[https://etherpad.mozilla.org/credibility Credibility]
*[https://etherpad.mozilla.org/Collaborating Collaborating]
*[https://etherpad.mozilla.org/security Security]
*[https://etherpad.mozilla.org/privacy Privacy]
*[https://etherpad.mozilla.org/search Search]
*[https://etherpad.mozilla.org/navigation Navigation]
*[https://etherpad.mozilla.org/webmechanics Web Mechanics]
* [http://etherpad.mozilla.org/designaccessibility Design and Accessibility]
* [https://etherpad.mozilla.org/infrastructure Infrastructure]

=Sprint=
===Wed Morning===
* '''GOAL: ship a mock-up of the "Credibility" page'''. To model and discuss Wed. Show how a new template could work for the page. Experiment with look and feel, etc.
* '''[http://mzl.la/1fMCbXj Ticket Tag]''': [wedam]
<div>
<onlyinclude>
<bugzilla>
{
"product": "Webmaker",
"whiteboard": "[wedam]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "last_change_time"
}
</bugzilla>
</onlyinclude>
</div>

===Wed Afternoon===
* '''GOAL: get started on three high-priority pages together''': Privacy, Remix, Coding & Scripting.
* '''Who's focusing on what?''' (please hack)
** '''Cassie''': design. icons + make the new pages layout look awesome.
** '''Kate''': design, coding. Technical review where needed
** '''Kat & Drushka''': review "staff pick" teaching kits for each page. Ensure the titles are clear.
** '''Brett''': Remix. Draft a team to draft the "remix" page.
** '''Matt / Claw:''' divide up privacy + coding & scripting.
** '''Humph''': joining Thurs & Fri. Question: Humph, where do you want to focus?
** '''Ali''': Localization / Translation

* '''Tag''': [wed] [aft]
<div>
<onlyinclude>
<bugzilla>
{
"product": "Webmaker",
"whiteboard": "[wed] [aft]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</onlyinclude>
</div>

===Thursday===
* '''GOAL: ship three more pages'''. To be decided together.
* [http://mzl.la/1iTNz4w '''Tag''']: [thurs]
<div>
<onlyinclude>
<bugzilla>
{
"product": "Webmaker",
"whiteboard": "[thurs]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "last_change_time"
}
</bugzilla>
</onlyinclude>
</div>

===Friday===
* '''GOAL: ship how many more?'''. Plus: ship a draft style guide. Documenting best practices we learned from working together over the week.
* '''[http://mzl.la/1kHDUtn Tag]''': [fri]
<div>
<onlyinclude>
<bugzilla>
{
"product": "Webmaker",
"whiteboard": "[fri]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "last_change_time"
}
</bugzilla>
</onlyinclude>
</div>
[https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&list_id=10102809&o1=substring&query_format=advanced&component=Teaching%20Kits%20%2F%20Curriculum&product=Webmaker All Webmaker curriculum tickets]
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/hirpw_mt.png

Webmaker/Textbook

2014-05-08T18:18:51Z

Brett Gaylor:

__NOTOC__
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/v0h9d5rl.png
=Toward Web Lit Textbook 1.0=
* '''Schedule & Logistics''': https://etherpad.mozilla.org/book-sprint

==Links==
* '''Notes''': https://etherpad.mozilla.org/Textbook

'''Prototypes'''
* '''Sample page copy''': The "Credibility" page. 2nd draft copy: https://etherpad.mozilla.org/credibility
* Webmaker.org "Explore" prototype: https://webmaker.mofostaging.net/explore

'''Good sources for activities and kits'''
* Web Lit Mapper. A good source of resources and activities, tagged by competency http://weblitmapper.webmakerprototypes.org/
* Top 100 resources (many are outside OERs). http://mzl.la/top100
* "Best in Show" -- our most updated list of OERs/Kits per competency. https://teach.etherpad.mozilla.org/best-in-show
* Teaching Kit production queue. Kits in progress. Burn down list: http://mzl.la/kit_list

'''Documentation'''
* "How to create a good teaching kit." Documentation on SUMO [link] (needs to be updated, using copy here https://wiki.mozilla.org/Webmaker/Teaching_Kits and the SUMO page)
* Style guide for writing these pages. Starting a draft here: https://etherpad.mozilla.org/style_guide
* Community engagement plan. https://teach.etherpad.mozilla.org/featureseries
* Quarterly Curation Sprint Plan https://etherpad.mozilla.org/style-guide-editorial

Experimental:
** '''Kit Builder'''. Fuzzy's new [http://fuzzyfox.github.io/webmaker-kits-builder kit builder prototype] + [https://fuzzyfox.github.io/webmaker-kits-builder/README.md documentation]
** '''Gallery Maker.''' aka Cade's "makeLister." New tool for creating Webmaker.org galleries. [https://bugzilla.mozilla.org/show_bug.cgi?id=1005905 Blocked on this]
** '''Web Lit Map visual redesign ideas '''[https://www.dropbox.com/s/kzl0xa0rj3yoe1c/webliteracymap_sngconcepts.pdf A few basic sketches from Sabrina ]

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/qur82k-2.png

= Competency Page directory=
*[https://etherpad.mozilla.org/composing Composing]
*[https://etherpad.mozilla.org/codingscripting Coding/Scripting]
*[https://etherpad.mozilla.org/remix Remix]
*[https://etherpad.mozilla.org/credibility Credibility]
*[https://etherpad.mozilla.org/Collaborating Collaborating]
*[https://etherpad.mozilla.org/security Security]
*[https://etherpad.mozilla.org/privacy Privacy]
*[https://etherpad.mozilla.org/search Search]
*[https://etherpad.mozilla.org/navigation Navigation]
*[https://etherpad.mozilla.org/webmechanics Web Mechanics]
* [http://etherpad.mozilla.org/designaccessibility Design and Accessibility]

=Sprint=
===Wed Morning===
* '''GOAL: ship a mock-up of the "Credibility" page'''. To model and discuss Wed. Show how a new template could work for the page. Experiment with look and feel, etc.
* '''[http://mzl.la/1fMCbXj Ticket Tag]''': [wedam]
<div>
<onlyinclude>
<bugzilla>
{
"product": "Webmaker",
"whiteboard": "[wedam]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "last_change_time"
}
</bugzilla>
</onlyinclude>
</div>

===Wed Afternoon===
* '''GOAL: get started on three high-priority pages together''': Privacy, Remix, Coding & Scripting.
* '''Who's focusing on what?''' (please hack)
** '''Cassie''': design. icons + make the new pages layout look awesome.
** '''Kate''': design, coding. Technical review where needed
** '''Kat & Drushka''': review "staff pick" teaching kits for each page. Ensure the titles are clear.
** '''Brett''': Remix. Draft a team to draft the "remix" page.
** '''Matt / Claw:''' divide up privacy + coding & scripting.
** '''Humph''': joining Thurs & Fri. Question: Humph, where do you want to focus?
** '''Ali''': Localization / Translation

* '''Tag''': [wed] [aft]
<div>
<onlyinclude>
<bugzilla>
{
"product": "Webmaker",
"whiteboard": "[wed] [aft]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</onlyinclude>
</div>

===Thursday===
* '''GOAL: ship three more pages'''. To be decided together.
* [http://mzl.la/1iTNz4w '''Tag''']: [thurs]
<div>
<onlyinclude>
<bugzilla>
{
"product": "Webmaker",
"whiteboard": "[thurs]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "last_change_time"
}
</bugzilla>
</onlyinclude>
</div>

===Friday===
* '''GOAL: ship how many more?'''. Plus: ship a draft style guide. Documenting best practices we learned from working together over the week.
* '''[http://mzl.la/1kHDUtn Tag]''': [fri]
<div>
<onlyinclude>
<bugzilla>
{
"product": "Webmaker",
"whiteboard": "[fri]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "last_change_time"
}
</bugzilla>
</onlyinclude>
</div>
[https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&list_id=10102809&o1=substring&query_format=advanced&component=Teaching%20Kits%20%2F%20Curriculum&product=Webmaker All Webmaker curriculum tickets]
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/hirpw_mt.png

Webmaker/Textbook

2014-05-08T15:26:04Z

Brett Gaylor: /* Competency Page directory */

__NOTOC__
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/v0h9d5rl.png
=Toward Web Lit Textbook 1.0=
* '''Schedule & Logistics''': https://etherpad.mozilla.org/book-sprint

==Links==
* '''Notes''': https://etherpad.mozilla.org/Textbook

'''Prototypes'''
* '''Sample page copy''': The "Credibility" page. 2nd draft copy: https://etherpad.mozilla.org/credibility
* Webmaker.org "Explore" prototype: https://webmaker.mofostaging.net/explore

'''Good sources for activities and kits'''
* Web Lit Mapper. A good source of resources and activities, tagged by competency http://weblitmapper.webmakerprototypes.org/
* Top 100 resources (many are outside OERs). http://mzl.la/top100
* "Best in Show" -- our most updated list of OERs/Kits per competency. https://teach.etherpad.mozilla.org/best-in-show
* Teaching Kit production queue. Kits in progress. Burn down list: http://mzl.la/kit_list

'''Documentation'''
* "How to create a good teaching kit." Documentation on SUMO [link] (needs to be updated, using copy here https://wiki.mozilla.org/Webmaker/Teaching_Kits and the SUMO page)
* Style guide for writing these pages. Starting a draft here: https://etherpad.mozilla.org/style_guide
* Community engagement plan. https://teach.etherpad.mozilla.org/featureseries
* Quarterly Curation Sprint Plan https://etherpad.mozilla.org/style-guide-editorial

Experimental:
** '''Kit Builder'''. Fuzzy's new [http://fuzzyfox.github.io/webmaker-kits-builder kit builder prototype] + [https://fuzzyfox.github.io/webmaker-kits-builder/README.md documentation]
** '''Gallery Maker.''' aka Cade's "makeLister." New tool for creating Webmaker.org galleries. [https://bugzilla.mozilla.org/show_bug.cgi?id=1005905 Blocked on this]
** '''Web Lit Map visual redesign ideas '''[https://www.dropbox.com/s/kzl0xa0rj3yoe1c/webliteracymap_sngconcepts.pdf A few basic sketches from Sabrina ]

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/qur82k-2.png

= Competency Page directory=
*[https://etherpad.mozilla.org/composing Composing]
*[https://etherpad.mozilla.org/codingscripting Coding/Scripting]
*[https://etherpad.mozilla.org/remix Remix]
*[https://etherpad.mozilla.org/credibility Credibility]
*[https://etherpad.mozilla.org/Collaborating Collaborating]
*[https://etherpad.mozilla.org/security Security]
*[https://etherpad.mozilla.org/privacy Privacy]
*[https://etherpad.mozilla.org/search Search]
*[https://etherpad.mozilla.org/navigation Navigation]
*[https://etherpad.mozilla.org/webmechanics Web Mechanics]

=Sprint=
===Wed Morning===
* '''GOAL: ship a mock-up of the "Credibility" page'''. To model and discuss Wed. Show how a new template could work for the page. Experiment with look and feel, etc.
* '''[http://mzl.la/1fMCbXj Ticket Tag]''': [wedam]
<div>
<onlyinclude>
<bugzilla>
{
"product": "Webmaker",
"whiteboard": "[wedam]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "last_change_time"
}
</bugzilla>
</onlyinclude>
</div>

===Wed Afternoon===
* '''GOAL: get started on three high-priority pages together''': Privacy, Remix, Coding & Scripting.
* '''Who's focusing on what?''' (please hack)
** '''Cassie''': design. icons + make the new pages layout look awesome.
** '''Kate''': design, coding. Technical review where needed
** '''Kat & Drushka''': review "staff pick" teaching kits for each page. Ensure the titles are clear.
** '''Brett''': Remix. Draft a team to draft the "remix" page.
** '''Matt / Claw:''' divide up privacy + coding & scripting.
** '''Humph''': joining Thurs & Fri. Question: Humph, where do you want to focus?
** '''Ali''': Localization / Translation

* '''Tag''': [wed] [aft]
<div>
<onlyinclude>
<bugzilla>
{
"product": "Webmaker",
"whiteboard": "[wed] [aft]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</onlyinclude>
</div>

===Thursday===
* '''GOAL: ship three more pages'''. To be decided together.
* [http://mzl.la/1iTNz4w '''Tag''']: [thurs]
<div>
<onlyinclude>
<bugzilla>
{
"product": "Webmaker",
"whiteboard": "[thurs]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "last_change_time"
}
</bugzilla>
</onlyinclude>
</div>

===Friday===
* '''GOAL: ship how many more?'''. Plus: ship a draft style guide. Documenting best practices we learned from working together over the week.
* '''[http://mzl.la/1kHDUtn Tag]''': [fri]
<div>
<onlyinclude>
<bugzilla>
{
"product": "Webmaker",
"whiteboard": "[fri]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "last_change_time"
}
</bugzilla>
</onlyinclude>
</div>
[https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&list_id=10102809&o1=substring&query_format=advanced&component=Teaching%20Kits%20%2F%20Curriculum&product=Webmaker All Webmaker curriculum tickets]
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/hirpw_mt.png

AllHands

2014-04-30T07:44:37Z

Brett Gaylor:

[[File:AllHandsRise.png|600px]]
=MoFo 2014 All Hands=
* '''Schedule''' https://etherpad.mozilla.org/allhands2014schedule
* '''Logistics''' https://etherpad.mozilla.org/All-Hands-logistics
* '''Story''' https://wiki.mozilla.org/AllHands/Story
* '''Demos''' https://etherpad.mozilla.org/All-Hands-demos
* '''MoCos''' https://etherpad.mozilla.org/MoCo-MoFo
* '''Done''' https://wiki.mozilla.org/AllHands/Done
* '''Hashtags''' [https://twitter.com/search?f=realtime&q=%23mozhelp&src=typd #mozhelp] [https://twitter.com/search?f=realtime&q=%23mofo10k&src=typd #mofo10k]

=[https://wiki.mozilla.org/AllHands/Workshops Workshops and Demos]=
[[File:Workshops.png|200px|left]] 

=Scrum=
==Tues==
===DevOps: Making it easier to make===
When: All day, every day 
Goal:  Increase efficiency, safety, and ease of pushing code. MoFo point: JP  
Bugzilla tags: [allhands][metrics]
<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"whiteboard": "[allhands][devops]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>

===Contributor Metrics: connecting the threads===
When: Tues 10:00-12:00 (this scheduled time is a moco/mofo catch-up meeting) 
Goal:  Connecting the strands so we're heading in the same direction. Face-to-face discussions about Baloo, and BI Datawarehouse tools; Tableau server and dashboards; MoFo Interim Contributor Dashboard and; the systems; behind it; + the Adhoc contribution logger.  MoFo point: Adam and Jbuck  SF Moco contacts:  David Boswell  Local Moco, but not SF: Anurag Phadke (Mountain View),  Collaborators: Chris D 
Bugzilla tags: [allhands][metrics]
<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"whiteboard": "[allhands][metrics]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>

===Going Global: Three new markets for Webmaker in 2014===
When: Tues (anytime) 
 What they need from us and how we'll win. We have funded partnerships planned in Bangladesh, Brazil and more. Let's focus on where we are funded and do it well. Show where geographically anchored / regional funding is; talk about creating more visibility  about the data we have; leverage planned Maker Parties in these key locales; finalise the first draft of an exemplary teaching kit that activates these commuinties, and measure where in the world Mozilla can make the most impact. Lead: Ben Moskowitz; Adam Lofting Collaborators: Kat, Karen, Michelle, Chris, Geoff, An-Me, Amira 
[http://mzl.la/1hASFMO Tag]: [allhands][global]
<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"whiteboard": "[allhands][global]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>
 

===Landing the badges moonshot: Webmaker + Badgekit sprint===
* Anytime
*'''Lead''': Kate
*'''Collaborators''': An Me, Erik, Andrew, JP, Jbuck
*'''Goal: We will issue the Webmaker Super Mentor badge'''. We're a few short tickets away from being able to issue and approve Webmaker badges in Badgekit. Let's sprint towards completion.
*'''Deliverable''': Ship the Webmaker Super Mentor Badge, supporting the complete end-to-end user story: see, apply, review, issue, receive.
*'''Webmaker badges roadmap:''' [[Webmaker/Badges#Q2_Roadmap|Q2 Roadmap]]
*'''Bugzilla tags''': webmakerbadges, followup, [allhands]

<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"product": "webmaker",
"whiteboard": "webmakerbadges, followup",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>

===Getting real about press and marketing: Press Kits===
When: Tues 10:00-12:00 
Goal:  Creating press kits for MoFo produtcs. 
MoFo point: Erica S. and Lainie 
etherpad:https://mofocomms.etherpad.mozilla.org/presskits 
Bugzilla tags: [allhands][presskits]
<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"whiteboard": "[allhands][press][presskits]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>

===Events: converting event participants into users and contributors===
 How do we turn Webmaker and Maker Party event participants into users, supporters and contributors? This is one of the most important things we can do towards our 10k contributor goal this year. And it's hard. It will take a cross-team approach with engineers, community team and partnership teams working together. Let's get the key stakeholders together to agree on strategy and document a cross-team sprint together here:  https://wiki.mozilla.org/Webmaker/Events Lead: Brett + Matt Required: Brett, Matt, Amira, Gavin, Cassie Requested: Michelle, Kate Hudson, Lainie Context and reading: https://etherpad.mozilla.org/Events Notes: https://etherpad.mozilla.org/events-allhands 
Tag: [allhands][events] 
When: Anytime 
'''Deliverable''': Get consensus with stakeholders. Then document our events roadmap. https://etherpad.mozilla.org/Events https://wiki.mozilla.org/Webmaker/Events
<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"whiteboard": "[allhands][events]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>

===Documentation and process: How we support our engagement work ===
Time: Tuesday morning 
Lead: Erika Owens, Leah Gilliam Collaborators: Local SF contact: GoalWe're all doing a lot of great work. How do we document it and share our learnings within our teams, between our projects, with our stakeholders, and beyond? Thinking through the followthrough and documentation process is also critical in keeping contributors engaged. Let's sketch out some of the key elements of documentation and follow-through and share tactics about how to make sure it actually happens.

Etherpad: https://etherpad.mozilla.org/allhands2014-community-docs We're going to loop back with Matt's working MoFo session. '''Length''':? 
'''Tags''': [allhands][newcommunities][documentation]
<div style="align:left;">
<bugzilla>
{
"whiteboard": "[allhands][newcommunities][documentation]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>

===Maker Party: Driving Mozilla-wide participation ===
 From Open News to the Science Lab and beyond, let's make sure this year's Maker Party includes all areas of MoFo. This can also include how to leverage upcoming MozCamps, plus  Mozilla's new "gathering plan" for distributed events. Let's also pick a few likely MoCo groups and document with them what they might do as well.  Lead: Amira/Michelle Collaborators: Winston, WPR folks for Mozilla-spaces events 
[http://mzl.la/PEbrMr Tag]: [allhands][mozmakerparty] 
When: Tuesday afternoon. Talk to Winston & WPR separately 
<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"whiteboard": "[allhands] [mozmakerparty]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>

=== Webmaker Training: Get ready to level up 5K+ contributors ===
'''Webmaker Training will reach thousands of mentors on its first iteration on May 12.''' Let's polish the content and lock in the comms needed to "feed the funnel" for Maker Party. This includes reviewing the modules, freshening the site, and inviting the Super Mentors and participants. 
'''Lead''': Laura 
'''Collaborators''': Lainie, Mozilla Reps, Cassie, Jbuck, Michelle, William 
Tags: [allhands][training] 
When and where: Tuesday morning, community space 
<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"whiteboard": "[allhands][training]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>

=== Mozfest: Roadmap and Brainstorm ===
'''Mozfest is shipping its roadmap and key documentation. Also drop in to leave your dreams and ideas for this year.''' 
'''Lead''': Sarah, Misty, Michelle 
'''Collaborators''': Anyone who wants to drop in! 
Tags: [allhands] [mozfest] 
When and where: Tuesday afternoon, Foxhole open space 
<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"whiteboard": "[allhands] [mozfest]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>

===Ford Foundation The Web We Want Proposal===
* Anytime
*'''Lead''': Lynn
*'''Collaborators''': Dave S
*'''Goal: We will finish the proposal to the Ford Foundation
*'''Deliverable''': Ship the proposal to Ford Foundation.
*'''Bugzilla tags''' [allhands]

===Shipping a map of educational efforts across Mozilla===
* Tuesday afternoon
*'''Lead''': Kaitlin
*'''Collaborators''': Laura H, Brian
*'''Goal''': Map existing educational/training programs, create a resource making it clearer to communicate.
*'''Deliverable''': Craft a sketch / resource.
*'''Bugzilla tags''' [allhands][trainingmap]
<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"whiteboard": "[allhands][trainingmap]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>

==Wed==
 
===Hive Badges MVP: Determining the criteria of the Hive Community Member badge===
Time: 9:30 Wednesday
 At the Summit to Reconnect Learning in Redwood City this past February, we pledged to ship Hive badges by summer 2014. We'll be using the badges team planning sheet to organize our thoughts around an MVP badge that will look a lot like the Webmaker Mentor and Super Mentor badges, and will be issued via Webmaker.org this summer.
 Context: https://omnignorant.makes.org/thimble/hive-global-badges-update-march-24-2014
 Lead: Robert Friedman
 Collaborators: Leah, Kathryn, Kari, Lindsey, Sam, CLAW
 Etherpad: https://etherpad.mozilla.org/hivebadges2
 Deliverable: This, completed: https://docs.google.com/a/mozillafoundation.org/spreadsheets/d/1RqzHo1GXZeRiFGMQvntAQvuR2i76GaZsO87XkfZN0pk/edit
 Tags: [allhands] [Hive] [hivebadges]
 
<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"whiteboard": "[allhands] [Hive] [hivebadges]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>

===Fill the Funnel, MoFos. Shipping the Maker Party Marketing Plan===
Time: 9:30 Wednesday
 We ran a great, multi-channel marketing campaign around money: the EOY campaign. Now we need to do it about people. This session is an applied, tactical planning session for breaking our Maker Party marketing into defined assets, scheduled, and tasks. The Webmaker team has kicked ass and shipped a product. Now it's on us to get people to use it.
 Context: This, but for people: https://fundraising.mozilla.org/campaign-overview/ Lead: Geoffrey, Erica S, Hannah Collaborators: Amira, Erika D., Lainie, Andrea Deliverable: A detailed marketing plan and schedule, broken out across the bugs. 
Tags: [allhands] [Maker Party 2014] [MarketingPlan]
<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"whiteboard": "[Webmaker] [Maker Party 2014] [MarketingPlan] [tier 1] [July]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>

===Learning from Users: usability testing our Engagement Ladder===
Time: 9:30 Wednesday
 Let's do usability testing on our [https://wiki.mozilla.org/Webmaker/Engagement_Ladder Engagement Ladder], to see where people are getting stuck and increase our conversation rate. Our engagement ladder is everything. We're asking users to perform a small number of key calls to action (like signing up for a Webmaker account, sharing a teaching kit, entering an event into our platform, etc.) How do we do smart usability testing against these tasks so we can see where users are getting stuck -- and capture quick wins to increase our conversion rate?  Context: https://wiki.mozilla.org/Webmaker/Engagement_Ladder + [http://openmatt.org/2014/04/04/product_testing/ blog post on Q2 Product Testing] Lead: Cassie, Karen Smith Collaborators: Cori Schauer + Tony Santos (User research) + Kat https://etherpad.mozilla.org/learningfromusers Deliverables: 
* Run a usability test for account creation, event creation, and the new /explore page
* Clarify difference between co-design (community) and user testing (product)
* How can we communicate results better across mozilla 
Tags: [allhands] [usability]
<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"whiteboard": "[allhands] [usability]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>

===Appmaker: Getting Input on User Value===
Time: 9:30-12:30 Wednesday 
 Goal: test Appmaker strategy against MoCo market research analysis of the opportunity and need. Plus review user demographics and operators in each FirefoxOS market. We think there are gains in combining platform, marketplace, digital literacy. Are we teed up to provide value here? 
MoFo point: Bobby (+Ben) SF local contacts: Ria Joy, if we can get her to come from Seattle, Cori Schauer (conflicts with user research session at same time, Cori available wed 9-11) Length: 4-6 hours 
Tags: [allhands] [appmaker]
 Deliverables:  
* Document Appmaker audience segmentation & analysis
* Document work plan for feeding audience research into Appmaker product strategy
<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"whiteboard": "[allhands] [appmaker]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>

===Navigating Web Literacy with badges===
Time: 9:30 Wednesday 
 Goal: create an MVP for Web Literacy badge pathways. 
MoFo point: Chloe, Doug Length: 2-3 hours 
Collaborators: Mike L, Lucas, Andrew, Jess, Atul, Laura, Kat, Michelle 
Tags: [allhands] [pathways]
 Deliverables:  
* Create spreadsheet and populate with Web Literacy skills to issue 'badges'
* Link artwork to spreadsheet
* Create sample 'badge' pathways
<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"whiteboard": "[allhands] [pathways]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>

===New Communities: make a page on mozilla.org===
Time: 11:00 am Wednesday 
Lead: Dan/Erin Kissane Collaborators: Kaitlin, Dave, Studio MoFo Local SF contact: Holly Hastbritt (mozilla.org UX) Goal:  Collaborate & sprint on making a one-pager "New Communities" page  on Mozilla.org. Plus getting "News" and "Science" added to the  Mozilla.org "get involved" page. http://www.mozilla.org/contribute/ This can be a great way to tell the story around what Mozilla is doing  in these new spaces, plus drive referral traffic and contributors to  those projects.  '''Length''': 6hrs, max 
Etherpad: https://etherpad.mozilla.org/communities 
'''Tags''': [allhands][newcommunities]
<div style="align:left;">
<bugzilla>
{
"whiteboard": "[allhands][newcommunities]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>

===[https://developer.mozilla.org/en-US MDN] + Webmaker: prepping for May workweek===
Time:Wednesday 2:30
 Goal:  Determine, plot and start hacking on easy wins in preparation for the end of May MDN/Webmaker workweek. Plus document larger strategic goals for collaborating with MDN going forward. Discuss the Thimble roadmap (and Thimble tutorials in particular) and see how MDN needs can be included. MoFo lead: Laura/Brett SF local contacts: Ali Length: 1/4 day 
Tags: [allhands][MDN] 
Deliverables:  * Train MDN staff to create Thimble tutorials.  * Update MDN staff on product vision for Thimble and Brackets  * Transfer knowledge in creating MakeAPI galleries
<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"whiteboard": "[allhands][MDN]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>

===Marketing: Project:Trust Mozilla Campaign Coordination===
'''When''': Wed 1pm 
 Trust is an emerging theme in many campaigns going on across Mozilla: marketing, advocacy, policy, engagement, education. The leads of the campaigns have agreed to start meeting to coordinate the work, maybe ship a shared platform or two. This is the first meeting of that group. Lead: Geoff MacDougall Collaborators: Dave Steer, Erica Sackin, Andrea Wood, Mary Ellen Muckerman, Eric Petitt, Michelle Thorne, Alex Fowler SF local  contacts: Dave Steer, Eric Petitt Proposed length: 90 mins
<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"whiteboard": "[allhands][trust]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>

===Review and iterate Webmaker.org information architecture===
When: Wed 12:30
 Goal: Take stock of all the pages on webmaker.org. Are they serving our needs? Where are there gaps? How might we improve our information architecture to support new pages like /explore and profiles? And how can we measure if its working? We'll update a complete list of all current pages with "jobs" and notes on next steps for each 
Page list: [https://docs.google.com/spreadsheets/d/1ejFHysKOLEGXynU6ZUQgUKn5AVlNgqDBtjrTyM8Zbk4/edit#gid=0 Every Page Has a Job] (Google doc) 
Lead: Cassie Collaborators: Matt, Kat, Kate, Adam, Doug 
Tags: [allhands] [ia]
<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"whiteboard": "[allhands] [ia]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>

===Working with the GSMA===
Time: Wed 12:30-4:30 
 Goal: design first set of engagements w/ GSMA around Spreadtrum phone, Appmaker, Webmaker. Plus produce a 15 slide aligment deck for internal stakeholders MoFo point: Mark (+Ben) SF local contacts: Pete Scanlon, Ria Joy, Rick; Fant (a meeting at some point?), someone from Bill Walker org, someone from Christopher Lee org, Irina Sandu (voice?) David Palomino (voice?) Length: 4-6 hours 
Tags: [allhands] [gsma] 
<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"whiteboard": "[allhands] [gsma]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>

===Marketing: Project:Trust Mozilla Campaign Coordination===
When: Wed, 1pm
 Trust is an emerging theme in many campaigns going on across Mozilla: marketing, advocacy, policy, engagement, education. The leads of the campaigns have agreed to start meeting to coordinate the work, maybe ship a shared platform or two. This is the first meeting of that group. Lead: Geoff MacDougall Collaborators: Dave Steer, Erica Sackin, Andrea Wood, Mary Ellen Muckerman, Eric Petitt, Michelle Thorne, Alex Fowler SF local  contacts: Dave Steer, Eric Petitt Proposed length: 90 mins 
<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"whiteboard": "[allhands][trust]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>

===Hive CHI Wordpress MVP: Building out an MVP wordpress blog for Hive Chicago===
Time: 1:30pm Wednesday
 It's time for Hive Chicago to catch up with NYC and TOR by launching a dynamic online presence at hivechicago.org. Anyone is welcome to come help us scrum through this MVP with copy editing support, content and hosting expertise, CRM tools for Wordpress, graphic elements to make our work pop, etc.
 Context: this crappy old site http://www.hivechicago.org
 Lead: Robert Friedman
 Collaborators: Elsa, Sam, CLAW, Lainie
 Implementation Plan: https://docs.google.com/spreadsheet/ccc?key=0Aq0GxL3v7LxvdDV0T0RnTWJDNEV0V0M4aVJFeUtvQXc&usp=sharing
 Website Copy:: https://drive.google.com/a/mozilla.com/folderview?id=0B-EZWDUirQ46RGRvZUgtN1hsQWM&usp=sharing
 Deliverable: A blog! http://hivechicago.cnkt.ca/wp-admin/
 Tags: [allhands] [Hive] [HiveCHI]
 
<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"whiteboard": "[allhands] [Hive] [HiveCHI]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>

=== The future of badges.mozilla.org ===
*'''Time: Wednesday, 3:00 PM'''
*'''Lead''': Emily
*'''Collaborators''':
*'''Goal: Let's prototype this site's future'''. We will start with a look at what badges.mozilla.org was and who used it. Then we'll plan what it might become, and the larger vision and resources that will needed. Plus how it might it fit with the larger plan for MoFo and MoCo badges. Less yack, more hack.
* '''Deliverable''': Discuss and try to document the plan for badges.mozilla.org going forward. ( ''Here: https://etherpad.mozilla.org/badges-mozilla-org. And then link to from https://wiki.mozilla.org/Webmaker/Badges'' )
* '''Bugzilla tag''': [allhands][badges.mozilla.org]

<onlyinclude><div style="align:left;"><bugzilla>{
"whiteboard": "[allhands][badges.mozilla.org]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}</bugzilla><div style="align:left;"></onlyinclude>

==Anytime / Unscheduled==
===Getting real about Marketing and Press===
 This is critical. We have to pour as many people into the top of our funnel as possible. Press is a huge and proven way of doing  this. For example, if we landed two Lifehacker articles per quarter, we'd be tripling our users. We  don't currently have solid press kits/marketing kits for our products. Let's make some. Plus work out the details for how we're going to pitch Webmaker to press going forward.  Lead: Erica S and Lainie  Collaborators: Amira, Erin K, Kaitlin T, Erika D, Sabrina, Dave Steer, Hannah, Kaitlyn, Erin Kissane, Dan Sinker Note: Loop in [https://etherpad.mozilla.org/MoCo-MoFo Moco Marketing]? Length: 3-4 hours 
When: Anytime 
[http://mzl.la/1mNPWra Tag]: [allhands][press]
<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"whiteboard": "[allhands][press]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>
===Hive: Shipping Hive Cookbook Pages===
 Goal: Ship pages of the Hive Cookbook. Documenting and outlining existing Hive practices, strategies, goals and thinking onto the Mozilla Wiki. Started here https://wiki.mozilla.org/Webmaker/Hive '''Lead''': Chris L, Leah, Sam Katherine '''Collaborators''': Robert, Elsa, Julia, Lainie, Karen 
/>'''When''': Anytime, 1/2 day 
'''Tag''': [allhands][hive] 
Deliverables: 
<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"whiteboard": "[allhands][hive]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>

===Partnerships: becoming a closing machine===
 We now work from an integrated pipeline. It contains partners that bring us funding, contributors, or both. This means two things: (i) further integrating our recruitment, product, and management of partners, and (ii) become a closing machine.
* Goal: Cultural: Shift to being 'closers that care'. Everyone in the org understands the urgency of money and is clear-eyed about how we get to keep working.
* Practical: Log and start to action all of our leads. Account for managed growth through grants. Implement new ways to communicate the long-term evolution of our fundraising and stay accountable to each other.
* Lead: Ben Moskowitz Collaborators: Geoff MacDougall, Matt Thompson, Hannah, Lynn Melander Moore, Amira Dhalla, David Ascher
* When: Anytime, 2 hours
* Deliverables: Bridges between Webmaker requirements and fundraising lead generation 
<bugzilla>
{
"whiteboard": "[allhands] [closing]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>

=== Code contribution: guidelines and one-stop shopping ===
'''We want to ensure our code contributors feel welcome in our open source project'''. Let's first examine what conditions and guidelines we need, where we're doing well, and where we need to improve. Then turn that into an inviting "one stop shopping" page at developer.webmaker.org that can on-board new code contributors. 
'''Lead''':Kate 
 '''When: Anytime ''' 
Tags: [allhands][codecontrib]
<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"whiteboard": "[allhands][codecontrib]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>

===Prepping the "Webmaker Textbook 1.0" writing sprint===
Prepping for a book sprint to create an open "textbook" or "cookbook" for teaching web literacy. Let's get our roadmap ready for shipping awesome Webmaker teaching curriculum. Toronto will host a writing sprint May 7,8,9 to complete webmaker.org/explore. Recognizing this piece of content is crucial to our successful launch this summer, we need to hit the ground running. We will make sure each attendees has an assigned Web Lit competency and that the work is scoped so we can spend a full three days writing 
'''Context''': https://wiki.mozilla.org/Webmaker/Textbook 
Lead: OpenMatt Collaborators: Kat, Michelle, Claw, Cassie, Kate, Drushka, Fuzzy 
When: Anytime 
Tags: [allhands] [textbook]
<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"whiteboard": "[allhands] [textbook]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>

=== Email-fu (3:30 in 7th floor room "Justice League") ===
https://www.evernote.com/shard/s202/sh/c0ef9720-3791-4f03-9ba1-d3efaed02f55/943400ad77698088067406b5ac127f8c/deep/0/File-Shi-DeRu-and-Shi-DeYang.jpg---Wikipedia,-the-free-encyclopedia.png
 Goal: Now that we are sending out emails to larger groups, including supporters registered for events, let's make sure that they're as effective as can be. Lead: Andrea (twitter: @valiant): Collaborators: Jbuck (infra), Aki (figure out HTML emails), Sabrina (design), Drushka (words) 
When: 3:30 in 7th floor room "Justice League" 
 Etherpad: https://etherpad.mozilla.org/allhands-email-fu
<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"whiteboard": "[allhands] [email]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>

===MoFo / MoCo Collaborations===
 Goal: Collaborate with our awesome MoCo colleauges. 
'''Lead''': 
'''Collaborators''': 
'''When''': Anytime, list in bug clearly 
'''Tag''': [allhands][mofoco] 
Deliverables: 
<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"whiteboard": "[allhands][mofoco]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>

===Brainstorm better name for programs under "new communities"===
 Goal: Come up with a name that better captures what's going on. Also check this out: https://etherpad.mozilla.org/sinker-newcommunities 
'''Lead''': Erin? Dave S? Kay? 
'''Collaborators''': All y'all 
'''When''': Anytime 
'''Tag''': [allhands][betternaming] 
Deliverables: A new name 
<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"whiteboard": "[allhands][betternaming]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>

== Thursday ==
===Maker Party: Real Life User Stories===
 Let's role-play to see how ready we are. A captivating theatrical experience, directed by Geoffrey MacDougall, and featuring a full cast of MoFos. We've spent months building systems, content, funnels, and tools that let us engage and support our various users, supporters, and contributors. On July 15th those  systems, content and funnels will be put to the test. Let's rehearse and drill our processes. This session will see us act out (literally)  the user stories in our [[Engagement Ladder workhttps://wiki.mozilla.org/Webmaker/Engagement_Ladder|Engagement Ladder work]], making sure there's no walls or black holes. Lead: Geoffrey MacDougall Collaborators: Amira Dhalla, Chris Lawrence, Matt Thompson When: Thursday morning
<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"whiteboard": "[allhands] [user_stories]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/pjvdd1t5.png

AllHands

2014-04-29T15:52:33Z

Brett Gaylor:

Webmaker/Design/2014Q2

2014-04-26T15:26:37Z

Brett Gaylor: /* Gvn Pre-AH Sprint */

= Q2 Targets =

== Explore R2 ==
* '''Whiteboard:''' [explore][r2]
* '''Who's responsible:''' Kate, Cassie, Aki
* '''Target completion date:''' April 25
==== Objectives ====
* Advance prototype (currently: http://webmaker-explore.herokuapp.com)
* MVP requirements and scoping: https://etherpad.mozilla.org/exploremvp
<div>
<bugzilla>
{
"product": "webmaker",
"whiteboard": "explore, r2",
"include_fields": "id, priority, component, summary, status, assigned_to",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
== 2014 Maker Party ==

* '''Whiteboard:''' [2014makerparty][mvp]
* '''Who's responsible:''' Gavin
* '''Target completion date:''' April 28th
==== Objectives ====
* Live site by All Hands, April 28
* Localization
<div>
<bugzilla>
{
"product": "webmaker",
"whiteboard": "2014makerparty, mvp",
"include_fields": "id, component, summary, status, assigned_to",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
== Teaching Kit Fast Follow ==

* '''Whiteboard:''' [teachingkit][r2]
* '''Who's responsible:''' Kate
* '''Target completion date:''' April 11
==== Objectives ====
* Web Lit tagging
* Tutorial instructions
* See '''[https://docs.google.com/a/mozillafoundation.org/spreadsheet/ccc?key=0AjfN9sXlOXt1dDZBcHRDdFVDZFU4Y2o5VlZlM0t2Snc#gid=1 Teaching Kit User Stories]'''
<div>
<bugzilla>
{
"product": "webmaker",
"whiteboard": "teachingkit, r2",
"include_fields": "id, component, summary, status, assigned_to",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
== Badges Proof of Concept ==

* '''Whiteboard:''' [webmakerbadges][mvp]
* '''Who's responsible:''' Cassie, Gavin, Kate
* '''Target completion date:''' April 25 (All Hands)
==== Objectives ====
A "moonshot" objective to build a simple integration with Badge Kit on webmaker.org that completes a full user journey to apply for the super mentor badge.

Post-MVP includes:
* A section on webmaker to explore badges (e.g. badges.webmaker.org)
* Other interactions that prompt you to apply for a badge, like after you host an event, create a teaching kit, etc.
* Other badges, including Web Lit badges (first of which will be Remix)
* Integrating Discovery pathways with Webmaker.org in some way. See http://openbadges-discovery.herokuapp.com/
* Update https://webmaker.org/mentor so you can earn the supermentor badge from this page using badgekit
* Be able to apply for a badge from /Explore under "Become a mentor" – See the 'featured mentors' section here: https://webmaker.mofostaging.net/explore/#/competencies/navigation
* integrate badges you've earned with user profiles

<div>
<bugzilla>
{
"product": "webmaker",
"whiteboard": "webmakerbadges, mvp",
"include_fields": "id, component, summary, status, assigned_to",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
== Web Lit badges graphic design ==
* '''Whiteboard:''' [weblitdesign]
* '''Who's responsible:''' Cassie, Studio Mofo (tbd)
* '''Target completion date:''' June 30
<div>
<bugzilla>
{
"product": "webmaker",
"whiteboard": "[weblitdesign]",
"include_fields": "id, component, summary, status, assigned_to",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>

== Homepage & site IA revisions ==
* '''Whiteboard:''' [homepage]
* '''Who's responsible:''' TBD
* '''Target completion date:''' TBD
==== Objectives ====
* Further communicate mentor focus
* Improve flows to tools and explore section
* Improve main nav and footer
<div>
<bugzilla>
{
"product": "webmaker",
"whiteboard": "homepage",
"include_fields": "id, priority, component, summary, status, assigned_to",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
== Revised Profiles ==
* '''Whiteboard:''' [profile2]
* '''Who's responsible:''' TBD
* '''Target completion date:''' TBD
==== Objectives ====
* TBD
* Improved UI
* Focus on mentorship and activity
* Add contact info
* include hosting of events, contributor activity
* Implement results of user testing + surveys
* Indicate users' activities
<div>
<bugzilla>
{
"product": "webmaker",
"whiteboard": "profile2",
"include_fields": "id, priority, component, summary, status, assigned_to",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
== Gallery revisions ==
* '''Whiteboard:''' [gallery][r2]
* '''Who's responsible:''' TBD
* '''Target completion date:''' TBD
==== Objectives ====
* Allow users to tag any URL and have it show up on Webmaker.org (Atul's bookmarklet)
<div>
<bugzilla>
{
"product": "webmaker",
"whiteboard": "gallery, r2",
"include_fields": "id, priority, component, summary, status, assigned_to",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
== Gvn Pre-AH Sprint ==

* '''Whiteboard:''' [pre-ah]
* '''Who's responsible:''' Gavin
* '''Target completion date:''' April 25th
<div>
<bugzilla>
{
"product": "webmaker",
"whiteboard": "pre-ah",
"include_fields": "id, component, summary, status, assigned_to",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>

Webmaker/Design/2014Q2

2014-04-26T15:26:16Z

Brett Gaylor:

= Q2 Targets =

== Explore R2 ==
* '''Whiteboard:''' [explore][r2]
* '''Who's responsible:''' Kate, Cassie, Aki
* '''Target completion date:''' April 25
==== Objectives ====
* Advance prototype (currently: http://webmaker-explore.herokuapp.com)
* MVP requirements and scoping: https://etherpad.mozilla.org/exploremvp
<div>
<bugzilla>
{
"product": "webmaker",
"whiteboard": "explore, r2",
"include_fields": "id, priority, component, summary, status, assigned_to",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
== 2014 Maker Party ==

* '''Whiteboard:''' [2014makerparty][mvp]
* '''Who's responsible:''' Gavin
* '''Target completion date:''' April 28th
==== Objectives ====
* Live site by All Hands, April 28
* Localization
<div>
<bugzilla>
{
"product": "webmaker",
"whiteboard": "2014makerparty, mvp",
"include_fields": "id, component, summary, status, assigned_to",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
== Teaching Kit Fast Follow ==

* '''Whiteboard:''' [teachingkit][r2]
* '''Who's responsible:''' Kate
* '''Target completion date:''' April 11
==== Objectives ====
* Web Lit tagging
* Tutorial instructions
* See '''[https://docs.google.com/a/mozillafoundation.org/spreadsheet/ccc?key=0AjfN9sXlOXt1dDZBcHRDdFVDZFU4Y2o5VlZlM0t2Snc#gid=1 Teaching Kit User Stories]'''
<div>
<bugzilla>
{
"product": "webmaker",
"whiteboard": "teachingkit, r2",
"include_fields": "id, component, summary, status, assigned_to",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
== Badges Proof of Concept ==

* '''Whiteboard:''' [webmakerbadges][mvp]
* '''Who's responsible:''' Cassie, Gavin, Kate
* '''Target completion date:''' April 25 (All Hands)
==== Objectives ====
A "moonshot" objective to build a simple integration with Badge Kit on webmaker.org that completes a full user journey to apply for the super mentor badge.

Post-MVP includes:
* A section on webmaker to explore badges (e.g. badges.webmaker.org)
* Other interactions that prompt you to apply for a badge, like after you host an event, create a teaching kit, etc.
* Other badges, including Web Lit badges (first of which will be Remix)
* Integrating Discovery pathways with Webmaker.org in some way. See http://openbadges-discovery.herokuapp.com/
* Update https://webmaker.org/mentor so you can earn the supermentor badge from this page using badgekit
* Be able to apply for a badge from /Explore under "Become a mentor" – See the 'featured mentors' section here: https://webmaker.mofostaging.net/explore/#/competencies/navigation
* integrate badges you've earned with user profiles

<div>
<bugzilla>
{
"product": "webmaker",
"whiteboard": "webmakerbadges, mvp",
"include_fields": "id, component, summary, status, assigned_to",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
== Web Lit badges graphic design ==
* '''Whiteboard:''' [weblitdesign]
* '''Who's responsible:''' Cassie, Studio Mofo (tbd)
* '''Target completion date:''' June 30
<div>
<bugzilla>
{
"product": "webmaker",
"whiteboard": "[weblitdesign]",
"include_fields": "id, component, summary, status, assigned_to",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>

== Homepage & site IA revisions ==
* '''Whiteboard:''' [homepage]
* '''Who's responsible:''' TBD
* '''Target completion date:''' TBD
==== Objectives ====
* Further communicate mentor focus
* Improve flows to tools and explore section
* Improve main nav and footer
<div>
<bugzilla>
{
"product": "webmaker",
"whiteboard": "homepage",
"include_fields": "id, priority, component, summary, status, assigned_to",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
== Revised Profiles ==
* '''Whiteboard:''' [profile2]
* '''Who's responsible:''' TBD
* '''Target completion date:''' TBD
==== Objectives ====
* TBD
* Improved UI
* Focus on mentorship and activity
* Add contact info
* include hosting of events, contributor activity
* Implement results of user testing + surveys
* Indicate users' activities
<div>
<bugzilla>
{
"product": "webmaker",
"whiteboard": "profile2",
"include_fields": "id, priority, component, summary, status, assigned_to",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
== Gallery revisions ==
* '''Whiteboard:''' [gallery][r2]
* '''Who's responsible:''' TBD
* '''Target completion date:''' TBD
==== Objectives ====
* Allow users to tag any URL and have it show up on Webmaker.org (Atul's bookmarklet)
<div>
<bugzilla>
{
"product": "webmaker",
"whiteboard": "gallery, r2",
"include_fields": "id, priority, component, summary, status, assigned_to",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
== Gvn Pre-AH Sprint ==

* '''Whiteboard:''' [pre-ah]
* '''Who's responsible:''' Gavin
* '''Target completion date:''' April 25th
</div>
<bugzilla>
{
"product": "webmaker",
"whiteboard": "pre-ah",
"include_fields": "id, component, summary, status, assigned_to",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>

Webmaker/Design/2014Q2

2014-04-26T15:24:36Z

Brett Gaylor:

<div>
= Q2 Targets =

== Explore R2 ==
* '''Whiteboard:''' [explore][r2]
* '''Who's responsible:''' Kate, Cassie, Aki
* '''Target completion date:''' April 25
==== Objectives ====
* Advance prototype (currently: http://webmaker-explore.herokuapp.com)
* MVP requirements and scoping: https://etherpad.mozilla.org/exploremvp
<bugzilla>
{
"product": "webmaker",
"whiteboard": "explore, r2",
"include_fields": "id, priority, component, summary, status, assigned_to",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>

== 2014 Maker Party ==

* '''Whiteboard:''' [2014makerparty][mvp]
* '''Who's responsible:''' Gavin
* '''Target completion date:''' April 28th
==== Objectives ====
* Live site by All Hands, April 28
* Localization

<bugzilla>
{
"product": "webmaker",
"whiteboard": "2014makerparty, mvp",
"include_fields": "id, component, summary, status, assigned_to",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>

== Teaching Kit Fast Follow ==

* '''Whiteboard:''' [teachingkit][r2]
* '''Who's responsible:''' Kate
* '''Target completion date:''' April 11
==== Objectives ====
* Web Lit tagging
* Tutorial instructions
* See '''[https://docs.google.com/a/mozillafoundation.org/spreadsheet/ccc?key=0AjfN9sXlOXt1dDZBcHRDdFVDZFU4Y2o5VlZlM0t2Snc#gid=1 Teaching Kit User Stories]'''
<bugzilla>
{
"product": "webmaker",
"whiteboard": "teachingkit, r2",
"include_fields": "id, component, summary, status, assigned_to",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>

== Badges Proof of Concept ==

* '''Whiteboard:''' [webmakerbadges][mvp]
* '''Who's responsible:''' Cassie, Gavin, Kate
* '''Target completion date:''' April 25 (All Hands)
==== Objectives ====
A "moonshot" objective to build a simple integration with Badge Kit on webmaker.org that completes a full user journey to apply for the super mentor badge.

Post-MVP includes:
* A section on webmaker to explore badges (e.g. badges.webmaker.org)
* Other interactions that prompt you to apply for a badge, like after you host an event, create a teaching kit, etc.
* Other badges, including Web Lit badges (first of which will be Remix)
* Integrating Discovery pathways with Webmaker.org in some way. See http://openbadges-discovery.herokuapp.com/
* Update https://webmaker.org/mentor so you can earn the supermentor badge from this page using badgekit
* Be able to apply for a badge from /Explore under "Become a mentor" – See the 'featured mentors' section here: https://webmaker.mofostaging.net/explore/#/competencies/navigation
* integrate badges you've earned with user profiles

<bugzilla>
{
"product": "webmaker",
"whiteboard": "webmakerbadges, mvp",
"include_fields": "id, component, summary, status, assigned_to",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>

== Web Lit badges graphic design ==
* '''Whiteboard:''' [weblitdesign]
* '''Who's responsible:''' Cassie, Studio Mofo (tbd)
* '''Target completion date:''' June 30
<bugzilla>
{
"product": "webmaker",
"whiteboard": "[weblitdesign]",
"include_fields": "id, component, summary, status, assigned_to",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>

== Homepage & site IA revisions ==
* '''Whiteboard:''' [homepage]
* '''Who's responsible:''' TBD
* '''Target completion date:''' TBD
==== Objectives ====
* Further communicate mentor focus
* Improve flows to tools and explore section
* Improve main nav and footer
<bugzilla>
{
"product": "webmaker",
"whiteboard": "homepage",
"include_fields": "id, priority, component, summary, status, assigned_to",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</onlyinclude>
== Revised Profiles ==
* '''Whiteboard:''' [profile2]
* '''Who's responsible:''' TBD
* '''Target completion date:''' TBD
==== Objectives ====
* TBD
* Improved UI
* Focus on mentorship and activity
* Add contact info
* include hosting of events, contributor activity
* Implement results of user testing + surveys
* Indicate users' activities
<bugzilla>
{
"product": "webmaker",
"whiteboard": "profile2",
"include_fields": "id, priority, component, summary, status, assigned_to",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>

== Gallery revisions ==
* '''Whiteboard:''' [gallery][r2]
* '''Who's responsible:''' TBD
* '''Target completion date:''' TBD
==== Objectives ====
* Allow users to tag any URL and have it show up on Webmaker.org (Atul's bookmarklet)
<bugzilla>
{
"product": "webmaker",
"whiteboard": "gallery, r2",
"include_fields": "id, priority, component, summary, status, assigned_to",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>

== Gvn Pre-AH Sprint ==

* '''Whiteboard:''' [pre-ah]
* '''Who's responsible:''' Gavin
* '''Target completion date:''' April 25th

<bugzilla>
{
"product": "webmaker",
"whiteboard": "pre-ah",
"include_fields": "id, component, summary, status, assigned_to",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>

Webmaker/Engagement Ladder

2014-04-26T15:19:59Z

Brett Gaylor:

__NOTOC__
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/ry8lxg84.png
=What we're shipping in Q2:=
** 1) '''DEFINITIONS''' -- '''Document the on-ramps'''. As user stories. "When users do x, we want to count and respond like y."
** 2) '''INFRASTRUCTURE''' -- '''Wire the on-ramps.''' So we can a) count and b) respond when people walk through them.
** 3) '''COMMUNICATIONS''' -- '''Communicate to the on-rampees.''' The messages users receive once they walk through. With the right calls to action to do more.
** 4) '''NEW: USABILITY TESTING''' -- '''User test the on-ramps.''' Where are these users getting stuck or stubbing their toe on these on-ramps? Clear away these blockers to increase our conversion rates.

===Key links===
* '''[https://docs.google.com/spreadsheet/ccc?key=0Al0Wg7eR7tHcdGxNNE41RTl4eHBLNG92ZXBHY2l6MkE&usp=sharing#gid=0 DEFINITIONS SPREADSHEET]''' -- http://mzl.la/contribution_pathways -- Contribution Pathways. User stories that list the counting and responses we need. Broken down by sprint'''
* '''[http://adamlofting.github.io/mofo-contributors-dashboard/ CONTRIBUTION DASHBOARD] (prototype)''' -- Pulling in and visualizing contributor data
* [https://wiki.mozilla.org/Webmaker/Contribution ENGAGEMENT LADDER]. High level. Our user, supporter, contributor funnel. How Webmaker contributors TEACH, BUILD and ORGANIZE.
* EMAIL LIST SEGMENTS. From BSD https://etherpad.mozilla.org/Webmaker-email-segments

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/8riscpl0.png

=1) DEFINITIONS =
===DEFINITIONS v2 (April 2) (COMPLETE)===
* '''Goal''': MVP user stories. Covering the key bases: signing up, entering an event, etc. ([https://docs.google.com/spreadsheet/ccc?key=0Al0Wg7eR7tHcdGxNNE41RTl4eHBLNG92ZXBHY2l6MkE&usp=sharing#gid=6 COMPLETED HERE])
* '''Roles''': R: '''Michelle''' A: '''Claw''' C: '''Amira, Jbuck, Andrea''' I: webmaker-dev, mozteach
* '''Bugzilla''': Component: '''Engagement Ladder''' | Whiteboard tag: '''[definitions-v2]'''
<div>
<onlyinclude>
<bugzilla>
{
"product": "webmaker",
"component":"Engagement Ladder",
"whiteboard": "[definitions-v2]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</onlyinclude>
</div>
===DEFINITIONS v3 & v4 (April 9) (COMPLETE)===
* '''Goal''': From user to contributor. Additional use cases beyond the MVP: signing up for training, presenting on a community call, etc.
<div>
<onlyinclude>
<bugzilla>
{
"product": "webmaker",
"component":"Engagement Ladder",
"whiteboard": "[definitions-v3]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</onlyinclude>
</div>
=2) Infrastructure=
=== INFRASTRUCTURE v1 (April 11)===
* '''Goal''': Trigger counting and communications for MVP users stories cases documented in the "definitions" sprint.
* '''Roles''': R: '''Jbuck''' A: '''Brett''' C: '''Adam, Michelle, Andrea''' I: '''mozteach, webmaker-dev, engagement team'''
* '''Bugzilla''': Component: '''Engagement Ladder''' | Whiteboard tag: '''infrastructurev1'''
<onlyinclude>
</div>

<div>
<bugzilla>
{
"product": "Webmaker",
"status_whiteboard": "infrastructurev1",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</onlyinclude>
</div>
=== INFRASTRUCTURE v2 (April 25 -- before All Hands?)===
* '''Goal''': Trigger counting and response for the V3 users stories cases documented here: http://mzl.la/contribution_pathways
* '''Bugzilla''': Component: '''Engagement Ladder''' | Whiteboard tag: '''infrastructurev2'''
* '''File one of these tickets''': http://mzl.la/infrastructurev2
<div>
<onlyinclude>
<bugzilla>
{
"product": "Webmaker",
"status_whiteboard": "infrastructurev2",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</onlyinclude>
</div>
= 3) Communications =
=== COMMUNICATIONS v2 (April 15)===
* '''Roles''': R: '''Lainie''' A: '''Brett & Matt''' C: '''Amira, Jbuck, ErikaD, Andrea'''
* '''Goal''': 1) Review and write current and new email responses. For sign-up, events, teaching kits and remix.
* 2) Learn and model best practices. Learn how to get good at this.
** (Use this for best practices: http://reallygoodemails.com/ and CC Andrea on all tickets)

===Key links===
* '''Email copy''': current drafts for all email responses is here: https://teach.etherpad.mozilla.org/emailengagementtemplates
* '''Bugzilla''': Component: '''Engagement Ladder''' | Whiteboard tag: '''[communications-v2]''' | [http://mzl.la/1dNhNox File one of these tickets]
<div>
<onlyinclude>
<bugzilla>
{
"product": "webmaker",
"component":"Engagement Ladder",
"whiteboard": "[communications-v2]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</onlyinclude>
</div>
=== COMMUNICATIONS v3 (April 25 -- before All Hands)===
* '''Roles''': R: '''Lainie''' A: '''Brett & Matt''' C: '''Amira, Jbuck, ErikaD, Andrea'''
* '''Goal''': Write the emails. Plus optimization and housekeeping from v2.
<div>
<onlyinclude>
<bugzilla>
{
"product": "webmaker",
"component":"Engagement Ladder",
"whiteboard": "[communications-v3]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</onlyinclude>
</div>

= 4) USABILITY TESTING v1 (April 25)=
* Do initial user testing for the V2 and V3 user stories listed here: http://mzl.la/contribution_pathways
* Where are users getting stuck? What are quick wins for addressing them?
* Blog, triage key learnings together, and then file those learnings as actionable tickets.

Tickets to file:
** Sign-up: do usability testing and document key learnings
** Event creation: do usability testing and document key learnings
** Submit a teaching kit

Lower priority:
** Sign up and on-boarding for Webmaker training (???)
** Attend and present in a Webmaker community call (???)
** Translation and localization (???)
** Participate in Webmaker QA or testing (???)

===Quick Links===
'''Engagement Ladder tickets'''
* [https://bugzilla.mozilla.org/enter_bug.cgi?product=Webmaker&component=Engagement%20Ladder File a ticket]
* [https://bugzilla.mozilla.org/buglist.cgi?list_id=9811999&query_format=advanced&component=Engagement%20Ladder&product=Webmaker See all tickets]

Webmaker/Engagement Ladder

2014-04-26T15:11:21Z

Brett Gaylor:

__NOTOC__
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/ry8lxg84.png
=What we're shipping in Q2:=
** 1) '''DEFINITIONS''' -- '''Document the on-ramps'''. As user stories. "When users do x, we want to count and respond like y."
** 2) '''INFRASTRUCTURE''' -- '''Wire the on-ramps.''' So we can a) count and b) respond when people walk through them.
** 3) '''COMMUNICATIONS''' -- '''Communicate to the on-rampees.''' The messages users receive once they walk through. With the right calls to action to do more.
** 4) '''NEW: USABILITY TESTING''' -- '''User test the on-ramps.''' Where are these users getting stuck or stubbing their toe on these on-ramps? Clear away these blockers to increase our conversion rates.

===Key links===
* '''[https://docs.google.com/spreadsheet/ccc?key=0Al0Wg7eR7tHcdGxNNE41RTl4eHBLNG92ZXBHY2l6MkE&usp=sharing#gid=0 DEFINITIONS SPREADSHEET]''' -- http://mzl.la/contribution_pathways -- Contribution Pathways. User stories that list the counting and responses we need. Broken down by sprint'''
* '''[http://adamlofting.github.io/mofo-contributors-dashboard/ CONTRIBUTION DASHBOARD] (prototype)''' -- Pulling in and visualizing contributor data
* [https://wiki.mozilla.org/Webmaker/Contribution ENGAGEMENT LADDER]. High level. Our user, supporter, contributor funnel. How Webmaker contributors TEACH, BUILD and ORGANIZE.
* EMAIL LIST SEGMENTS. From BSD https://etherpad.mozilla.org/Webmaker-email-segments

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/8riscpl0.png

=1) DEFINITIONS =
===DEFINITIONS v2 (April 2) (COMPLETE)===
* '''Goal''': MVP user stories. Covering the key bases: signing up, entering an event, etc. ([https://docs.google.com/spreadsheet/ccc?key=0Al0Wg7eR7tHcdGxNNE41RTl4eHBLNG92ZXBHY2l6MkE&usp=sharing#gid=6 COMPLETED HERE])
* '''Roles''': R: '''Michelle''' A: '''Claw''' C: '''Amira, Jbuck, Andrea''' I: webmaker-dev, mozteach
* '''Bugzilla''': Component: '''Engagement Ladder''' | Whiteboard tag: '''[definitions-v2]'''
<div>
<onlyinclude>
<bugzilla>
{
"product": "webmaker",
"component":"Engagement Ladder",
"whiteboard": "[definitions-v2]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</onlyinclude>
===DEFINITIONS v3 & v4 (April 9) (COMPLETE)===
* '''Goal''': From user to contributor. Additional use cases beyond the MVP: signing up for training, presenting on a community call, etc.
<onlyinclude>
<bugzilla>
{
"product": "webmaker",
"component":"Engagement Ladder",
"whiteboard": "[definitions-v3]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</onlyinclude>
</div>
=2) Infrastructure=
=== INFRASTRUCTURE v1 (April 11)===
* '''Goal''': Trigger counting and communications for MVP users stories cases documented in the "definitions" sprint.
* '''Roles''': R: '''Jbuck''' A: '''Brett''' C: '''Adam, Michelle, Andrea''' I: '''mozteach, webmaker-dev, engagement team'''
* '''Bugzilla''': Component: '''Engagement Ladder''' | Whiteboard tag: '''infrastructurev1'''
<onlyinclude>
<bugzilla>
{
"product": "Webmaker",
"status_whiteboard": "infrastructurev1",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</onlyinclude>
=== INFRASTRUCTURE v2 (April 25 -- before All Hands?)===
* '''Goal''': Trigger counting and response for the V3 users stories cases documented here: http://mzl.la/contribution_pathways
* '''Bugzilla''': Component: '''Engagement Ladder''' | Whiteboard tag: '''infrastructurev2'''
* '''File one of these tickets''': http://mzl.la/infrastructurev2
<onlyinclude>
<bugzilla>
{
"product": "Webmaker",
"status_whiteboard": "infrastructurev2",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</onlyinclude>

= 3) Communications =
=== COMMUNICATIONS v2 (April 15)===
* '''Roles''': R: '''Lainie''' A: '''Brett & Matt''' C: '''Amira, Jbuck, ErikaD, Andrea'''
* '''Goal''': 1) Review and write current and new email responses. For sign-up, events, teaching kits and remix.
* 2) Learn and model best practices. Learn how to get good at this.
** (Use this for best practices: http://reallygoodemails.com/ and CC Andrea on all tickets)

===Key links===
* '''Email copy''': current drafts for all email responses is here: https://teach.etherpad.mozilla.org/emailengagementtemplates
* '''Bugzilla''': Component: '''Engagement Ladder''' | Whiteboard tag: '''[communications-v2]''' | [http://mzl.la/1dNhNox File one of these tickets]
<onlyinclude>
<bugzilla>
{
"product": "webmaker",
"component":"Engagement Ladder",
"whiteboard": "[communications-v2]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</onlyinclude>
=== COMMUNICATIONS v3 (April 25 -- before All Hands)===
* '''Roles''': R: '''Lainie''' A: '''Brett & Matt''' C: '''Amira, Jbuck, ErikaD, Andrea'''
* '''Goal''': Write the emails. Plus optimization and housekeeping from v2.
<onlyinclude>
<bugzilla>
{
"product": "webmaker",
"component":"Engagement Ladder",
"whiteboard": "[communications-v3]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</onlyinclude>

= 4) USABILITY TESTING v1 (April 25)=
* Do initial user testing for the V2 and V3 user stories listed here: http://mzl.la/contribution_pathways
* Where are users getting stuck? What are quick wins for addressing them?
* Blog, triage key learnings together, and then file those learnings as actionable tickets.

Tickets to file:
** Sign-up: do usability testing and document key learnings
** Event creation: do usability testing and document key learnings
** Submit a teaching kit

Lower priority:
** Sign up and on-boarding for Webmaker training (???)
** Attend and present in a Webmaker community call (???)
** Translation and localization (???)
** Participate in Webmaker QA or testing (???)

===Quick Links===
'''Engagement Ladder tickets'''
* [https://bugzilla.mozilla.org/enter_bug.cgi?product=Webmaker&component=Engagement%20Ladder File a ticket]
* [https://bugzilla.mozilla.org/buglist.cgi?list_id=9811999&query_format=advanced&component=Engagement%20Ladder&product=Webmaker See all tickets]

AllHands/Funnel Inside

2014-04-26T05:54:25Z

Brett Gaylor: /* Review and iterate Webmaker.org information architecture */

[[File:Funnel Inside.png|225px|right]]
===Learning from Users: getting good at usability testing===
Time: 9:30 Wednesday
 Let's do usability testing on our engagement ladder, to see where people are getting stuck and increase our conversation rate. Our engagement ladder is everything. We're asking users to perform a small number of key calls to action (like signing up for a   Webmaker  account, sharing a teaching kit, entering an event into our platform, etc.) How do we do smart usability testing against these tasks so we can see where users are getting stuck -- and capture quick wins to increase our conversion rate?  Context: http://mzl.la/Pu9ulB + http://openmatt.org/2014/04/04/product_testing/ Lead: Cassie/Karen Smith Collaborators: Cori Schauer  + Tony Santos (User research) + Kat Deliverable: Run a usability test for account creation, event creation, and the new /explore page. 

===Prepping the Webmaker/explore writing sprint===
Prepping for a book sprint to create an open "textbook" or "cookbook" for teaching web literacy. Let's get our roadmap ready for shipping awesome Webmaker teaching curriculum. Toronto will host a writing sprint May 7,8,9 to complete webmaker.org/explore.  Recognizing this piece of content is crucial to our successful launch this summer, we need to hit the ground running. We will make sure each attendees has an assigned Web Lit competency and  that the work is scoped so we can spend a full three days writing Lead (for prep and logistics): Matt Collaborators: Kat, Michelle, Claw, Cassie, Kate, Drushka, Fuzzy Deliverable: Document our roadmap. For shipping the textbook, plus celebrating the community contributing to it. (Kat's Webmaker series) 

===Prototyping together===
'''How to tell and sell the difference between prototype and product'''. Let's work out a process for how we turn prototypes into product that will keep us agile while allowing us to meet our current commitments. We did great work last quarter turning the Web Lit Map into an exciting content direction.  We've got great new extensions for the browser,  3rd   party app integration and more coming up. Let's keep this going,  and  also be clear about expectations for sales, partnerships, and   productization. Lead: Brett 
Collaborators: Atul, WebmakerUX team, Doug, Paula, Dev team, Fuzzy, Chloe, Mike Larrson, Jess Deliverable:  * Documentation for the life cycle of a prototype.  * Documentation for how to talk about and "sell" key current protoypes like the Web Lit Mapper.  

===Appmaker: Getting Input on User Value&nbsp===
Time: 9:30-12:30 Wednesday 
 Goal: test Appmaker strategy against MoCo market research team analysis of the opportunity and need. Plus review user demographics and operators in each  Firefox OS market. We think there are gains in combining platform, marketplace, digital literacy. Are we teed up to provide value here? 
MoFo point: Bobby (+Ben) SF local  contacts: Ria Joy, if we can get her to come from Seattle, Cori Schauer (conflicts with user research session at same time, Cori available wed 9-11) Proposed length: 4-6 hours Deliverable:  
* Document Appmaker audience segmentation & analysis
* Document work plan for feeding audience research into Appmaker product strategy

===Working with the GSMA===
Time: 12:30-4:30 Wednesday 
 Goal: design first set of engagements w/ GSMA around Spreadtrum phone, Appmaker, Webmaker. Plus produce a 15 slide aligment deck for internal stakeholders MoFo point: Mark (+Ben) SF  local contacts: Pete Scanlon, Ria Joy, Rick  Fant (a meeting at some point?), someone from  Bill Walker org, someone  from Christopher Lee org, Irina Sandu (voice?)  David Palomino (voice?) Proposed length: 4-6 hours Deliverable:  * Ship internal slide deck on the mobile development opportunity for Mozilla  * Scope 3 actionable demo collaborations between MoCo + MoFo 

===Review and iterate Webmaker.org information architecture===
Time: 12:30 Wednesday
 Goal: Take stock of all the pages on webmaker.org. Are they serving our needs? Where are there gaps? How might we improve our information architecture to support new pages like /explore and profiles? And how can we measure if its working? Lead: Cassie Collaborators: Matt, Kat, Kate, Adam Deliverable: A complete list of all current pages with "jobs" and notes on next steps for each Resource: Google doc: [https://docs.google.com/spreadsheets/d/1ejFHysKOLEGXynU6ZUQgUKn5AVlNgqDBtjrTyM8Zbk4/edit#gid=0 Every Page Has a Job] 

===Email like a Bawse===
 Goal: Now that we are sending out emails based on user events, let's make sure that they're as effective as can be. Lead: Andrea: Collaborators: Jbuck (infra), Aki (figure out HTML emails), Sabrina (design), Drushka (words) Deliverables: * Review existing emails for engagement ladder * Add "email drafting" to the Encyclopedia Best Practica * Design attractive HTML emails sent from Webmaker.org * Build proper HTML email delivery for Webmaker postal service 

=== Building a Webmaker QA Community ===
Time: Wednesday 12:30 
Lead: Jbuck 
The QA community has begun to make tests for Webmaker.org (see https://github.com/mozilla/webmaker-tests/issues/37#issuecomment-41444213)
Let's keep the momentum going and get setup within MozQA systems like MozTrap, chart out what the next set of automated tests should be, and get some advice about how to outreach to the existing QA community.
 
Collaborators: rbillings, JP, Cade 
Deliverables:
Setting up Webmaker in MozTrap 
Creating Webmaker tests in MozTrap 
Creating Webmaker tasks in "one and done" 
Deciding what the next appropriate automated test would be 

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/9csx7tfm.png

AllHands/Funnel Inside

2014-04-26T05:52:52Z

Brett Gaylor: /* Building a Webmaker QA Community */

[[File:Funnel Inside.png|225px|right]]
===Learning from Users: getting good at usability testing===
Time: 9:30 Wednesday
 Let's do usability testing on our engagement ladder, to see where people are getting stuck and increase our conversation rate. Our engagement ladder is everything. We're asking users to perform a small number of key calls to action (like signing up for a   Webmaker  account, sharing a teaching kit, entering an event into our platform, etc.) How do we do smart usability testing against these tasks so we can see where users are getting stuck -- and capture quick wins to increase our conversion rate?  Context: http://mzl.la/Pu9ulB + http://openmatt.org/2014/04/04/product_testing/ Lead: Cassie/Karen Smith Collaborators: Cori Schauer  + Tony Santos (User research) + Kat Deliverable: Run a usability test for account creation, event creation, and the new /explore page. 

===Prepping the Webmaker/explore writing sprint===
Prepping for a book sprint to create an open "textbook" or "cookbook" for teaching web literacy. Let's get our roadmap ready for shipping awesome Webmaker teaching curriculum. Toronto will host a writing sprint May 7,8,9 to complete webmaker.org/explore.  Recognizing this piece of content is crucial to our successful launch this summer, we need to hit the ground running. We will make sure each attendees has an assigned Web Lit competency and  that the work is scoped so we can spend a full three days writing Lead (for prep and logistics): Matt Collaborators: Kat, Michelle, Claw, Cassie, Kate, Drushka, Fuzzy Deliverable: Document our roadmap. For shipping the textbook, plus celebrating the community contributing to it. (Kat's Webmaker series) 

===Prototyping together===
'''How to tell and sell the difference between prototype and product'''. Let's work out a process for how we turn prototypes into product that will keep us agile while allowing us to meet our current commitments. We did great work last quarter turning the Web Lit Map into an exciting content direction.  We've got great new extensions for the browser,  3rd   party app integration and more coming up. Let's keep this going,  and  also be clear about expectations for sales, partnerships, and   productization. Lead: Brett 
Collaborators: Atul, WebmakerUX team, Doug, Paula, Dev team, Fuzzy, Chloe, Mike Larrson, Jess Deliverable:  * Documentation for the life cycle of a prototype.  * Documentation for how to talk about and "sell" key current protoypes like the Web Lit Mapper.  

===Appmaker: Getting Input on User Value&nbsp===
Time: 9:30-12:30 Wednesday 
 Goal: test Appmaker strategy against MoCo market research team analysis of the opportunity and need. Plus review user demographics and operators in each  Firefox OS market. We think there are gains in combining platform, marketplace, digital literacy. Are we teed up to provide value here? 
MoFo point: Bobby (+Ben) SF local  contacts: Ria Joy, if we can get her to come from Seattle, Cori Schauer (conflicts with user research session at same time, Cori available wed 9-11) Proposed length: 4-6 hours Deliverable:  
* Document Appmaker audience segmentation & analysis
* Document work plan for feeding audience research into Appmaker product strategy

===Working with the GSMA===
Time: 12:30-4:30 Wednesday 
 Goal: design first set of engagements w/ GSMA around Spreadtrum phone, Appmaker, Webmaker. Plus produce a 15 slide aligment deck for internal stakeholders MoFo point: Mark (+Ben) SF  local contacts: Pete Scanlon, Ria Joy, Rick  Fant (a meeting at some point?), someone from  Bill Walker org, someone  from Christopher Lee org, Irina Sandu (voice?)  David Palomino (voice?) Proposed length: 4-6 hours Deliverable:  * Ship internal slide deck on the mobile development opportunity for Mozilla  * Scope 3 actionable demo collaborations between MoCo + MoFo 

===Review and iterate Webmaker.org information architecture===
 Goal: Take stock of all the pages on webmaker.org. Are they serving our needs? Where are there gaps? How might we improve our information architecture to support new pages like /explore and profiles? And how can we measure if its working? Lead: Cassie Collaborators: Matt, Kat, Kate, Adam Deliverable: A complete list of all current pages with "jobs" and notes on next steps for each Resource: Google doc: [https://docs.google.com/spreadsheets/d/1ejFHysKOLEGXynU6ZUQgUKn5AVlNgqDBtjrTyM8Zbk4/edit#gid=0 Every Page Has a Job] 

===Email like a Bawse===
 Goal: Now that we are sending out emails based on user events, let's make sure that they're as effective as can be. Lead: Andrea: Collaborators: Jbuck (infra), Aki (figure out HTML emails), Sabrina (design), Drushka (words) Deliverables: * Review existing emails for engagement ladder * Add "email drafting" to the Encyclopedia Best Practica * Design attractive HTML emails sent from Webmaker.org * Build proper HTML email delivery for Webmaker postal service 

=== Building a Webmaker QA Community ===
Time: Wednesday 12:30 
Lead: Jbuck 
The QA community has begun to make tests for Webmaker.org (see https://github.com/mozilla/webmaker-tests/issues/37#issuecomment-41444213)
Let's keep the momentum going and get setup within MozQA systems like MozTrap, chart out what the next set of automated tests should be, and get some advice about how to outreach to the existing QA community.
 
Collaborators: rbillings, JP, Cade 
Deliverables:
Setting up Webmaker in MozTrap 
Creating Webmaker tests in MozTrap 
Creating Webmaker tasks in "one and done" 
Deciding what the next appropriate automated test would be 

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/9csx7tfm.png

AllHands/Funnel Inside

2014-04-26T05:52:12Z

Brett Gaylor: /* Building a Webmaker QA Community */

[[File:Funnel Inside.png|225px|right]]
===Learning from Users: getting good at usability testing===
Time: 9:30 Wednesday
 Let's do usability testing on our engagement ladder, to see where people are getting stuck and increase our conversation rate. Our engagement ladder is everything. We're asking users to perform a small number of key calls to action (like signing up for a   Webmaker  account, sharing a teaching kit, entering an event into our platform, etc.) How do we do smart usability testing against these tasks so we can see where users are getting stuck -- and capture quick wins to increase our conversion rate?  Context: http://mzl.la/Pu9ulB + http://openmatt.org/2014/04/04/product_testing/ Lead: Cassie/Karen Smith Collaborators: Cori Schauer  + Tony Santos (User research) + Kat Deliverable: Run a usability test for account creation, event creation, and the new /explore page. 

===Prepping the Webmaker/explore writing sprint===
Prepping for a book sprint to create an open "textbook" or "cookbook" for teaching web literacy. Let's get our roadmap ready for shipping awesome Webmaker teaching curriculum. Toronto will host a writing sprint May 7,8,9 to complete webmaker.org/explore.  Recognizing this piece of content is crucial to our successful launch this summer, we need to hit the ground running. We will make sure each attendees has an assigned Web Lit competency and  that the work is scoped so we can spend a full three days writing Lead (for prep and logistics): Matt Collaborators: Kat, Michelle, Claw, Cassie, Kate, Drushka, Fuzzy Deliverable: Document our roadmap. For shipping the textbook, plus celebrating the community contributing to it. (Kat's Webmaker series) 

===Prototyping together===
'''How to tell and sell the difference between prototype and product'''. Let's work out a process for how we turn prototypes into product that will keep us agile while allowing us to meet our current commitments. We did great work last quarter turning the Web Lit Map into an exciting content direction.  We've got great new extensions for the browser,  3rd   party app integration and more coming up. Let's keep this going,  and  also be clear about expectations for sales, partnerships, and   productization. Lead: Brett 
Collaborators: Atul, WebmakerUX team, Doug, Paula, Dev team, Fuzzy, Chloe, Mike Larrson, Jess Deliverable:  * Documentation for the life cycle of a prototype.  * Documentation for how to talk about and "sell" key current protoypes like the Web Lit Mapper.  

===Appmaker: Getting Input on User Value&nbsp===
Time: 9:30-12:30 Wednesday 
 Goal: test Appmaker strategy against MoCo market research team analysis of the opportunity and need. Plus review user demographics and operators in each  Firefox OS market. We think there are gains in combining platform, marketplace, digital literacy. Are we teed up to provide value here? 
MoFo point: Bobby (+Ben) SF local  contacts: Ria Joy, if we can get her to come from Seattle, Cori Schauer (conflicts with user research session at same time, Cori available wed 9-11) Proposed length: 4-6 hours Deliverable:  
* Document Appmaker audience segmentation & analysis
* Document work plan for feeding audience research into Appmaker product strategy

===Working with the GSMA===
Time: 12:30-4:30 Wednesday 
 Goal: design first set of engagements w/ GSMA around Spreadtrum phone, Appmaker, Webmaker. Plus produce a 15 slide aligment deck for internal stakeholders MoFo point: Mark (+Ben) SF  local contacts: Pete Scanlon, Ria Joy, Rick  Fant (a meeting at some point?), someone from  Bill Walker org, someone  from Christopher Lee org, Irina Sandu (voice?)  David Palomino (voice?) Proposed length: 4-6 hours Deliverable:  * Ship internal slide deck on the mobile development opportunity for Mozilla  * Scope 3 actionable demo collaborations between MoCo + MoFo 

===Review and iterate Webmaker.org information architecture===
 Goal: Take stock of all the pages on webmaker.org. Are they serving our needs? Where are there gaps? How might we improve our information architecture to support new pages like /explore and profiles? And how can we measure if its working? Lead: Cassie Collaborators: Matt, Kat, Kate, Adam Deliverable: A complete list of all current pages with "jobs" and notes on next steps for each Resource: Google doc: [https://docs.google.com/spreadsheets/d/1ejFHysKOLEGXynU6ZUQgUKn5AVlNgqDBtjrTyM8Zbk4/edit#gid=0 Every Page Has a Job] 

===Email like a Bawse===
 Goal: Now that we are sending out emails based on user events, let's make sure that they're as effective as can be. Lead: Andrea: Collaborators: Jbuck (infra), Aki (figure out HTML emails), Sabrina (design), Drushka (words) Deliverables: * Review existing emails for engagement ladder * Add "email drafting" to the Encyclopedia Best Practica * Design attractive HTML emails sent from Webmaker.org * Build proper HTML email delivery for Webmaker postal service 

=== Building a Webmaker QA Community ===
Time: Wednesday 12:30 
Lead: Jbuck 
The QA community has begun to make tests for Webmaker.org (see https://github.com/mozilla/webmaker-tests/issues/37#issuecomment-41444213)
Let's keep the momentum going and get setup within MozQA systems like MozTrap, chart out what the next set of automated tests should be, and get some advice about how to outreach to the existing QA community.
 
Collaborators: rbillings, JP, Cade 
Deliverables:
Setting up Webmaker in MozTrap 
Creating Webmaker tests in MozTrap 
Creating Webmaker tasks in "one and done" 

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/9csx7tfm.png

AllHands/Funnel Inside

2014-04-26T05:51:40Z

Brett Gaylor: /* Building a Webmaker QA Community */

[[File:Funnel Inside.png|225px|right]]
===Learning from Users: getting good at usability testing===
Time: 9:30 Wednesday
 Let's do usability testing on our engagement ladder, to see where people are getting stuck and increase our conversation rate. Our engagement ladder is everything. We're asking users to perform a small number of key calls to action (like signing up for a   Webmaker  account, sharing a teaching kit, entering an event into our platform, etc.) How do we do smart usability testing against these tasks so we can see where users are getting stuck -- and capture quick wins to increase our conversion rate?  Context: http://mzl.la/Pu9ulB + http://openmatt.org/2014/04/04/product_testing/ Lead: Cassie/Karen Smith Collaborators: Cori Schauer  + Tony Santos (User research) + Kat Deliverable: Run a usability test for account creation, event creation, and the new /explore page. 

===Prepping the Webmaker/explore writing sprint===
Prepping for a book sprint to create an open "textbook" or "cookbook" for teaching web literacy. Let's get our roadmap ready for shipping awesome Webmaker teaching curriculum. Toronto will host a writing sprint May 7,8,9 to complete webmaker.org/explore.  Recognizing this piece of content is crucial to our successful launch this summer, we need to hit the ground running. We will make sure each attendees has an assigned Web Lit competency and  that the work is scoped so we can spend a full three days writing Lead (for prep and logistics): Matt Collaborators: Kat, Michelle, Claw, Cassie, Kate, Drushka, Fuzzy Deliverable: Document our roadmap. For shipping the textbook, plus celebrating the community contributing to it. (Kat's Webmaker series) 

===Prototyping together===
'''How to tell and sell the difference between prototype and product'''. Let's work out a process for how we turn prototypes into product that will keep us agile while allowing us to meet our current commitments. We did great work last quarter turning the Web Lit Map into an exciting content direction.  We've got great new extensions for the browser,  3rd   party app integration and more coming up. Let's keep this going,  and  also be clear about expectations for sales, partnerships, and   productization. Lead: Brett 
Collaborators: Atul, WebmakerUX team, Doug, Paula, Dev team, Fuzzy, Chloe, Mike Larrson, Jess Deliverable:  * Documentation for the life cycle of a prototype.  * Documentation for how to talk about and "sell" key current protoypes like the Web Lit Mapper.  

===Appmaker: Getting Input on User Value&nbsp===
Time: 9:30-12:30 Wednesday 
 Goal: test Appmaker strategy against MoCo market research team analysis of the opportunity and need. Plus review user demographics and operators in each  Firefox OS market. We think there are gains in combining platform, marketplace, digital literacy. Are we teed up to provide value here? 
MoFo point: Bobby (+Ben) SF local  contacts: Ria Joy, if we can get her to come from Seattle, Cori Schauer (conflicts with user research session at same time, Cori available wed 9-11) Proposed length: 4-6 hours Deliverable:  
* Document Appmaker audience segmentation & analysis
* Document work plan for feeding audience research into Appmaker product strategy

===Working with the GSMA===
Time: 12:30-4:30 Wednesday 
 Goal: design first set of engagements w/ GSMA around Spreadtrum phone, Appmaker, Webmaker. Plus produce a 15 slide aligment deck for internal stakeholders MoFo point: Mark (+Ben) SF  local contacts: Pete Scanlon, Ria Joy, Rick  Fant (a meeting at some point?), someone from  Bill Walker org, someone  from Christopher Lee org, Irina Sandu (voice?)  David Palomino (voice?) Proposed length: 4-6 hours Deliverable:  * Ship internal slide deck on the mobile development opportunity for Mozilla  * Scope 3 actionable demo collaborations between MoCo + MoFo 

===Review and iterate Webmaker.org information architecture===
 Goal: Take stock of all the pages on webmaker.org. Are they serving our needs? Where are there gaps? How might we improve our information architecture to support new pages like /explore and profiles? And how can we measure if its working? Lead: Cassie Collaborators: Matt, Kat, Kate, Adam Deliverable: A complete list of all current pages with "jobs" and notes on next steps for each Resource: Google doc: [https://docs.google.com/spreadsheets/d/1ejFHysKOLEGXynU6ZUQgUKn5AVlNgqDBtjrTyM8Zbk4/edit#gid=0 Every Page Has a Job] 

===Email like a Bawse===
 Goal: Now that we are sending out emails based on user events, let's make sure that they're as effective as can be. Lead: Andrea: Collaborators: Jbuck (infra), Aki (figure out HTML emails), Sabrina (design), Drushka (words) Deliverables: * Review existing emails for engagement ladder * Add "email drafting" to the Encyclopedia Best Practica * Design attractive HTML emails sent from Webmaker.org * Build proper HTML email delivery for Webmaker postal service 

=== Building a Webmaker QA Community ===
Time: Wednesday 12:30 
Lead: Jbuck 
The QA community has begun to make tests for Webmaker.org (see https://github.com/mozilla/webmaker-tests/issues/37#issuecomment-41444213)
Let's get setup within MozQA systems like MozTrap, chart out what the next set of automated tests should be, and get some advice about how to outreach to the existing QA community.
 
Collaborators: rbillings, JP, Cade 
Deliverables:
Setting up Webmaker in MozTrap 
Creating Webmaker tests in MozTrap 
Creating Webmaker tasks in "one and done" 

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/9csx7tfm.png

AllHands/Funnel Inside

2014-04-26T05:51:23Z

Brett Gaylor: /* Building a Webmaker QA Community */

[[File:Funnel Inside.png|225px|right]]
===Learning from Users: getting good at usability testing===
Time: 9:30 Wednesday
 Let's do usability testing on our engagement ladder, to see where people are getting stuck and increase our conversation rate. Our engagement ladder is everything. We're asking users to perform a small number of key calls to action (like signing up for a   Webmaker  account, sharing a teaching kit, entering an event into our platform, etc.) How do we do smart usability testing against these tasks so we can see where users are getting stuck -- and capture quick wins to increase our conversion rate?  Context: http://mzl.la/Pu9ulB + http://openmatt.org/2014/04/04/product_testing/ Lead: Cassie/Karen Smith Collaborators: Cori Schauer  + Tony Santos (User research) + Kat Deliverable: Run a usability test for account creation, event creation, and the new /explore page. 

===Prepping the Webmaker/explore writing sprint===
Prepping for a book sprint to create an open "textbook" or "cookbook" for teaching web literacy. Let's get our roadmap ready for shipping awesome Webmaker teaching curriculum. Toronto will host a writing sprint May 7,8,9 to complete webmaker.org/explore.  Recognizing this piece of content is crucial to our successful launch this summer, we need to hit the ground running. We will make sure each attendees has an assigned Web Lit competency and  that the work is scoped so we can spend a full three days writing Lead (for prep and logistics): Matt Collaborators: Kat, Michelle, Claw, Cassie, Kate, Drushka, Fuzzy Deliverable: Document our roadmap. For shipping the textbook, plus celebrating the community contributing to it. (Kat's Webmaker series) 

===Prototyping together===
'''How to tell and sell the difference between prototype and product'''. Let's work out a process for how we turn prototypes into product that will keep us agile while allowing us to meet our current commitments. We did great work last quarter turning the Web Lit Map into an exciting content direction.  We've got great new extensions for the browser,  3rd   party app integration and more coming up. Let's keep this going,  and  also be clear about expectations for sales, partnerships, and   productization. Lead: Brett 
Collaborators: Atul, WebmakerUX team, Doug, Paula, Dev team, Fuzzy, Chloe, Mike Larrson, Jess Deliverable:  * Documentation for the life cycle of a prototype.  * Documentation for how to talk about and "sell" key current protoypes like the Web Lit Mapper.  

===Appmaker: Getting Input on User Value&nbsp===
Time: 9:30-12:30 Wednesday 
 Goal: test Appmaker strategy against MoCo market research team analysis of the opportunity and need. Plus review user demographics and operators in each  Firefox OS market. We think there are gains in combining platform, marketplace, digital literacy. Are we teed up to provide value here? 
MoFo point: Bobby (+Ben) SF local  contacts: Ria Joy, if we can get her to come from Seattle, Cori Schauer (conflicts with user research session at same time, Cori available wed 9-11) Proposed length: 4-6 hours Deliverable:  
* Document Appmaker audience segmentation & analysis
* Document work plan for feeding audience research into Appmaker product strategy

===Working with the GSMA===
Time: 12:30-4:30 Wednesday 
 Goal: design first set of engagements w/ GSMA around Spreadtrum phone, Appmaker, Webmaker. Plus produce a 15 slide aligment deck for internal stakeholders MoFo point: Mark (+Ben) SF  local contacts: Pete Scanlon, Ria Joy, Rick  Fant (a meeting at some point?), someone from  Bill Walker org, someone  from Christopher Lee org, Irina Sandu (voice?)  David Palomino (voice?) Proposed length: 4-6 hours Deliverable:  * Ship internal slide deck on the mobile development opportunity for Mozilla  * Scope 3 actionable demo collaborations between MoCo + MoFo 

===Review and iterate Webmaker.org information architecture===
 Goal: Take stock of all the pages on webmaker.org. Are they serving our needs? Where are there gaps? How might we improve our information architecture to support new pages like /explore and profiles? And how can we measure if its working? Lead: Cassie Collaborators: Matt, Kat, Kate, Adam Deliverable: A complete list of all current pages with "jobs" and notes on next steps for each Resource: Google doc: [https://docs.google.com/spreadsheets/d/1ejFHysKOLEGXynU6ZUQgUKn5AVlNgqDBtjrTyM8Zbk4/edit#gid=0 Every Page Has a Job] 

===Email like a Bawse===
 Goal: Now that we are sending out emails based on user events, let's make sure that they're as effective as can be. Lead: Andrea: Collaborators: Jbuck (infra), Aki (figure out HTML emails), Sabrina (design), Drushka (words) Deliverables: * Review existing emails for engagement ladder * Add "email drafting" to the Encyclopedia Best Practica * Design attractive HTML emails sent from Webmaker.org * Build proper HTML email delivery for Webmaker postal service 

=== Building a Webmaker QA Community ===
Time: Wednesday 12:30
Lead: Jbuck 
The QA community has begun to make tests for Webmaker.org (see https://github.com/mozilla/webmaker-tests/issues/37#issuecomment-41444213)
Let's get setup within MozQA systems like MozTrap, chart out what the next set of automated tests should be, and get some advice about how to outreach to the existing QA community.
 
Collaborators: rbillings, JP, Cade 
Deliverables:
Setting up Webmaker in MozTrap 
Creating Webmaker tests in MozTrap 
Creating Webmaker tasks in "one and done" 

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/9csx7tfm.png

AllHands/Funnel Inside

2014-04-26T05:41:54Z

Brett Gaylor: /* Building a Webmaker QA Community */

[[File:Funnel Inside.png|225px|right]]
===Learning from Users: getting good at usability testing===
Time: 9:30 Wednesday
 Let's do usability testing on our engagement ladder, to see where people are getting stuck and increase our conversation rate. Our engagement ladder is everything. We're asking users to perform a small number of key calls to action (like signing up for a   Webmaker  account, sharing a teaching kit, entering an event into our platform, etc.) How do we do smart usability testing against these tasks so we can see where users are getting stuck -- and capture quick wins to increase our conversion rate?  Context: http://mzl.la/Pu9ulB + http://openmatt.org/2014/04/04/product_testing/ Lead: Cassie/Karen Smith Collaborators: Cori Schauer  + Tony Santos (User research) + Kat Deliverable: Run a usability test for account creation, event creation, and the new /explore page. 

===Prepping the Webmaker/explore writing sprint===
Prepping for a book sprint to create an open "textbook" or "cookbook" for teaching web literacy. Let's get our roadmap ready for shipping awesome Webmaker teaching curriculum. Toronto will host a writing sprint May 7,8,9 to complete webmaker.org/explore.  Recognizing this piece of content is crucial to our successful launch this summer, we need to hit the ground running. We will make sure each attendees has an assigned Web Lit competency and  that the work is scoped so we can spend a full three days writing Lead (for prep and logistics): Matt Collaborators: Kat, Michelle, Claw, Cassie, Kate, Drushka, Fuzzy Deliverable: Document our roadmap. For shipping the textbook, plus celebrating the community contributing to it. (Kat's Webmaker series) 

===Prototyping together===
'''How to tell and sell the difference between prototype and product'''. Let's work out a process for how we turn prototypes into product that will keep us agile while allowing us to meet our current commitments. We did great work last quarter turning the Web Lit Map into an exciting content direction.  We've got great new extensions for the browser,  3rd   party app integration and more coming up. Let's keep this going,  and  also be clear about expectations for sales, partnerships, and   productization. Lead: Brett 
Collaborators: Atul, WebmakerUX team, Doug, Paula, Dev team, Fuzzy, Chloe, Mike Larrson, Jess Deliverable:  * Documentation for the life cycle of a prototype.  * Documentation for how to talk about and "sell" key current protoypes like the Web Lit Mapper.  

===Appmaker: Getting Input on User Value&nbsp===
Time: 9:30-12:30 Wednesday 
 Goal: test Appmaker strategy against MoCo market research team analysis of the opportunity and need. Plus review user demographics and operators in each  Firefox OS market. We think there are gains in combining platform, marketplace, digital literacy. Are we teed up to provide value here? 
MoFo point: Bobby (+Ben) SF local  contacts: Ria Joy, if we can get her to come from Seattle, Cori Schauer (conflicts with user research session at same time, Cori available wed 9-11) Proposed length: 4-6 hours Deliverable:  
* Document Appmaker audience segmentation & analysis
* Document work plan for feeding audience research into Appmaker product strategy

===Working with the GSMA===
Time: 12:30-4:30 Wednesday 
 Goal: design first set of engagements w/ GSMA around Spreadtrum phone, Appmaker, Webmaker. Plus produce a 15 slide aligment deck for internal stakeholders MoFo point: Mark (+Ben) SF  local contacts: Pete Scanlon, Ria Joy, Rick  Fant (a meeting at some point?), someone from  Bill Walker org, someone  from Christopher Lee org, Irina Sandu (voice?)  David Palomino (voice?) Proposed length: 4-6 hours Deliverable:  * Ship internal slide deck on the mobile development opportunity for Mozilla  * Scope 3 actionable demo collaborations between MoCo + MoFo 

===Review and iterate Webmaker.org information architecture===
 Goal: Take stock of all the pages on webmaker.org. Are they serving our needs? Where are there gaps? How might we improve our information architecture to support new pages like /explore and profiles? And how can we measure if its working? Lead: Cassie Collaborators: Matt, Kat, Kate, Adam Deliverable: A complete list of all current pages with "jobs" and notes on next steps for each Resource: Google doc: [https://docs.google.com/spreadsheets/d/1ejFHysKOLEGXynU6ZUQgUKn5AVlNgqDBtjrTyM8Zbk4/edit#gid=0 Every Page Has a Job] 

===Email like a Bawse===
 Goal: Now that we are sending out emails based on user events, let's make sure that they're as effective as can be. Lead: Andrea: Collaborators: Jbuck (infra), Aki (figure out HTML emails), Sabrina (design), Drushka (words) Deliverables: * Review existing emails for engagement ladder * Add "email drafting" to the Encyclopedia Best Practica * Design attractive HTML emails sent from Webmaker.org * Build proper HTML email delivery for Webmaker postal service 

=== Building a Webmaker QA Community ===
Lead: Jbuck 
The QA community has begun to make tests for Webmaker.org (see https://github.com/mozilla/webmaker-tests/issues/37#issuecomment-41444213)
Let's get setup within MozQA systems like MozTrap, chart out what the next set of automated tests should be, and get some advice about how to outreach to the existing QA community.
 
Collaborators: rbillings, JP, Cade 
Deliverables:
Setting up Webmaker in MozTrap 
Creating Webmaker tests in MozTrap 
Creating Webmaker tasks in "one and done" 

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/9csx7tfm.png

AllHands/Funnel Inside

2014-04-26T05:41:31Z

Brett Gaylor: /* Building a QA Community */

[[File:Funnel Inside.png|225px|right]]
===Learning from Users: getting good at usability testing===
Time: 9:30 Wednesday
 Let's do usability testing on our engagement ladder, to see where people are getting stuck and increase our conversation rate. Our engagement ladder is everything. We're asking users to perform a small number of key calls to action (like signing up for a   Webmaker  account, sharing a teaching kit, entering an event into our platform, etc.) How do we do smart usability testing against these tasks so we can see where users are getting stuck -- and capture quick wins to increase our conversion rate?  Context: http://mzl.la/Pu9ulB + http://openmatt.org/2014/04/04/product_testing/ Lead: Cassie/Karen Smith Collaborators: Cori Schauer  + Tony Santos (User research) + Kat Deliverable: Run a usability test for account creation, event creation, and the new /explore page. 

===Prepping the Webmaker/explore writing sprint===
Prepping for a book sprint to create an open "textbook" or "cookbook" for teaching web literacy. Let's get our roadmap ready for shipping awesome Webmaker teaching curriculum. Toronto will host a writing sprint May 7,8,9 to complete webmaker.org/explore.  Recognizing this piece of content is crucial to our successful launch this summer, we need to hit the ground running. We will make sure each attendees has an assigned Web Lit competency and  that the work is scoped so we can spend a full three days writing Lead (for prep and logistics): Matt Collaborators: Kat, Michelle, Claw, Cassie, Kate, Drushka, Fuzzy Deliverable: Document our roadmap. For shipping the textbook, plus celebrating the community contributing to it. (Kat's Webmaker series) 

===Prototyping together===
'''How to tell and sell the difference between prototype and product'''. Let's work out a process for how we turn prototypes into product that will keep us agile while allowing us to meet our current commitments. We did great work last quarter turning the Web Lit Map into an exciting content direction.  We've got great new extensions for the browser,  3rd   party app integration and more coming up. Let's keep this going,  and  also be clear about expectations for sales, partnerships, and   productization. Lead: Brett 
Collaborators: Atul, WebmakerUX team, Doug, Paula, Dev team, Fuzzy, Chloe, Mike Larrson, Jess Deliverable:  * Documentation for the life cycle of a prototype.  * Documentation for how to talk about and "sell" key current protoypes like the Web Lit Mapper.  

===Appmaker: Getting Input on User Value&nbsp===
Time: 9:30-12:30 Wednesday 
 Goal: test Appmaker strategy against MoCo market research team analysis of the opportunity and need. Plus review user demographics and operators in each  Firefox OS market. We think there are gains in combining platform, marketplace, digital literacy. Are we teed up to provide value here? 
MoFo point: Bobby (+Ben) SF local  contacts: Ria Joy, if we can get her to come from Seattle, Cori Schauer (conflicts with user research session at same time, Cori available wed 9-11) Proposed length: 4-6 hours Deliverable:  
* Document Appmaker audience segmentation & analysis
* Document work plan for feeding audience research into Appmaker product strategy

===Working with the GSMA===
Time: 12:30-4:30 Wednesday 
 Goal: design first set of engagements w/ GSMA around Spreadtrum phone, Appmaker, Webmaker. Plus produce a 15 slide aligment deck for internal stakeholders MoFo point: Mark (+Ben) SF  local contacts: Pete Scanlon, Ria Joy, Rick  Fant (a meeting at some point?), someone from  Bill Walker org, someone  from Christopher Lee org, Irina Sandu (voice?)  David Palomino (voice?) Proposed length: 4-6 hours Deliverable:  * Ship internal slide deck on the mobile development opportunity for Mozilla  * Scope 3 actionable demo collaborations between MoCo + MoFo 

===Review and iterate Webmaker.org information architecture===
 Goal: Take stock of all the pages on webmaker.org. Are they serving our needs? Where are there gaps? How might we improve our information architecture to support new pages like /explore and profiles? And how can we measure if its working? Lead: Cassie Collaborators: Matt, Kat, Kate, Adam Deliverable: A complete list of all current pages with "jobs" and notes on next steps for each Resource: Google doc: [https://docs.google.com/spreadsheets/d/1ejFHysKOLEGXynU6ZUQgUKn5AVlNgqDBtjrTyM8Zbk4/edit#gid=0 Every Page Has a Job] 

===Email like a Bawse===
 Goal: Now that we are sending out emails based on user events, let's make sure that they're as effective as can be. Lead: Andrea: Collaborators: Jbuck (infra), Aki (figure out HTML emails), Sabrina (design), Drushka (words) Deliverables: * Review existing emails for engagement ladder * Add "email drafting" to the Encyclopedia Best Practica * Design attractive HTML emails sent from Webmaker.org * Build proper HTML email delivery for Webmaker postal service 

=== Building a Webmaker QA Community ===
Lead: Jbuck 
The QA community has begun to make tests for Webmaker.org (see https://github.com/mozilla/webmaker-tests/issues/37#issuecomment-41444213)
Let's get setup within MozQA systems like MozTrap, chart out what the next set of automated tests should be, and get some advice about how to outreach to the existing QA community.
 
Collaborators: rbillings, JP, Cade 
Deliverables:
Setting up Webmaker in MozTrap
Creating Webmaker tests in MozTrap
Creating Webmaker tasks in "one and done"

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/9csx7tfm.png

AllHands/Funnel Inside

2014-04-26T05:19:47Z

Brett Gaylor: /* Learning from Users: getting good at usability testing */

[[File:Funnel Inside.png|225px|right]]
===Learning from Users: getting good at usability testing===
Time: 9:30 Wednesday
 Let's do usability testing on our engagement ladder, to see where people are getting stuck and increase our conversation rate. Our engagement ladder is everything. We're asking users to perform a small number of key calls to action (like signing up for a   Webmaker  account, sharing a teaching kit, entering an event into our platform, etc.) How do we do smart usability testing against these tasks so we can see where users are getting stuck -- and capture quick wins to increase our conversion rate?  Context: http://mzl.la/Pu9ulB + http://openmatt.org/2014/04/04/product_testing/ Lead: Cassie/Karen Smith Collaborators: Cori Schauer  + Tony Santos (User research) + Kat Deliverable: Run a usability test for account creation, event creation, and the new /explore page. 

===Prepping the Webmaker/explore writing sprint===
Prepping for a book sprint to create an open "textbook" or "cookbook" for teaching web literacy. Let's get our roadmap ready for shipping awesome Webmaker teaching curriculum. Toronto will host a writing sprint May 7,8,9 to complete webmaker.org/explore.  Recognizing this piece of content is crucial to our successful launch this summer, we need to hit the ground running. We will make sure each attendees has an assigned Web Lit competency and  that the work is scoped so we can spend a full three days writing Lead (for prep and logistics): Matt Collaborators: Kat, Michelle, Claw, Cassie, Kate, Drushka, Fuzzy Deliverable: Document our roadmap. For shipping the textbook, plus celebrating the community contributing to it. (Kat's Webmaker series) 

===Prototyping together===
'''How to tell and sell the difference between prototype and product'''. Let's work out a process for how we turn prototypes into product that will keep us agile while allowing us to meet our current commitments. We did great work last quarter turning the Web Lit Map into an exciting content direction.  We've got great new extensions for the browser,  3rd   party app integration and more coming up. Let's keep this going,  and  also be clear about expectations for sales, partnerships, and   productization. Lead: Brett 
Collaborators: Atul, WebmakerUX team, Doug, Paula, Dev team, Fuzzy, Chloe, Mike Larrson, Jess Deliverable:  * Documentation for the life cycle of a prototype.  * Documentation for how to talk about and "sell" key current protoypes like the Web Lit Mapper.  

===Appmaker: Getting Input on User Value&nbsp===
Time: 9:30-12:30 Wednesday 
 Goal: test Appmaker strategy against MoCo market research team analysis of the opportunity and need. Plus review user demographics and operators in each  Firefox OS market. We think there are gains in combining platform, marketplace, digital literacy. Are we teed up to provide value here? 
MoFo point: Bobby (+Ben) SF local  contacts: Ria Joy, if we can get her to come from Seattle, Cori Schauer (conflicts with user research session at same time, Cori available wed 9-11) Proposed length: 4-6 hours Deliverable:  
* Document Appmaker audience segmentation & analysis
* Document work plan for feeding audience research into Appmaker product strategy

===Working with the GSMA===
Time: 12:30-4:30 Wednesday 
 Goal: design first set of engagements w/ GSMA around Spreadtrum phone, Appmaker, Webmaker. Plus produce a 15 slide aligment deck for internal stakeholders MoFo point: Mark (+Ben) SF  local contacts: Pete Scanlon, Ria Joy, Rick  Fant (a meeting at some point?), someone from  Bill Walker org, someone  from Christopher Lee org, Irina Sandu (voice?)  David Palomino (voice?) Proposed length: 4-6 hours Deliverable:  * Ship internal slide deck on the mobile development opportunity for Mozilla  * Scope 3 actionable demo collaborations between MoCo + MoFo 

===Review and iterate Webmaker.org information architecture===
 Goal: Take stock of all the pages on webmaker.org. Are they serving our needs? Where are there gaps? How might we improve our information architecture to support new pages like /explore and profiles? And how can we measure if its working? Lead: Cassie Collaborators: Matt, Kat, Kate, Adam Deliverable: A complete list of all current pages with "jobs" and notes on next steps for each Resource: Google doc: [https://docs.google.com/spreadsheets/d/1ejFHysKOLEGXynU6ZUQgUKn5AVlNgqDBtjrTyM8Zbk4/edit#gid=0 Every Page Has a Job] 

===Email like a Bawse===
 Goal: Now that we are sending out emails based on user events, let's make sure that they're as effective as can be. Lead: Andrea: Collaborators: Jbuck (infra), Aki (figure out HTML emails), Sabrina (design), Drushka (words) Deliverables: * Review existing emails for engagement ladder * Add "email drafting" to the Encyclopedia Best Practica * Design attractive HTML emails sent from Webmaker.org * Build proper HTML email delivery for Webmaker postal service 

=== Building a QA Community ===
Lead: Jbuck 
The QA community has begun to make tests for Webmaker.org (see https://github.com/mozilla/webmaker-tests/issues/37#issuecomment-41444213)
Let's discuss with the QA team how we can build a great community of testers, and also, how to be great at tests.
 
Collaborators: rbillings, JP, Cade 
Deliverables: A set of tickets about what to test next.
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/9csx7tfm.png

AllHands/Funnel Inside

2014-04-26T05:18:46Z

Brett Gaylor: /* Working with the GSMA */

[[File:Funnel Inside.png|225px|right]]
===Learning from Users: getting good at usability testing===
Time: 9:30 Wednesday
 Let's do usability testing on our engagement ladder, to see where people are getting stuck and increase our conversation rate. Our engagement ladder is everything. We're asking users to perform a mall number of key calls to action and (like signing up for a   Webmaker  account, sharing a teaching kit, entering an event into our platform, etc.) How do we do smart usability testing against these tasks so we can see where users are getting stuck -- and capture quick wins to increase our conversion rate?  Context: http://mzl.la/Pu9ulB + http://openmatt.org/2014/04/04/product_testing/ Lead: Cassie/Karen Smith Collaborators: Cori Schauer  + Tony Santos (User research) + Kat Deliverable: Run a usability test for account creation, event creation, and the new /explore page. 

===Prepping the Webmaker/explore writing sprint===
Prepping for a book sprint to create an open "textbook" or "cookbook" for teaching web literacy. Let's get our roadmap ready for shipping awesome Webmaker teaching curriculum. Toronto will host a writing sprint May 7,8,9 to complete webmaker.org/explore.  Recognizing this piece of content is crucial to our successful launch this summer, we need to hit the ground running. We will make sure each attendees has an assigned Web Lit competency and  that the work is scoped so we can spend a full three days writing Lead (for prep and logistics): Matt Collaborators: Kat, Michelle, Claw, Cassie, Kate, Drushka, Fuzzy Deliverable: Document our roadmap. For shipping the textbook, plus celebrating the community contributing to it. (Kat's Webmaker series) 

===Prototyping together===
'''How to tell and sell the difference between prototype and product'''. Let's work out a process for how we turn prototypes into product that will keep us agile while allowing us to meet our current commitments. We did great work last quarter turning the Web Lit Map into an exciting content direction.  We've got great new extensions for the browser,  3rd   party app integration and more coming up. Let's keep this going,  and  also be clear about expectations for sales, partnerships, and   productization. Lead: Brett 
Collaborators: Atul, WebmakerUX team, Doug, Paula, Dev team, Fuzzy, Chloe, Mike Larrson, Jess Deliverable:  * Documentation for the life cycle of a prototype.  * Documentation for how to talk about and "sell" key current protoypes like the Web Lit Mapper.  

===Appmaker: Getting Input on User Value&nbsp===
Time: 9:30-12:30 Wednesday 
 Goal: test Appmaker strategy against MoCo market research team analysis of the opportunity and need. Plus review user demographics and operators in each  Firefox OS market. We think there are gains in combining platform, marketplace, digital literacy. Are we teed up to provide value here? 
MoFo point: Bobby (+Ben) SF local  contacts: Ria Joy, if we can get her to come from Seattle, Cori Schauer (conflicts with user research session at same time, Cori available wed 9-11) Proposed length: 4-6 hours Deliverable:  
* Document Appmaker audience segmentation & analysis
* Document work plan for feeding audience research into Appmaker product strategy

===Working with the GSMA===
Time: 12:30-4:30 Wednesday 
 Goal: design first set of engagements w/ GSMA around Spreadtrum phone, Appmaker, Webmaker. Plus produce a 15 slide aligment deck for internal stakeholders MoFo point: Mark (+Ben) SF  local contacts: Pete Scanlon, Ria Joy, Rick  Fant (a meeting at some point?), someone from  Bill Walker org, someone  from Christopher Lee org, Irina Sandu (voice?)  David Palomino (voice?) Proposed length: 4-6 hours Deliverable:  * Ship internal slide deck on the mobile development opportunity for Mozilla  * Scope 3 actionable demo collaborations between MoCo + MoFo 

===Review and iterate Webmaker.org information architecture===
 Goal: Take stock of all the pages on webmaker.org. Are they serving our needs? Where are there gaps? How might we improve our information architecture to support new pages like /explore and profiles? And how can we measure if its working? Lead: Cassie Collaborators: Matt, Kat, Kate, Adam Deliverable: A complete list of all current pages with "jobs" and notes on next steps for each Resource: Google doc: [https://docs.google.com/spreadsheets/d/1ejFHysKOLEGXynU6ZUQgUKn5AVlNgqDBtjrTyM8Zbk4/edit#gid=0 Every Page Has a Job] 

===Email like a Bawse===
 Goal: Now that we are sending out emails based on user events, let's make sure that they're as effective as can be. Lead: Andrea: Collaborators: Jbuck (infra), Aki (figure out HTML emails), Sabrina (design), Drushka (words) Deliverables: * Review existing emails for engagement ladder * Add "email drafting" to the Encyclopedia Best Practica * Design attractive HTML emails sent from Webmaker.org * Build proper HTML email delivery for Webmaker postal service 

=== Building a QA Community ===
Lead: Jbuck 
The QA community has begun to make tests for Webmaker.org (see https://github.com/mozilla/webmaker-tests/issues/37#issuecomment-41444213)
Let's discuss with the QA team how we can build a great community of testers, and also, how to be great at tests.
 
Collaborators: rbillings, JP, Cade 
Deliverables: A set of tickets about what to test next.
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/9csx7tfm.png

AllHands/Funnel Inside

2014-04-26T05:18:18Z

Brett Gaylor: /* Appmaker: Getting Input on User Value&nbsp */

[[File:Funnel Inside.png|225px|right]]
===Learning from Users: getting good at usability testing===
Time: 9:30 Wednesday
 Let's do usability testing on our engagement ladder, to see where people are getting stuck and increase our conversation rate. Our engagement ladder is everything. We're asking users to perform a mall number of key calls to action and (like signing up for a   Webmaker  account, sharing a teaching kit, entering an event into our platform, etc.) How do we do smart usability testing against these tasks so we can see where users are getting stuck -- and capture quick wins to increase our conversion rate?  Context: http://mzl.la/Pu9ulB + http://openmatt.org/2014/04/04/product_testing/ Lead: Cassie/Karen Smith Collaborators: Cori Schauer  + Tony Santos (User research) + Kat Deliverable: Run a usability test for account creation, event creation, and the new /explore page. 

===Prepping the Webmaker/explore writing sprint===
Prepping for a book sprint to create an open "textbook" or "cookbook" for teaching web literacy. Let's get our roadmap ready for shipping awesome Webmaker teaching curriculum. Toronto will host a writing sprint May 7,8,9 to complete webmaker.org/explore.  Recognizing this piece of content is crucial to our successful launch this summer, we need to hit the ground running. We will make sure each attendees has an assigned Web Lit competency and  that the work is scoped so we can spend a full three days writing Lead (for prep and logistics): Matt Collaborators: Kat, Michelle, Claw, Cassie, Kate, Drushka, Fuzzy Deliverable: Document our roadmap. For shipping the textbook, plus celebrating the community contributing to it. (Kat's Webmaker series) 

===Prototyping together===
'''How to tell and sell the difference between prototype and product'''. Let's work out a process for how we turn prototypes into product that will keep us agile while allowing us to meet our current commitments. We did great work last quarter turning the Web Lit Map into an exciting content direction.  We've got great new extensions for the browser,  3rd   party app integration and more coming up. Let's keep this going,  and  also be clear about expectations for sales, partnerships, and   productization. Lead: Brett 
Collaborators: Atul, WebmakerUX team, Doug, Paula, Dev team, Fuzzy, Chloe, Mike Larrson, Jess Deliverable:  * Documentation for the life cycle of a prototype.  * Documentation for how to talk about and "sell" key current protoypes like the Web Lit Mapper.  

===Appmaker: Getting Input on User Value&nbsp===
Time: 9:30-12:30 Wednesday 
 Goal: test Appmaker strategy against MoCo market research team analysis of the opportunity and need. Plus review user demographics and operators in each  Firefox OS market. We think there are gains in combining platform, marketplace, digital literacy. Are we teed up to provide value here? 
MoFo point: Bobby (+Ben) SF local  contacts: Ria Joy, if we can get her to come from Seattle, Cori Schauer (conflicts with user research session at same time, Cori available wed 9-11) Proposed length: 4-6 hours Deliverable:  
* Document Appmaker audience segmentation & analysis
* Document work plan for feeding audience research into Appmaker product strategy

===Working with the GSMA===
 Goal: design first set of engagements w/ GSMA around Spreadtrum phone, Appmaker, Webmaker. Plus produce a 15 slide aligment deck for internal stakeholders MoFo point: Mark (+Ben) SF  local contacts: Pete Scanlon, Ria Joy, Rick  Fant (a meeting at some point?), someone from  Bill Walker org, someone  from Christopher Lee org, Irina Sandu (voice?)  David Palomino (voice?) Proposed length: 4-6 hours Deliverable:  * Ship internal slide deck on the mobile development opportunity for Mozilla  * Scope 3 actionable demo collaborations between MoCo + MoFo 
===Review and iterate Webmaker.org information architecture===
 Goal: Take stock of all the pages on webmaker.org. Are they serving our needs? Where are there gaps? How might we improve our information architecture to support new pages like /explore and profiles? And how can we measure if its working? Lead: Cassie Collaborators: Matt, Kat, Kate, Adam Deliverable: A complete list of all current pages with "jobs" and notes on next steps for each Resource: Google doc: [https://docs.google.com/spreadsheets/d/1ejFHysKOLEGXynU6ZUQgUKn5AVlNgqDBtjrTyM8Zbk4/edit#gid=0 Every Page Has a Job] 

===Email like a Bawse===
 Goal: Now that we are sending out emails based on user events, let's make sure that they're as effective as can be. Lead: Andrea: Collaborators: Jbuck (infra), Aki (figure out HTML emails), Sabrina (design), Drushka (words) Deliverables: * Review existing emails for engagement ladder * Add "email drafting" to the Encyclopedia Best Practica * Design attractive HTML emails sent from Webmaker.org * Build proper HTML email delivery for Webmaker postal service 

=== Building a QA Community ===
Lead: Jbuck 
The QA community has begun to make tests for Webmaker.org (see https://github.com/mozilla/webmaker-tests/issues/37#issuecomment-41444213)
Let's discuss with the QA team how we can build a great community of testers, and also, how to be great at tests.
 
Collaborators: rbillings, JP, Cade 
Deliverables: A set of tickets about what to test next.
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/9csx7tfm.png

AllHands/Funnel Inside

2014-04-26T05:15:11Z

Brett Gaylor: /* Learning from Users: getting good at usability testing */

[[File:Funnel Inside.png|225px|right]]
===Learning from Users: getting good at usability testing===
Time: 9:30 Wednesday
 Let's do usability testing on our engagement ladder, to see where people are getting stuck and increase our conversation rate. Our engagement ladder is everything. We're asking users to perform a mall number of key calls to action and (like signing up for a   Webmaker  account, sharing a teaching kit, entering an event into our platform, etc.) How do we do smart usability testing against these tasks so we can see where users are getting stuck -- and capture quick wins to increase our conversion rate?  Context: http://mzl.la/Pu9ulB + http://openmatt.org/2014/04/04/product_testing/ Lead: Cassie/Karen Smith Collaborators: Cori Schauer  + Tony Santos (User research) + Kat Deliverable: Run a usability test for account creation, event creation, and the new /explore page. 

===Prepping the Webmaker/explore writing sprint===
Prepping for a book sprint to create an open "textbook" or "cookbook" for teaching web literacy. Let's get our roadmap ready for shipping awesome Webmaker teaching curriculum. Toronto will host a writing sprint May 7,8,9 to complete webmaker.org/explore.  Recognizing this piece of content is crucial to our successful launch this summer, we need to hit the ground running. We will make sure each attendees has an assigned Web Lit competency and  that the work is scoped so we can spend a full three days writing Lead (for prep and logistics): Matt Collaborators: Kat, Michelle, Claw, Cassie, Kate, Drushka, Fuzzy Deliverable: Document our roadmap. For shipping the textbook, plus celebrating the community contributing to it. (Kat's Webmaker series) 

===Prototyping together===
'''How to tell and sell the difference between prototype and product'''. Let's work out a process for how we turn prototypes into product that will keep us agile while allowing us to meet our current commitments. We did great work last quarter turning the Web Lit Map into an exciting content direction.  We've got great new extensions for the browser,  3rd   party app integration and more coming up. Let's keep this going,  and  also be clear about expectations for sales, partnerships, and   productization. Lead: Brett 
Collaborators: Atul, WebmakerUX team, Doug, Paula, Dev team, Fuzzy, Chloe, Mike Larrson, Jess Deliverable:  * Documentation for the life cycle of a prototype.  * Documentation for how to talk about and "sell" key current protoypes like the Web Lit Mapper.  

===Appmaker: Getting Input on User Value&nbsp===
 Goal: test Appmaker strategy against MoCo market research team analysis of the opportunity and need. Plus review user demographics and operators in each  Firefox OS market. We think there are gains in combining platform, marketplace, digital literacy. Are we teed up to provide value here? 
MoFo point: Bobby (+Ben) SF local  contacts: Ria Joy, if we can get her to come from Seattle, Cori Schauer Proposed length: 4-6 hours Deliverable:  
* Document Appmaker audience segmentation & analysis
* Document work plan for feeding audience research into Appmaker product strategy

===Working with the GSMA===
 Goal: design first set of engagements w/ GSMA around Spreadtrum phone, Appmaker, Webmaker. Plus produce a 15 slide aligment deck for internal stakeholders MoFo point: Mark (+Ben) SF  local contacts: Pete Scanlon, Ria Joy, Rick  Fant (a meeting at some point?), someone from  Bill Walker org, someone  from Christopher Lee org, Irina Sandu (voice?)  David Palomino (voice?) Proposed length: 4-6 hours Deliverable:  * Ship internal slide deck on the mobile development opportunity for Mozilla  * Scope 3 actionable demo collaborations between MoCo + MoFo 
===Review and iterate Webmaker.org information architecture===
 Goal: Take stock of all the pages on webmaker.org. Are they serving our needs? Where are there gaps? How might we improve our information architecture to support new pages like /explore and profiles? And how can we measure if its working? Lead: Cassie Collaborators: Matt, Kat, Kate, Adam Deliverable: A complete list of all current pages with "jobs" and notes on next steps for each Resource: Google doc: [https://docs.google.com/spreadsheets/d/1ejFHysKOLEGXynU6ZUQgUKn5AVlNgqDBtjrTyM8Zbk4/edit#gid=0 Every Page Has a Job] 

===Email like a Bawse===
 Goal: Now that we are sending out emails based on user events, let's make sure that they're as effective as can be. Lead: Andrea: Collaborators: Jbuck (infra), Aki (figure out HTML emails), Sabrina (design), Drushka (words) Deliverables: * Review existing emails for engagement ladder * Add "email drafting" to the Encyclopedia Best Practica * Design attractive HTML emails sent from Webmaker.org * Build proper HTML email delivery for Webmaker postal service 

=== Building a QA Community ===
Lead: Jbuck 
The QA community has begun to make tests for Webmaker.org (see https://github.com/mozilla/webmaker-tests/issues/37#issuecomment-41444213)
Let's discuss with the QA team how we can build a great community of testers, and also, how to be great at tests.
 
Collaborators: rbillings, JP, Cade 
Deliverables: A set of tickets about what to test next.
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/9csx7tfm.png

AllHands/Funnel Feeding

2014-04-26T05:12:19Z

Brett Gaylor: /* New Communities Co-design session: make a page on mozilla.org */

[[File:Funnel Feeding.png|300px|right]]
===Getting Real About Marketing + Press===
 This is critical. We have to pour as many people into the top of our funnel as possible. Press is a huge and proven way of doing  this. For example, if we landed two Lifehacker articles per quarter, we'd be tripling our users. We  don't currently have solid press kits/marketing kits for our products. Let's make some. Plus work out the details for how we're going to pitch Webmaker to press going forward.  Lead: Erica S and Lainie  Collaborators: Amira, Erin K, Kaitlin T, Erika D, Sabrina, Dave Steer, Hannah, Kaitlyn, Erin Kissane, Dan Sinker Note: Loop in Moco Marketing? Time Window: 3-4 hours Deliverables:  * press kit for Webmaker, Maker Party and Training Launch  * press kit for Open News  * press kit for Science Lab 

===Partnerships: becoming a closing machine===
 We now work from an integrated pipeline. It contains partners that bring us funding, contributors, or both. This means two things: (i) further integrating our recruitment, product, and management of partners, and (ii) become a closing machine. Goal: Cultural: Shift to being 'closers that care'. Practical: Log and start to action all of our leads. Account for managed growth through grants. Lead: Ben Moskowitz Collaborators: Geoff MacDougall, Matt Thompson, Hannah, Lynn Melander Moore, Amira Dhalla Time Window: 2 hours Deliverable: Prototype an interface between Webmaker requirements and Fundraising lead generation QUESTION: what does that deliverable mean? What are we going to document or make? +1 (GM) 
===Going Global: Three new markets for Webmaker in 2014===
 What they need from us and how we'll win. We have funded partnerships planned in Bangladesh, Brazil and more. Let's focus on where we are funded and do it well. Show where geographically anchored / regional funding is; talk about creating more visibility  about the data we have; leverage planned Maker Parties in these key locales; and measure where in the world Mozilla can make impact. Lead: Ben Moskowitz; Adam Lofting Collaborators: Michelle, Chris, Geoff, An-Me, Amira Deliverable: Document our plan for new markets ( and link to it here: https://wiki.mozilla.org/Webmaker/Markets https://wiki.mozilla.org/Webmaker/Markets ) Deliverable: Document a plan for informed, data-based decision making on global expansion <ul><li>Note: Synch this with the market and comms research MoCo is already doing </li></ul>

===Driving Mozilla-wide participation in Maker Party===
 From Open News to the Science Lab and beyond, let's make sure this year's Maker Party includes all areas of MoFo. This can also include how to leverage upcoming MozCamps, plus  Mozilla's new "gathering plan" for distributed events. Let's also pick a few likely MoCo groups and document with them what they might do as well.  Lead: Amira/Michelle Collaborators: Winston, WPR folks for Mozilla-spaces events Deliverable:  Open News and Science Lab document what they're going to do for Maker Party  Document with MDN what they might do as part of Maker Party Draft a Maker Party story and CTAs targeted directly at Mozilla community members <ul><li>(could be a draft WordPress landing page on the new Maker Party site. Then shipped to Mozilla.org or elsewhere.) </li></ul>
===Converting Maker Party event participants into contributors===
 How do we turn Webmaker and Maker Party event participants into users, supporters and contributors? This is one of the most important things we can do towards our 10k contributor goal this year. And it's hard. It will take a cross-team approach with engineers, community team and partnership teams working together. Let's get the key stakeholders together to agree on strategy and document a cross-team sprint together here:  https://wiki.mozilla.org/Webmaker/Events Lead: Brett + Matt Required: Brett, Matt, Amira, Gavin, Cassie Requested: Michelle, Kate Hudson, Lainie Context and reading: https://etherpad.mozilla.org/Events Deliverable: Get consensus with stakeholders. Then document our events roadmap. https://etherpad.mozilla.org/Events https://wiki.mozilla.org/Webmaker/Events 
===Project:Trust -- Mozilla Campaign Coordination===
 Trust is an emerging theme in many campaigns going on across Mozilla: marketing, advocacy, policy, engagement, education. The leads of the campaigns have agreed to start meeting to coordinate the work, maybe ship a shared platform or two. This is the first meeting of that group. Lead: Geoff MacDougall Collaborators: Dave Steer, Erica Sackin, Andrea Wood, Mary Ellen Muckerman, Eric Petitt, Michelle Thorne, Alex Fowler SF local  contacts: Dave Steer, Eric Petitt Proposed length: 90 mins Deliverable: Document our plan and next steps for leveraging Trust campaigns 

===Maker Party: Real Life User Stories (the theatrical experience)===
 Let's role-play to see how ready we are. We've all spent a number of months building systems, content, funnels, and tools that let us engage, support, and provide value to our many  types of users, supporters, and contributors. On July 15th those  systems, content, and funnels will be put to the test. We need to  rehearse and drill our processes. This session will see us act out (literally)  the user stories in our engagement ladder work, making sure none of the users we need to engage run into  walls or black holes. Lead: Geoffrey MacDougall Collaborators: Amira Dhalla, Chris Lawrence, Matt Thompson Proposed Length: A morning Deliverable: A captivating theatrical experience directed by Geoffrey MacDougall, featuring a full cast of MoFos. Add to our current Engagement Ladder user stories where necessary. Triaged and prioritized  here: http://mzl.la/contribution_pathways 
===Hive Documentation===
 Goal: Ship pages of the Hive Cookbook. Documenting and outlining existing Hive practices, strategies, goals and thinking onto the Mozilla Wiki. Started here https://wiki.mozilla.org/Webmaker/Hive Lead: Chris L, Leah, Sam Katherine Collaborators: Robert, Elsa, Julia, Lainie, Karen Non MOFO invitee: Zakyia Harris Proposed length: 1/2 day Deliverables:   * Ship new Hive Cookbook pages for Hive Chicago, Toronto and NYC.  * Update main Hive Landing page and begin building out further Hive resource pages like FAQ 

===Webmaker + MDN: prepping for May workweek===
Time:Wednesday 1:30
 Goal:  Determine, plot and start hacking on easy wins in preparation for the end of May     MDN/Webmaker workweek. Plus document larger strategic goals for collaborating with MDN going forward. Discuss the Thimble roadmap (and Thimble tutorials in particular) and see how MDN needs can be included. MoFo lead: Laura/Brett SF local contacts: Ali Proposed length: 1/4 day Deliverables:  * Train MDN staff to create Thimble tutorials.  * Update MDN staff on product vision for Thimble and Brackets.  * Transfer knowledge in creating MakeAPI galleries 

===New Communities Co-design session: make a page on mozilla.org===
Time: 1:30 Wednesday 
Lead: Dan/Erin Kissane Collaborators: Kaitlin, Dave, Studio MoFo Local SF contact: Holly Hastbritt (mozilla.org PM) Goal:  Collaborate & sprint on making a one-pager "New Communities" page  on Mozilla.org. Plus getting "News" and "Science" added to the  Mozilla.org "get involved" page. http://www.mozilla.org/contribute/ This can be a great way to tell the story around what Mozilla is doing  in these new spaces, plus drive referral traffic and contributors to  those projects.  time window: 6hrs, max Deliverable: Ship the page. With copy and design that follows Mozilla.org style Write copy for getting "News" added to the "Get Involved" page Write copy for getting "Science" added to the "Get Involved" page  File the tickets with MoCo colleagues to get that work shipped to mozilla.org 

=== Building a diverse pool of Webmaker contributors ===
Beginning first with our code contributors, we want to ensure that all contributors feel welcome in our open source project. Let's first examine what condititions and guidelines we should establish, where we're doing well, and we're we need to improve. Then we'll turn this into an inviting "one stop shopping"page at developer.webmaker.org that can onboard new code contributors.

Lead::Kate 
Deliverables: 
Draft of Webmaker code contributor guidelines 
Prototype of developer.webmaker.org

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/pjvdd1t5.png

AllHands/Funnel Feeding

2014-04-26T05:07:17Z

Brett Gaylor: /* New Communities Co-design session: make a page on mozilla.org */

[[File:Funnel Feeding.png|300px|right]]
===Getting Real About Marketing + Press===
 This is critical. We have to pour as many people into the top of our funnel as possible. Press is a huge and proven way of doing  this. For example, if we landed two Lifehacker articles per quarter, we'd be tripling our users. We  don't currently have solid press kits/marketing kits for our products. Let's make some. Plus work out the details for how we're going to pitch Webmaker to press going forward.  Lead: Erica S and Lainie  Collaborators: Amira, Erin K, Kaitlin T, Erika D, Sabrina, Dave Steer, Hannah, Kaitlyn, Erin Kissane, Dan Sinker Note: Loop in Moco Marketing? Time Window: 3-4 hours Deliverables:  * press kit for Webmaker, Maker Party and Training Launch  * press kit for Open News  * press kit for Science Lab 

===Partnerships: becoming a closing machine===
 We now work from an integrated pipeline. It contains partners that bring us funding, contributors, or both. This means two things: (i) further integrating our recruitment, product, and management of partners, and (ii) become a closing machine. Goal: Cultural: Shift to being 'closers that care'. Practical: Log and start to action all of our leads. Account for managed growth through grants. Lead: Ben Moskowitz Collaborators: Geoff MacDougall, Matt Thompson, Hannah, Lynn Melander Moore, Amira Dhalla Time Window: 2 hours Deliverable: Prototype an interface between Webmaker requirements and Fundraising lead generation QUESTION: what does that deliverable mean? What are we going to document or make? +1 (GM) 
===Going Global: Three new markets for Webmaker in 2014===
 What they need from us and how we'll win. We have funded partnerships planned in Bangladesh, Brazil and more. Let's focus on where we are funded and do it well. Show where geographically anchored / regional funding is; talk about creating more visibility  about the data we have; leverage planned Maker Parties in these key locales; and measure where in the world Mozilla can make impact. Lead: Ben Moskowitz; Adam Lofting Collaborators: Michelle, Chris, Geoff, An-Me, Amira Deliverable: Document our plan for new markets ( and link to it here: https://wiki.mozilla.org/Webmaker/Markets https://wiki.mozilla.org/Webmaker/Markets ) Deliverable: Document a plan for informed, data-based decision making on global expansion <ul><li>Note: Synch this with the market and comms research MoCo is already doing </li></ul>

===Driving Mozilla-wide participation in Maker Party===
 From Open News to the Science Lab and beyond, let's make sure this year's Maker Party includes all areas of MoFo. This can also include how to leverage upcoming MozCamps, plus  Mozilla's new "gathering plan" for distributed events. Let's also pick a few likely MoCo groups and document with them what they might do as well.  Lead: Amira/Michelle Collaborators: Winston, WPR folks for Mozilla-spaces events Deliverable:  Open News and Science Lab document what they're going to do for Maker Party  Document with MDN what they might do as part of Maker Party Draft a Maker Party story and CTAs targeted directly at Mozilla community members <ul><li>(could be a draft WordPress landing page on the new Maker Party site. Then shipped to Mozilla.org or elsewhere.) </li></ul>
===Converting Maker Party event participants into contributors===
 How do we turn Webmaker and Maker Party event participants into users, supporters and contributors? This is one of the most important things we can do towards our 10k contributor goal this year. And it's hard. It will take a cross-team approach with engineers, community team and partnership teams working together. Let's get the key stakeholders together to agree on strategy and document a cross-team sprint together here:  https://wiki.mozilla.org/Webmaker/Events Lead: Brett + Matt Required: Brett, Matt, Amira, Gavin, Cassie Requested: Michelle, Kate Hudson, Lainie Context and reading: https://etherpad.mozilla.org/Events Deliverable: Get consensus with stakeholders. Then document our events roadmap. https://etherpad.mozilla.org/Events https://wiki.mozilla.org/Webmaker/Events 
===Project:Trust -- Mozilla Campaign Coordination===
 Trust is an emerging theme in many campaigns going on across Mozilla: marketing, advocacy, policy, engagement, education. The leads of the campaigns have agreed to start meeting to coordinate the work, maybe ship a shared platform or two. This is the first meeting of that group. Lead: Geoff MacDougall Collaborators: Dave Steer, Erica Sackin, Andrea Wood, Mary Ellen Muckerman, Eric Petitt, Michelle Thorne, Alex Fowler SF local  contacts: Dave Steer, Eric Petitt Proposed length: 90 mins Deliverable: Document our plan and next steps for leveraging Trust campaigns 

===Maker Party: Real Life User Stories (the theatrical experience)===
 Let's role-play to see how ready we are. We've all spent a number of months building systems, content, funnels, and tools that let us engage, support, and provide value to our many  types of users, supporters, and contributors. On July 15th those  systems, content, and funnels will be put to the test. We need to  rehearse and drill our processes. This session will see us act out (literally)  the user stories in our engagement ladder work, making sure none of the users we need to engage run into  walls or black holes. Lead: Geoffrey MacDougall Collaborators: Amira Dhalla, Chris Lawrence, Matt Thompson Proposed Length: A morning Deliverable: A captivating theatrical experience directed by Geoffrey MacDougall, featuring a full cast of MoFos. Add to our current Engagement Ladder user stories where necessary. Triaged and prioritized  here: http://mzl.la/contribution_pathways 
===Hive Documentation===
 Goal: Ship pages of the Hive Cookbook. Documenting and outlining existing Hive practices, strategies, goals and thinking onto the Mozilla Wiki. Started here https://wiki.mozilla.org/Webmaker/Hive Lead: Chris L, Leah, Sam Katherine Collaborators: Robert, Elsa, Julia, Lainie, Karen Non MOFO invitee: Zakyia Harris Proposed length: 1/2 day Deliverables:   * Ship new Hive Cookbook pages for Hive Chicago, Toronto and NYC.  * Update main Hive Landing page and begin building out further Hive resource pages like FAQ 

===Webmaker + MDN: prepping for May workweek===
Time:Wednesday 1:30
 Goal:  Determine, plot and start hacking on easy wins in preparation for the end of May     MDN/Webmaker workweek. Plus document larger strategic goals for collaborating with MDN going forward. Discuss the Thimble roadmap (and Thimble tutorials in particular) and see how MDN needs can be included. MoFo lead: Laura/Brett SF local contacts: Ali Proposed length: 1/4 day Deliverables:  * Train MDN staff to create Thimble tutorials.  * Update MDN staff on product vision for Thimble and Brackets.  * Transfer knowledge in creating MakeAPI galleries 

===New Communities Co-design session: make a page on mozilla.org===
 Lead: Dan/Erin Kissane Collaborators: Kaitlin, Dave, Studio MoFo Local SF contact: Holly Hastbritt (mozilla.org PM) Goal:  Collaborate & sprint on making a one-pager "New Communities" page  on Mozilla.org. Plus getting "News" and "Science" added to the  Mozilla.org "get involved" page. http://www.mozilla.org/contribute/ This can be a great way to tell the story around what Mozilla is doing  in these new spaces, plus drive referral traffic and contributors to  those projects.  time window: 6hrs, max Deliverable: Ship the page. With copy and design that follows Mozilla.org style Write copy for getting "News" added to the "Get Involved" page Write copy for getting "Science" added to the "Get Involved" page  File the tickets with MoCo colleagues to get that work shipped to mozilla.org 

=== Building a diverse pool of Webmaker contributors ===
Beginning first with our code contributors, we want to ensure that all contributors feel welcome in our open source project. Let's first examine what condititions and guidelines we should establish, where we're doing well, and we're we need to improve. Then we'll turn this into an inviting "one stop shopping"page at developer.webmaker.org that can onboard new code contributors.

Lead::Kate 
Deliverables: 
Draft of Webmaker code contributor guidelines 
Prototype of developer.webmaker.org

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/pjvdd1t5.png

AllHands/Funnel Feeding

2014-04-26T05:04:03Z

Brett Gaylor: /* Webmaker + MDN: prepping for May workweek */

[[File:Funnel Feeding.png|300px|right]]
===Getting Real About Marketing + Press===
 This is critical. We have to pour as many people into the top of our funnel as possible. Press is a huge and proven way of doing  this. For example, if we landed two Lifehacker articles per quarter, we'd be tripling our users. We  don't currently have solid press kits/marketing kits for our products. Let's make some. Plus work out the details for how we're going to pitch Webmaker to press going forward.  Lead: Erica S and Lainie  Collaborators: Amira, Erin K, Kaitlin T, Erika D, Sabrina, Dave Steer, Hannah, Kaitlyn, Erin Kissane, Dan Sinker Note: Loop in Moco Marketing? Time Window: 3-4 hours Deliverables:  * press kit for Webmaker, Maker Party and Training Launch  * press kit for Open News  * press kit for Science Lab 

===Partnerships: becoming a closing machine===
 We now work from an integrated pipeline. It contains partners that bring us funding, contributors, or both. This means two things: (i) further integrating our recruitment, product, and management of partners, and (ii) become a closing machine. Goal: Cultural: Shift to being 'closers that care'. Practical: Log and start to action all of our leads. Account for managed growth through grants. Lead: Ben Moskowitz Collaborators: Geoff MacDougall, Matt Thompson, Hannah, Lynn Melander Moore, Amira Dhalla Time Window: 2 hours Deliverable: Prototype an interface between Webmaker requirements and Fundraising lead generation QUESTION: what does that deliverable mean? What are we going to document or make? +1 (GM) 
===Going Global: Three new markets for Webmaker in 2014===
 What they need from us and how we'll win. We have funded partnerships planned in Bangladesh, Brazil and more. Let's focus on where we are funded and do it well. Show where geographically anchored / regional funding is; talk about creating more visibility  about the data we have; leverage planned Maker Parties in these key locales; and measure where in the world Mozilla can make impact. Lead: Ben Moskowitz; Adam Lofting Collaborators: Michelle, Chris, Geoff, An-Me, Amira Deliverable: Document our plan for new markets ( and link to it here: https://wiki.mozilla.org/Webmaker/Markets https://wiki.mozilla.org/Webmaker/Markets ) Deliverable: Document a plan for informed, data-based decision making on global expansion <ul><li>Note: Synch this with the market and comms research MoCo is already doing </li></ul>

===Driving Mozilla-wide participation in Maker Party===
 From Open News to the Science Lab and beyond, let's make sure this year's Maker Party includes all areas of MoFo. This can also include how to leverage upcoming MozCamps, plus  Mozilla's new "gathering plan" for distributed events. Let's also pick a few likely MoCo groups and document with them what they might do as well.  Lead: Amira/Michelle Collaborators: Winston, WPR folks for Mozilla-spaces events Deliverable:  Open News and Science Lab document what they're going to do for Maker Party  Document with MDN what they might do as part of Maker Party Draft a Maker Party story and CTAs targeted directly at Mozilla community members <ul><li>(could be a draft WordPress landing page on the new Maker Party site. Then shipped to Mozilla.org or elsewhere.) </li></ul>
===Converting Maker Party event participants into contributors===
 How do we turn Webmaker and Maker Party event participants into users, supporters and contributors? This is one of the most important things we can do towards our 10k contributor goal this year. And it's hard. It will take a cross-team approach with engineers, community team and partnership teams working together. Let's get the key stakeholders together to agree on strategy and document a cross-team sprint together here:  https://wiki.mozilla.org/Webmaker/Events Lead: Brett + Matt Required: Brett, Matt, Amira, Gavin, Cassie Requested: Michelle, Kate Hudson, Lainie Context and reading: https://etherpad.mozilla.org/Events Deliverable: Get consensus with stakeholders. Then document our events roadmap. https://etherpad.mozilla.org/Events https://wiki.mozilla.org/Webmaker/Events 
===Project:Trust -- Mozilla Campaign Coordination===
 Trust is an emerging theme in many campaigns going on across Mozilla: marketing, advocacy, policy, engagement, education. The leads of the campaigns have agreed to start meeting to coordinate the work, maybe ship a shared platform or two. This is the first meeting of that group. Lead: Geoff MacDougall Collaborators: Dave Steer, Erica Sackin, Andrea Wood, Mary Ellen Muckerman, Eric Petitt, Michelle Thorne, Alex Fowler SF local  contacts: Dave Steer, Eric Petitt Proposed length: 90 mins Deliverable: Document our plan and next steps for leveraging Trust campaigns 

===Maker Party: Real Life User Stories (the theatrical experience)===
 Let's role-play to see how ready we are. We've all spent a number of months building systems, content, funnels, and tools that let us engage, support, and provide value to our many  types of users, supporters, and contributors. On July 15th those  systems, content, and funnels will be put to the test. We need to  rehearse and drill our processes. This session will see us act out (literally)  the user stories in our engagement ladder work, making sure none of the users we need to engage run into  walls or black holes. Lead: Geoffrey MacDougall Collaborators: Amira Dhalla, Chris Lawrence, Matt Thompson Proposed Length: A morning Deliverable: A captivating theatrical experience directed by Geoffrey MacDougall, featuring a full cast of MoFos. Add to our current Engagement Ladder user stories where necessary. Triaged and prioritized  here: http://mzl.la/contribution_pathways 
===Hive Documentation===
 Goal: Ship pages of the Hive Cookbook. Documenting and outlining existing Hive practices, strategies, goals and thinking onto the Mozilla Wiki. Started here https://wiki.mozilla.org/Webmaker/Hive Lead: Chris L, Leah, Sam Katherine Collaborators: Robert, Elsa, Julia, Lainie, Karen Non MOFO invitee: Zakyia Harris Proposed length: 1/2 day Deliverables:   * Ship new Hive Cookbook pages for Hive Chicago, Toronto and NYC.  * Update main Hive Landing page and begin building out further Hive resource pages like FAQ 

===Webmaker + MDN: prepping for May workweek===
Time:Wednesday 1:30
 Goal:  Determine, plot and start hacking on easy wins in preparation for the end of May     MDN/Webmaker workweek. Plus document larger strategic goals for collaborating with MDN going forward. Discuss the Thimble roadmap (and Thimble tutorials in particular) and see how MDN needs can be included. MoFo lead: Laura/Brett SF local contacts: Ali Proposed length: 1/4 day Deliverables:  * Train MDN staff to create Thimble tutorials.  * Update MDN staff on product vision for Thimble and Brackets.  * Transfer knowledge in creating MakeAPI galleries 

===New Communities Co-design session: make a page on mozilla.org===
 Lead: Dan/Erin Kissane Collaborators: Kaitlin, Dave, Studio MoFo Local SF contact: Jen Bersch (mozilla.org PM) Goal:  Collaborate & sprint on making a one-pager "New Communities" page  on Mozilla.org. Plus getting "News" and "Science" added to the  Mozilla.org "get involved" page. http://www.mozilla.org/contribute/ This can be a great way to tell the story around what Mozilla is doing  in these new spaces, plus drive referral traffic and contributors to  those projects.  time window: 6hrs, max  +1 DS +1 (KT) Deliverable: Ship the page. With copy and design that follows Mozilla.org style Write copy for getting "News" added to the "Get Involved" page Write copy for getting "Science" added to the "Get Involved" page  File the tickets with MoCo colleagues to get that work shipped to mozilla.org 
=== Building a diverse pool of Webmaker contributors ===
Beginning first with our code contributors, we want to ensure that all contributors feel welcome in our open source project. Let's first examine what condititions and guidelines we should establish, where we're doing well, and we're we need to improve. Then we'll turn this into an inviting "one stop shopping"page at developer.webmaker.org that can onboard new code contributors.

Lead::Kate 
Deliverables: 
Draft of Webmaker code contributor guidelines 
Prototype of developer.webmaker.org

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/pjvdd1t5.png

AllHands/Funnel Feeding

2014-04-26T05:02:12Z

Brett Gaylor: /* Project:Trust -- Mozilla Campaign Coordination */

[[File:Funnel Feeding.png|300px|right]]
===Getting Real About Marketing + Press===
 This is critical. We have to pour as many people into the top of our funnel as possible. Press is a huge and proven way of doing  this. For example, if we landed two Lifehacker articles per quarter, we'd be tripling our users. We  don't currently have solid press kits/marketing kits for our products. Let's make some. Plus work out the details for how we're going to pitch Webmaker to press going forward.  Lead: Erica S and Lainie  Collaborators: Amira, Erin K, Kaitlin T, Erika D, Sabrina, Dave Steer, Hannah, Kaitlyn, Erin Kissane, Dan Sinker Note: Loop in Moco Marketing? Time Window: 3-4 hours Deliverables:  * press kit for Webmaker, Maker Party and Training Launch  * press kit for Open News  * press kit for Science Lab 

===Partnerships: becoming a closing machine===
 We now work from an integrated pipeline. It contains partners that bring us funding, contributors, or both. This means two things: (i) further integrating our recruitment, product, and management of partners, and (ii) become a closing machine. Goal: Cultural: Shift to being 'closers that care'. Practical: Log and start to action all of our leads. Account for managed growth through grants. Lead: Ben Moskowitz Collaborators: Geoff MacDougall, Matt Thompson, Hannah, Lynn Melander Moore, Amira Dhalla Time Window: 2 hours Deliverable: Prototype an interface between Webmaker requirements and Fundraising lead generation QUESTION: what does that deliverable mean? What are we going to document or make? +1 (GM) 
===Going Global: Three new markets for Webmaker in 2014===
 What they need from us and how we'll win. We have funded partnerships planned in Bangladesh, Brazil and more. Let's focus on where we are funded and do it well. Show where geographically anchored / regional funding is; talk about creating more visibility  about the data we have; leverage planned Maker Parties in these key locales; and measure where in the world Mozilla can make impact. Lead: Ben Moskowitz; Adam Lofting Collaborators: Michelle, Chris, Geoff, An-Me, Amira Deliverable: Document our plan for new markets ( and link to it here: https://wiki.mozilla.org/Webmaker/Markets https://wiki.mozilla.org/Webmaker/Markets ) Deliverable: Document a plan for informed, data-based decision making on global expansion <ul><li>Note: Synch this with the market and comms research MoCo is already doing </li></ul>

===Driving Mozilla-wide participation in Maker Party===
 From Open News to the Science Lab and beyond, let's make sure this year's Maker Party includes all areas of MoFo. This can also include how to leverage upcoming MozCamps, plus  Mozilla's new "gathering plan" for distributed events. Let's also pick a few likely MoCo groups and document with them what they might do as well.  Lead: Amira/Michelle Collaborators: Winston, WPR folks for Mozilla-spaces events Deliverable:  Open News and Science Lab document what they're going to do for Maker Party  Document with MDN what they might do as part of Maker Party Draft a Maker Party story and CTAs targeted directly at Mozilla community members <ul><li>(could be a draft WordPress landing page on the new Maker Party site. Then shipped to Mozilla.org or elsewhere.) </li></ul>
===Converting Maker Party event participants into contributors===
 How do we turn Webmaker and Maker Party event participants into users, supporters and contributors? This is one of the most important things we can do towards our 10k contributor goal this year. And it's hard. It will take a cross-team approach with engineers, community team and partnership teams working together. Let's get the key stakeholders together to agree on strategy and document a cross-team sprint together here:  https://wiki.mozilla.org/Webmaker/Events Lead: Brett + Matt Required: Brett, Matt, Amira, Gavin, Cassie Requested: Michelle, Kate Hudson, Lainie Context and reading: https://etherpad.mozilla.org/Events Deliverable: Get consensus with stakeholders. Then document our events roadmap. https://etherpad.mozilla.org/Events https://wiki.mozilla.org/Webmaker/Events 
===Project:Trust -- Mozilla Campaign Coordination===
 Trust is an emerging theme in many campaigns going on across Mozilla: marketing, advocacy, policy, engagement, education. The leads of the campaigns have agreed to start meeting to coordinate the work, maybe ship a shared platform or two. This is the first meeting of that group. Lead: Geoff MacDougall Collaborators: Dave Steer, Erica Sackin, Andrea Wood, Mary Ellen Muckerman, Eric Petitt, Michelle Thorne, Alex Fowler SF local  contacts: Dave Steer, Eric Petitt Proposed length: 90 mins Deliverable: Document our plan and next steps for leveraging Trust campaigns 

===Maker Party: Real Life User Stories (the theatrical experience)===
 Let's role-play to see how ready we are. We've all spent a number of months building systems, content, funnels, and tools that let us engage, support, and provide value to our many  types of users, supporters, and contributors. On July 15th those  systems, content, and funnels will be put to the test. We need to  rehearse and drill our processes. This session will see us act out (literally)  the user stories in our engagement ladder work, making sure none of the users we need to engage run into  walls or black holes. Lead: Geoffrey MacDougall Collaborators: Amira Dhalla, Chris Lawrence, Matt Thompson Proposed Length: A morning Deliverable: A captivating theatrical experience directed by Geoffrey MacDougall, featuring a full cast of MoFos. Add to our current Engagement Ladder user stories where necessary. Triaged and prioritized  here: http://mzl.la/contribution_pathways 
===Hive Documentation===
 Goal: Ship pages of the Hive Cookbook. Documenting and outlining existing Hive practices, strategies, goals and thinking onto the Mozilla Wiki. Started here https://wiki.mozilla.org/Webmaker/Hive Lead: Chris L, Leah, Sam Katherine Collaborators: Robert, Elsa, Julia, Lainie, Karen Non MOFO invitee: Zakyia Harris Proposed length: 1/2 day Deliverables:   * Ship new Hive Cookbook pages for Hive Chicago, Toronto and NYC.  * Update main Hive Landing page and begin building out further Hive resource pages like FAQ 

===Webmaker + MDN: prepping for May workweek===
 Goal:  Determine, plot and start hacking on easy wins in preparation for the end of May     MDN/Webmaker workweek. Plus document larger strategic goals for collaborating with MDN going forward. Discuss the Thimble roadmap (and Thimble tutorials in particular) and see how MDN needs can be included. MoFo lead: Laura/Brett SF local contacts: Ali Proposed length: 1/4 day Deliverables:  * Train MDN staff to create Thimble tutorials.  * Update MDN staff on product vision for Thimble and Brackets.  * Transfer knowledge in creating MakeAPI galleries 
===New Communities Co-design session: make a page on mozilla.org===
 Lead: Dan/Erin Kissane Collaborators: Kaitlin, Dave, Studio MoFo Local SF contact: Jen Bersch (mozilla.org PM) Goal:  Collaborate & sprint on making a one-pager "New Communities" page  on Mozilla.org. Plus getting "News" and "Science" added to the  Mozilla.org "get involved" page. http://www.mozilla.org/contribute/ This can be a great way to tell the story around what Mozilla is doing  in these new spaces, plus drive referral traffic and contributors to  those projects.  time window: 6hrs, max  +1 DS +1 (KT) Deliverable: Ship the page. With copy and design that follows Mozilla.org style Write copy for getting "News" added to the "Get Involved" page Write copy for getting "Science" added to the "Get Involved" page  File the tickets with MoCo colleagues to get that work shipped to mozilla.org 
=== Building a diverse pool of Webmaker contributors ===
Beginning first with our code contributors, we want to ensure that all contributors feel welcome in our open source project. Let's first examine what condititions and guidelines we should establish, where we're doing well, and we're we need to improve. Then we'll turn this into an inviting "one stop shopping"page at developer.webmaker.org that can onboard new code contributors.

Lead::Kate 
Deliverables: 
Draft of Webmaker code contributor guidelines 
Prototype of developer.webmaker.org

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/pjvdd1t5.png

AllHands/Funnel Feeding

2014-04-26T04:46:45Z

Brett Gaylor: /* Going Global: Three new markets for Webmaker in 2014 */

[[File:Funnel Feeding.png|300px|right]]
===Getting Real About Marketing + Press===
 This is critical. We have to pour as many people into the top of our funnel as possible. Press is a huge and proven way of doing  this. For example, if we landed two Lifehacker articles per quarter, we'd be tripling our users. We  don't currently have solid press kits/marketing kits for our products. Let's make some. Plus work out the details for how we're going to pitch Webmaker to press going forward.  Lead: Erica S and Lainie  Collaborators: Amira, Erin K, Kaitlin T, Erika D, Sabrina, Dave Steer, Hannah, Kaitlyn, Erin Kissane, Dan Sinker Note: Loop in Moco Marketing? Time Window: 3-4 hours Deliverables:  * press kit for Webmaker, Maker Party and Training Launch  * press kit for Open News  * press kit for Science Lab 

===Partnerships: becoming a closing machine===
 We now work from an integrated pipeline. It contains partners that bring us funding, contributors, or both. This means two things: (i) further integrating our recruitment, product, and management of partners, and (ii) become a closing machine. Goal: Cultural: Shift to being 'closers that care'. Practical: Log and start to action all of our leads. Account for managed growth through grants. Lead: Ben Moskowitz Collaborators: Geoff MacDougall, Matt Thompson, Hannah, Lynn Melander Moore, Amira Dhalla Time Window: 2 hours Deliverable: Prototype an interface between Webmaker requirements and Fundraising lead generation QUESTION: what does that deliverable mean? What are we going to document or make? +1 (GM) 
===Going Global: Three new markets for Webmaker in 2014===
 What they need from us and how we'll win. We have funded partnerships planned in Bangladesh, Brazil and more. Let's focus on where we are funded and do it well. Show where geographically anchored / regional funding is; talk about creating more visibility  about the data we have; leverage planned Maker Parties in these key locales; and measure where in the world Mozilla can make impact. Lead: Ben Moskowitz; Adam Lofting Collaborators: Michelle, Chris, Geoff, An-Me, Amira Deliverable: Document our plan for new markets ( and link to it here: https://wiki.mozilla.org/Webmaker/Markets https://wiki.mozilla.org/Webmaker/Markets ) Deliverable: Document a plan for informed, data-based decision making on global expansion <ul><li>Note: Synch this with the market and comms research MoCo is already doing </li></ul>

===Driving Mozilla-wide participation in Maker Party===
 From Open News to the Science Lab and beyond, let's make sure this year's Maker Party includes all areas of MoFo. This can also include how to leverage upcoming MozCamps, plus  Mozilla's new "gathering plan" for distributed events. Let's also pick a few likely MoCo groups and document with them what they might do as well.  Lead: Amira/Michelle Collaborators: Winston, WPR folks for Mozilla-spaces events Deliverable:  Open News and Science Lab document what they're going to do for Maker Party  Document with MDN what they might do as part of Maker Party Draft a Maker Party story and CTAs targeted directly at Mozilla community members <ul><li>(could be a draft WordPress landing page on the new Maker Party site. Then shipped to Mozilla.org or elsewhere.) </li></ul>
===Converting Maker Party event participants into contributors===
 How do we turn Webmaker and Maker Party event participants into users, supporters and contributors? This is one of the most important things we can do towards our 10k contributor goal this year. And it's hard. It will take a cross-team approach with engineers, community team and partnership teams working together. Let's get the key stakeholders together to agree on strategy and document a cross-team sprint together here:  https://wiki.mozilla.org/Webmaker/Events Lead: Brett + Matt Required: Brett, Matt, Amira, Gavin, Cassie Requested: Michelle, Kate Hudson, Lainie Context and reading: https://etherpad.mozilla.org/Events Deliverable: Get consensus with stakeholders. Then document our events roadmap. https://etherpad.mozilla.org/Events https://wiki.mozilla.org/Webmaker/Events 
===Project:Trust -- Mozilla Campaign Coordination===
 Trust is an emerging theme in many campaigns going on across Mozilla: marketing, advocacy, policy, engagement, education. The leads of the campaigns have agreed to start meeting to coordinate the work, maybe ship a shared platform or two. This is the first meeting of that group. Lead: Geoff MacDougall Collaborators: Dave Steer, Erica Sackin, Andrea Wood, Mary Ellen Muckerman, Eric Petitt, Michelle Thorne, Alex Fowler SF local  contacts: Dave Steer, Eric Petitt Proposed length: 90 mins Deliverable: Document our plan and next steps for leveraging Trust campaigns +1 (GM; this is going to happen) +1AMC 
===Maker Party: Real Life User Stories (the theatrical experience)===
 Let's role-play to see how ready we are. We've all spent a number of months building systems, content, funnels, and tools that let us engage, support, and provide value to our many  types of users, supporters, and contributors. On July 15th those  systems, content, and funnels will be put to the test. We need to  rehearse and drill our processes. This session will see us act out (literally)  the user stories in our engagement ladder work, making sure none of the users we need to engage run into  walls or black holes. Lead: Geoffrey MacDougall Collaborators: Amira Dhalla, Chris Lawrence, Matt Thompson Proposed Length: A morning Deliverable: A captivating theatrical experience directed by Geoffrey MacDougall, featuring a full cast of MoFos. Add to our current Engagement Ladder user stories where necessary. Triaged and prioritized  here: http://mzl.la/contribution_pathways 
===Hive Documentation===
 Goal: Ship pages of the Hive Cookbook. Documenting and outlining existing Hive practices, strategies, goals and thinking onto the Mozilla Wiki. Started here https://wiki.mozilla.org/Webmaker/Hive Lead: Chris L, Leah, Sam Katherine Collaborators: Robert, Elsa, Julia, Lainie, Karen Non MOFO invitee: Zakyia Harris Proposed length: 1/2 day Deliverables:   * Ship new Hive Cookbook pages for Hive Chicago, Toronto and NYC.  * Update main Hive Landing page and begin building out further Hive resource pages like FAQ 

===Webmaker + MDN: prepping for May workweek===
 Goal:  Determine, plot and start hacking on easy wins in preparation for the end of May     MDN/Webmaker workweek. Plus document larger strategic goals for collaborating with MDN going forward. Discuss the Thimble roadmap (and Thimble tutorials in particular) and see how MDN needs can be included. MoFo lead: Laura/Brett SF local contacts: Ali Proposed length: 1/4 day Deliverables:  * Train MDN staff to create Thimble tutorials.  * Update MDN staff on product vision for Thimble and Brackets.  * Transfer knowledge in creating MakeAPI galleries 
===New Communities Co-design session: make a page on mozilla.org===
 Lead: Dan/Erin Kissane Collaborators: Kaitlin, Dave, Studio MoFo Local SF contact: Jen Bersch (mozilla.org PM) Goal:  Collaborate & sprint on making a one-pager "New Communities" page  on Mozilla.org. Plus getting "News" and "Science" added to the  Mozilla.org "get involved" page. http://www.mozilla.org/contribute/ This can be a great way to tell the story around what Mozilla is doing  in these new spaces, plus drive referral traffic and contributors to  those projects.  time window: 6hrs, max  +1 DS +1 (KT) Deliverable: Ship the page. With copy and design that follows Mozilla.org style Write copy for getting "News" added to the "Get Involved" page Write copy for getting "Science" added to the "Get Involved" page  File the tickets with MoCo colleagues to get that work shipped to mozilla.org 
=== Building a diverse pool of Webmaker contributors ===
Beginning first with our code contributors, we want to ensure that all contributors feel welcome in our open source project. Let's first examine what condititions and guidelines we should establish, where we're doing well, and we're we need to improve. Then we'll turn this into an inviting "one stop shopping"page at developer.webmaker.org that can onboard new code contributors.

Lead::Kate 
Deliverables: 
Draft of Webmaker code contributor guidelines 
Prototype of developer.webmaker.org

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/pjvdd1t5.png

AllHands/Funnel Feeding

2014-04-26T04:41:43Z

Brett Gaylor: /* Getting Real About Marketing + Press */

[[File:Funnel Feeding.png|300px|right]]
===Getting Real About Marketing + Press===
 This is critical. We have to pour as many people into the top of our funnel as possible. Press is a huge and proven way of doing  this. For example, if we landed two Lifehacker articles per quarter, we'd be tripling our users. We  don't currently have solid press kits/marketing kits for our products. Let's make some. Plus work out the details for how we're going to pitch Webmaker to press going forward.  Lead: Erica S and Lainie  Collaborators: Amira, Erin K, Kaitlin T, Erika D, Sabrina, Dave Steer, Hannah, Kaitlyn, Erin Kissane, Dan Sinker Note: Loop in Moco Marketing? Time Window: 3-4 hours Deliverables:  * press kit for Webmaker, Maker Party and Training Launch  * press kit for Open News  * press kit for Science Lab 

===Partnerships: becoming a closing machine===
 We now work from an integrated pipeline. It contains partners that bring us funding, contributors, or both. This means two things: (i) further integrating our recruitment, product, and management of partners, and (ii) become a closing machine. Goal: Cultural: Shift to being 'closers that care'. Practical: Log and start to action all of our leads. Account for managed growth through grants. Lead: Ben Moskowitz Collaborators: Geoff MacDougall, Matt Thompson, Hannah, Lynn Melander Moore, Amira Dhalla Time Window: 2 hours Deliverable: Prototype an interface between Webmaker requirements and Fundraising lead generation QUESTION: what does that deliverable mean? What are we going to document or make? +1 (GM) 
===Going Global: Three new markets for Webmaker in 2014===
 What they need from us and how we'll win. We have funded partnerships planned in Bangladesh, Brazil and more. Let's focus on where we are funded and do it well. Show where geographically anchored / regional funding is; talk about creating more visibility  about the data we have; leverage planned Maker Parties in these key locales; and measure where in the world Mozilla can make impact. Lead: Ben Moskowitz; Adam Lofting Collaborators: Michelle, Chris, Geoff, An-Me, Amira +1 (BG) +1 (MT)+1AMC +1 BM +1 (PLD) Deliverable: Document our plan for new markets ( and link to it here: https://wiki.mozilla.org/Webmaker/Markets https://wiki.mozilla.org/Webmaker/Markets ) Deliverable: Document a plan for informed, data-based decision making on global expansion <ul><li>Note: Synch this with the market and comms research MoCo is already doing </li></ul>
===Driving Mozilla-wide participation in Maker Party===
 From Open News to the Science Lab and beyond, let's make sure this year's Maker Party includes all areas of MoFo. This can also include how to leverage upcoming MozCamps, plus  Mozilla's new "gathering plan" for distributed events. Let's also pick a few likely MoCo groups and document with them what they might do as well.  Lead: Amira/Michelle Collaborators: Winston, WPR folks for Mozilla-spaces events Deliverable:  Open News and Science Lab document what they're going to do for Maker Party  Document with MDN what they might do as part of Maker Party Draft a Maker Party story and CTAs targeted directly at Mozilla community members <ul><li>(could be a draft WordPress landing page on the new Maker Party site. Then shipped to Mozilla.org or elsewhere.) </li></ul>
===Converting Maker Party event participants into contributors===
 How do we turn Webmaker and Maker Party event participants into users, supporters and contributors? This is one of the most important things we can do towards our 10k contributor goal this year. And it's hard. It will take a cross-team approach with engineers, community team and partnership teams working together. Let's get the key stakeholders together to agree on strategy and document a cross-team sprint together here:  https://wiki.mozilla.org/Webmaker/Events Lead: Brett + Matt Required: Brett, Matt, Amira, Gavin, Cassie Requested: Michelle, Kate Hudson, Lainie Context and reading: https://etherpad.mozilla.org/Events Deliverable: Get consensus with stakeholders. Then document our events roadmap. https://etherpad.mozilla.org/Events https://wiki.mozilla.org/Webmaker/Events 
===Project:Trust -- Mozilla Campaign Coordination===
 Trust is an emerging theme in many campaigns going on across Mozilla: marketing, advocacy, policy, engagement, education. The leads of the campaigns have agreed to start meeting to coordinate the work, maybe ship a shared platform or two. This is the first meeting of that group. Lead: Geoff MacDougall Collaborators: Dave Steer, Erica Sackin, Andrea Wood, Mary Ellen Muckerman, Eric Petitt, Michelle Thorne, Alex Fowler SF local  contacts: Dave Steer, Eric Petitt Proposed length: 90 mins Deliverable: Document our plan and next steps for leveraging Trust campaigns +1 (GM; this is going to happen) +1AMC 
===Maker Party: Real Life User Stories (the theatrical experience)===
 Let's role-play to see how ready we are. We've all spent a number of months building systems, content, funnels, and tools that let us engage, support, and provide value to our many  types of users, supporters, and contributors. On July 15th those  systems, content, and funnels will be put to the test. We need to  rehearse and drill our processes. This session will see us act out (literally)  the user stories in our engagement ladder work, making sure none of the users we need to engage run into  walls or black holes. Lead: Geoffrey MacDougall Collaborators: Amira Dhalla, Chris Lawrence, Matt Thompson Proposed Length: A morning Deliverable: A captivating theatrical experience directed by Geoffrey MacDougall, featuring a full cast of MoFos. Add to our current Engagement Ladder user stories where necessary. Triaged and prioritized  here: http://mzl.la/contribution_pathways 
===Hive Documentation===
 Goal: Ship pages of the Hive Cookbook. Documenting and outlining existing Hive practices, strategies, goals and thinking onto the Mozilla Wiki. Started here https://wiki.mozilla.org/Webmaker/Hive Lead: Chris L, Leah, Sam Katherine Collaborators: Robert, Elsa, Julia, Lainie, Karen Non MOFO invitee: Zakyia Harris Proposed length: 1/2 day Deliverables:   * Ship new Hive Cookbook pages for Hive Chicago, Toronto and NYC.  * Update main Hive Landing page and begin building out further Hive resource pages like FAQ 

===Webmaker + MDN: prepping for May workweek===
 Goal:  Determine, plot and start hacking on easy wins in preparation for the end of May     MDN/Webmaker workweek. Plus document larger strategic goals for collaborating with MDN going forward. Discuss the Thimble roadmap (and Thimble tutorials in particular) and see how MDN needs can be included. MoFo lead: Laura/Brett SF local contacts: Ali Proposed length: 1/4 day Deliverables:  * Train MDN staff to create Thimble tutorials.  * Update MDN staff on product vision for Thimble and Brackets.  * Transfer knowledge in creating MakeAPI galleries 
===New Communities Co-design session: make a page on mozilla.org===
 Lead: Dan/Erin Kissane Collaborators: Kaitlin, Dave, Studio MoFo Local SF contact: Jen Bersch (mozilla.org PM) Goal:  Collaborate & sprint on making a one-pager "New Communities" page  on Mozilla.org. Plus getting "News" and "Science" added to the  Mozilla.org "get involved" page. http://www.mozilla.org/contribute/ This can be a great way to tell the story around what Mozilla is doing  in these new spaces, plus drive referral traffic and contributors to  those projects.  time window: 6hrs, max  +1 DS +1 (KT) Deliverable: Ship the page. With copy and design that follows Mozilla.org style Write copy for getting "News" added to the "Get Involved" page Write copy for getting "Science" added to the "Get Involved" page  File the tickets with MoCo colleagues to get that work shipped to mozilla.org 
=== Building a diverse pool of Webmaker contributors ===
Beginning first with our code contributors, we want to ensure that all contributors feel welcome in our open source project. Let's first examine what condititions and guidelines we should establish, where we're doing well, and we're we need to improve. Then we'll turn this into an inviting "one stop shopping"page at developer.webmaker.org that can onboard new code contributors.

Lead::Kate 
Deliverables: 
Draft of Webmaker code contributor guidelines 
Prototype of developer.webmaker.org

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/pjvdd1t5.png

AllHands/Funnel Building

2014-04-26T04:40:53Z

Brett Gaylor: /* badges.mozilla.org Prototyping Party */

[[File:Funnel Building.png|175px|right]]
__TOC__
===Contributor Metrics: connecting the threads===
Time: Tuesday 10:00-12:00 
Goal:  Connecting the strands so we're heading in the same direction.  Face-to-face    discussions about Baloo, and BI Datawarehouse tools;  Tableau server and dashboards; MoFo Interim Contributor Dashboard and  the systems  behind it; + the Adhoc contribution logger.  MoFo point: Adam and Jbuck  SF Moco contacts:  David Boswell  Local Moco, but not SF: Anurag Phadke (Mountain View),  Collaborators: Chris D 

Bugzilla tags:[allhands][metrics]

Deliverable: [QUESTION: Adam, what is the concrete deliverable / ticket here?] 

===Landing the badges moonshot: Webmaker + Badgekit sprint===
*'''Lead''': Kate
*'''Collaborators''': An Me, Erik, Andrew, JP, Jbuck
*'''Goal: We will issue the Webmaker Super Mentor badge'''. We're a few short tickets away from being able to issue and approve Webmaker badges in Badgekit. Let's sprint towards completion.
*'''Deliverable''': Ship the Webmaker Super Mentor Badge, supporting the complete end-to-end user story: see, apply, review, issue, receive.
*'''Webmaker badges roadmap:''' [[Webmaker/Badges#Q2_Roadmap|Q2 Roadmap]]
*'''Bugzilla tags''': webmakerbadges, followup

<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"product": "webmaker",
"whiteboard": "webmakerbadges, followup",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>

=== badges.mozilla.org Prototyping Party ===
*'''Time: Wednesday, 3:00 PM'''
*'''Lead''': Emily
*'''Collaborators''':
*'''Goal: Let's prototype this site's future'''. We will start with a look at what badges.mozilla.org was and who used it. Then we'll plan what it might become, and the larger vision and resources that will needed. Plus how it might it fit with the larger plan for MoFo and MoCo badges. Less yack, more hack.

<onlyinclude><div style="align:left;"><bugzilla>{
"product": "mozilla.org",
"whiteboard": "[badges]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}</bugzilla><div style="align:left;"></onlyinclude>

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/04nv-wox.png

AllHands/Funnel Building

2014-04-26T04:40:03Z

Brett Gaylor: /* Landing the badges moonshot: Webmaker + Badgekit sprint */

[[File:Funnel Building.png|175px|right]]
__TOC__
===Contributor Metrics: connecting the threads===
Time: Tuesday 10:00-12:00 
Goal:  Connecting the strands so we're heading in the same direction.  Face-to-face    discussions about Baloo, and BI Datawarehouse tools;  Tableau server and dashboards; MoFo Interim Contributor Dashboard and  the systems  behind it; + the Adhoc contribution logger.  MoFo point: Adam and Jbuck  SF Moco contacts:  David Boswell  Local Moco, but not SF: Anurag Phadke (Mountain View),  Collaborators: Chris D 

Bugzilla tags:[allhands][metrics]

Deliverable: [QUESTION: Adam, what is the concrete deliverable / ticket here?] 

===Landing the badges moonshot: Webmaker + Badgekit sprint===
*'''Lead''': Kate
*'''Collaborators''': An Me, Erik, Andrew, JP, Jbuck
*'''Goal: We will issue the Webmaker Super Mentor badge'''. We're a few short tickets away from being able to issue and approve Webmaker badges in Badgekit. Let's sprint towards completion.
*'''Deliverable''': Ship the Webmaker Super Mentor Badge, supporting the complete end-to-end user story: see, apply, review, issue, receive.
*'''Webmaker badges roadmap:''' [[Webmaker/Badges#Q2_Roadmap|Q2 Roadmap]]
*'''Bugzilla tags''': webmakerbadges, followup

<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"product": "webmaker",
"whiteboard": "webmakerbadges, followup",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>

=== badges.mozilla.org Prototyping Party ===
*'''Lead''': Emily
*'''Collaborators''':
*'''Goal: Let's prototype this site's future'''. We will start with a look at what badges.mozilla.org was and who used it. Then we'll plan what it might become, and the larger vision and resources that will needed. Plus how it might it fit with the larger plan for MoFo and MoCo badges. Less yack, more hack.
*'''Time: Wednesday, 3:00 PM'''

<onlyinclude><div style="align:left;"><bugzilla>{
"product": "mozilla.org",
"whiteboard": "[badges]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}</bugzilla><div style="align:left;"></onlyinclude>

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/04nv-wox.png

AllHands/Funnel Building

2014-04-26T04:39:31Z

Brett Gaylor: /* Landing the badges moonshot: Webmaker + Badgekit sprint */

[[File:Funnel Building.png|175px|right]]
__TOC__
===Contributor Metrics: connecting the threads===
Time: Tuesday 10:00-12:00 
Goal:  Connecting the strands so we're heading in the same direction.  Face-to-face    discussions about Baloo, and BI Datawarehouse tools;  Tableau server and dashboards; MoFo Interim Contributor Dashboard and  the systems  behind it; + the Adhoc contribution logger.  MoFo point: Adam and Jbuck  SF Moco contacts:  David Boswell  Local Moco, but not SF: Anurag Phadke (Mountain View),  Collaborators: Chris D 

Bugzilla tags:[allhands][metrics]

Deliverable: [QUESTION: Adam, what is the concrete deliverable / ticket here?] 

===Landing the badges moonshot: Webmaker + Badgekit sprint===
*'''Lead''': Kate
*'''Collaborators''': An Me, Erik, Andrew, JP, Jbuck
*'''Goal: We will issue the Webmaker Super Mentor badge'''. We're a few short tickets away from being able to issue and approve Webmaker badges in Badgekit. Let's sprint towards completion.
*'''Deliverable''': Ship the Webmaker Super Mentor Badge, supporting the complete end-to-end user story: see, apply, review, issue, receive.
*'''Webmaker badges roadmap:''' [[Webmaker/Badges#Q2_Roadmap|Q2 Roadmap]]
*'''Bugzilla tags''': webmakerbadges, followup

<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"product": "webmaker",
"whiteboard": "[webmakerbadges][followup]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>

=== badges.mozilla.org Prototyping Party ===
*'''Lead''': Emily
*'''Collaborators''':
*'''Goal: Let's prototype this site's future'''. We will start with a look at what badges.mozilla.org was and who used it. Then we'll plan what it might become, and the larger vision and resources that will needed. Plus how it might it fit with the larger plan for MoFo and MoCo badges. Less yack, more hack.
*'''Time: Wednesday, 3:00 PM'''

<onlyinclude><div style="align:left;"><bugzilla>{
"product": "mozilla.org",
"whiteboard": "[badges]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}</bugzilla><div style="align:left;"></onlyinclude>

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/04nv-wox.png

AllHands/Funnel Building

2014-04-26T04:37:35Z

Brett Gaylor: /* Landing the badges moonshot: Webmaker + Badgekit sprint */

[[File:Funnel Building.png|175px|right]]
__TOC__
===Contributor Metrics: connecting the threads===
Time: Tuesday 10:00-12:00 
Goal:  Connecting the strands so we're heading in the same direction.  Face-to-face    discussions about Baloo, and BI Datawarehouse tools;  Tableau server and dashboards; MoFo Interim Contributor Dashboard and  the systems  behind it; + the Adhoc contribution logger.  MoFo point: Adam and Jbuck  SF Moco contacts:  David Boswell  Local Moco, but not SF: Anurag Phadke (Mountain View),  Collaborators: Chris D 

Bugzilla tags:[allhands][metrics]

Deliverable: [QUESTION: Adam, what is the concrete deliverable / ticket here?] 

===Landing the badges moonshot: Webmaker + Badgekit sprint===
*'''Lead''': Kate
*'''Collaborators''': An Me, Erik, Andrew, JP, Jbuck
*'''Goal: We will issue the Webmaker Super Mentor badge'''. We're a few short tickets away from being able to issue and approve Webmaker badges in Badgekit. Let's sprint towards completion.
*'''Deliverable''': Ship the Webmaker Super Mentor Badge, supporting the complete end-to-end user story: see, apply, review, issue, receive.
*'''Webmaker badges roadmap:''' [[Webmaker/Badges#Q2_Roadmap|Q2 Roadmap]]
*'''Bugzilla tags''': [webmakerbadges] [mvp]

<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"product": "webmaker",
"whiteboard": "[webmakerbadges][followup]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>

=== badges.mozilla.org Prototyping Party ===
*'''Lead''': Emily
*'''Collaborators''':
*'''Goal: Let's prototype this site's future'''. We will start with a look at what badges.mozilla.org was and who used it. Then we'll plan what it might become, and the larger vision and resources that will needed. Plus how it might it fit with the larger plan for MoFo and MoCo badges. Less yack, more hack.
*'''Time: Wednesday, 3:00 PM'''

<onlyinclude><div style="align:left;"><bugzilla>{
"product": "mozilla.org",
"whiteboard": "[badges]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}</bugzilla><div style="align:left;"></onlyinclude>

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/04nv-wox.png

AllHands/Funnel Feeding

2014-04-26T00:20:25Z

Brett Gaylor: /* Getting Real About Marketing + Press */

[[File:Funnel Feeding.png|300px|right]]
===Getting Real About Marketing + Press===
 This is critical. We have to pour as many people into the top of our funnel as possible. Press is a huge and proven way of doing  this. For example, if we landed two Lifehacker articles per quarter, we'd be tripling our users. We  don't currently have solid press kits/marketing kits for our products. Let's make some. Plus work out the details for how we're going to pitch Webmaker to press going forward.  Lead: Erica S and Lainie  Collaborators: Amira, Erin K, Kaitlin T, Erika D, Sabrina, Dave Steer, Hannah, Kaitlyn, Erin Kissane, Dan Sinker Note: Loop in Moco Marketing? Time Window: 3-4 hours Deliverables:  * press kit for Webmaker, Maker Party and Training Launch  * press kit for Open News  * press kit for Science Lab Out of scope for All Hands: * Document how to leverage MoCo PR resources * Press strategy for launching "Web Literacy Textbook" launch * Ship press kit for Hive * List of friendly educator press * Comms plan for Webmaker Training launch https://bugzilla.mozilla.org/show_bug.cgi?id=997376 https://bugzilla.mozilla.org/show_bug.cgi?id=997376 * Press strategy for Maker Party launch 

===Partnerships: becoming a closing machine===
 We now work from an integrated pipeline. It contains partners that bring us funding, contributors, or both. This means two things: (i) further integrating our recruitment, product, and management of partners, and (ii) become a closing machine. Goal: Cultural: Shift to being 'closers that care'. Practical: Log and start to action all of our leads. Account for managed growth through grants. Lead: Ben Moskowitz Collaborators: Geoff MacDougall, Matt Thompson, Hannah, Lynn Melander Moore, Amira Dhalla Time Window: 2 hours Deliverable: Prototype an interface between Webmaker requirements and Fundraising lead generation QUESTION: what does that deliverable mean? What are we going to document or make? +1 (GM) 
===Going Global: Three new markets for Webmaker in 2014===
 What they need from us and how we'll win. We have funded partnerships planned in Bangladesh, Brazil and more. Let's focus on where we are funded and do it well. Show where geographically anchored / regional funding is; talk about creating more visibility  about the data we have; leverage planned Maker Parties in these key locales; and measure where in the world Mozilla can make impact. Lead: Ben Moskowitz; Adam Lofting Collaborators: Michelle, Chris, Geoff, An-Me, Amira +1 (BG) +1 (MT)+1AMC +1 BM +1 (PLD) Deliverable: Document our plan for new markets ( and link to it here: https://wiki.mozilla.org/Webmaker/Markets https://wiki.mozilla.org/Webmaker/Markets ) Deliverable: Document a plan for informed, data-based decision making on global expansion <ul><li>Note: Synch this with the market and comms research MoCo is already doing </li></ul>
===Driving Mozilla-wide participation in Maker Party===
 From Open News to the Science Lab and beyond, let's make sure this year's Maker Party includes all areas of MoFo. This can also include how to leverage upcoming MozCamps, plus  Mozilla's new "gathering plan" for distributed events. Let's also pick a few likely MoCo groups and document with them what they might do as well.  Lead: Amira/Michelle Collaborators: Winston, WPR folks for Mozilla-spaces events Deliverable:  Open News and Science Lab document what they're going to do for Maker Party  Document with MDN what they might do as part of Maker Party Draft a Maker Party story and CTAs targeted directly at Mozilla community members <ul><li>(could be a draft WordPress landing page on the new Maker Party site. Then shipped to Mozilla.org or elsewhere.) </li></ul>
===Converting Maker Party event participants into contributors===
 How do we turn Webmaker and Maker Party event participants into users, supporters and contributors? This is one of the most important things we can do towards our 10k contributor goal this year. And it's hard. It will take a cross-team approach with engineers, community team and partnership teams working together. Let's get the key stakeholders together to agree on strategy and document a cross-team sprint together here:  https://wiki.mozilla.org/Webmaker/Events Lead: Brett + Matt Required: Brett, Matt, Amira, Gavin, Cassie Requested: Michelle, Kate Hudson, Lainie Context and reading: https://etherpad.mozilla.org/Events Deliverable: Get consensus with stakeholders. Then document our events roadmap. https://etherpad.mozilla.org/Events https://wiki.mozilla.org/Webmaker/Events 
===Project:Trust -- Mozilla Campaign Coordination===
 Trust is an emerging theme in many campaigns going on across Mozilla: marketing, advocacy, policy, engagement, education. The leads of the campaigns have agreed to start meeting to coordinate the work, maybe ship a shared platform or two. This is the first meeting of that group. Lead: Geoff MacDougall Collaborators: Dave Steer, Erica Sackin, Andrea Wood, Mary Ellen Muckerman, Eric Petitt, Michelle Thorne, Alex Fowler SF local  contacts: Dave Steer, Eric Petitt Proposed length: 90 mins Deliverable: Document our plan and next steps for leveraging Trust campaigns +1 (GM; this is going to happen) +1AMC 
===Maker Party: Real Life User Stories (the theatrical experience)===
 Let's role-play to see how ready we are. We've all spent a number of months building systems, content, funnels, and tools that let us engage, support, and provide value to our many  types of users, supporters, and contributors. On July 15th those  systems, content, and funnels will be put to the test. We need to  rehearse and drill our processes. This session will see us act out (literally)  the user stories in our engagement ladder work, making sure none of the users we need to engage run into  walls or black holes. Lead: Geoffrey MacDougall Collaborators: Amira Dhalla, Chris Lawrence, Matt Thompson Proposed Length: A morning Deliverable: A captivating theatrical experience directed by Geoffrey MacDougall, featuring a full cast of MoFos. Add to our current Engagement Ladder user stories where necessary. Triaged and prioritized  here: http://mzl.la/contribution_pathways 
===Hive Documentation===
 Goal: Ship pages of the Hive Cookbook. Documenting and outlining existing Hive practices, strategies, goals and thinking onto the Mozilla Wiki. Started here https://wiki.mozilla.org/Webmaker/Hive Lead: Chris L, Leah, Sam Katherine Collaborators: Robert, Elsa, Julia, Lainie, Karen Non MOFO invitee: Zakyia Harris Proposed length: 1/2 day Deliverables:   * Ship new Hive Cookbook pages for Hive Chicago, Toronto and NYC.  * Update main Hive Landing page and begin building out further Hive resource pages like FAQ 

===Webmaker + MDN: prepping for May workweek===
 Goal:  Determine, plot and start hacking on easy wins in preparation for the end of May     MDN/Webmaker workweek. Plus document larger strategic goals for collaborating with MDN going forward. Discuss the Thimble roadmap (and Thimble tutorials in particular) and see how MDN needs can be included. MoFo lead: Laura/Brett SF local contacts: Ali Proposed length: 1/4 day Deliverables:  * Train MDN staff to create Thimble tutorials.  * Update MDN staff on product vision for Thimble and Brackets.  * Transfer knowledge in creating MakeAPI galleries 
===New Communities Co-design session: make a page on mozilla.org===
 Lead: Dan/Erin Kissane Collaborators: Kaitlin, Dave, Studio MoFo Local SF contact: Jen Bersch (mozilla.org PM) Goal:  Collaborate & sprint on making a one-pager "New Communities" page  on Mozilla.org. Plus getting "News" and "Science" added to the  Mozilla.org "get involved" page. http://www.mozilla.org/contribute/ This can be a great way to tell the story around what Mozilla is doing  in these new spaces, plus drive referral traffic and contributors to  those projects.  time window: 6hrs, max  +1 DS +1 (KT) Deliverable: Ship the page. With copy and design that follows Mozilla.org style Write copy for getting "News" added to the "Get Involved" page Write copy for getting "Science" added to the "Get Involved" page  File the tickets with MoCo colleagues to get that work shipped to mozilla.org 
=== Building a diverse pool of Webmaker contributors ===
Beginning first with our code contributors, we want to ensure that all contributors feel welcome in our open source project. Let's first examine what condititions and guidelines we should establish, where we're doing well, and we're we need to improve. Then we'll turn this into an inviting "one stop shopping"page at developer.webmaker.org that can onboard new code contributors.

Lead::Kate 
Deliverables: 
Draft of Webmaker code contributor guidelines 
Prototype of developer.webmaker.org

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/pjvdd1t5.png

AllHands/Funnel Inside

2014-04-25T23:51:14Z

Brett Gaylor: /* Building a QA Community */

[[File:Funnel Inside.png|225px|right]]
===Learning from Users: getting good at usability testing===
 Let's do usability testing on our engagement ladder, to see where people are getting stuck and increase our conversation rate. Our engagement ladder is everything. We're asking users to perform a mall number of key calls to action and (like signing up for a   Webmaker  account, sharing a teaching kit, entering an event into our platform, etc.) How do we do smart usability testing against these tasks so we can see where users are getting stuck -- and capture quick wins to increase our conversion rate?  Context: http://mzl.la/Pu9ulB + http://openmatt.org/2014/04/04/product_testing/ Lead: Cassie/Karen Smith Collaborators: Cori Schauer  + Tony Santos (User research) + Kat Deliverable: Run a usability test for account creation, event creation, and the new /explore page. 
===Prepping the Webmaker/explore writing sprint===
Prepping for a book sprint to create an open "textbook" or "cookbook" for teaching web literacy. Let's get our roadmap ready for shipping awesome Webmaker teaching curriculum. Toronto will host a writing sprint May 7,8,9 to complete webmaker.org/explore.  Recognizing this piece of content is crucial to our successful launch this summer, we need to hit the ground running. We will make sure each attendees has an assigned Web Lit competency and  that the work is scoped so we can spend a full three days writing Lead (for prep and logistics): Matt Collaborators: Kat, Michelle, Claw, Cassie, Kate, Drushka, Fuzzy Deliverable: Document our roadmap. For shipping the textbook, plus celebrating the community contributing to it. (Kat's Webmaker series) 

===Prototyping together===
'''How to tell and sell the difference between prototype and product'''. Let's work out a process for how we turn prototypes into product that will keep us agile while allowing us to meet our current commitments. We did great work last quarter turning the Web Lit Map into an exciting content direction.  We've got great new extensions for the browser,  3rd   party app integration and more coming up. Let's keep this going,  and  also be clear about expectations for sales, partnerships, and   productization. Lead: Brett 
Collaborators: Atul, WebmakerUX team, Doug, Paula, Dev team, Fuzzy, Chloe, Mike Larrson, Jess Deliverable:  * Documentation for the life cycle of a prototype.  * Documentation for how to talk about and "sell" key current protoypes like the Web Lit Mapper.  

===Appmaker: Getting Input on User Value&nbsp===
 Goal: test Appmaker strategy against MoCo market research team analysis of the opportunity and need. Plus review user demographics and operators in each  Firefox OS market. We think there are gains in combining platform, marketplace, digital literacy. Are we teed up to provide value here? 
MoFo point: Bobby (+Ben) SF local  contacts: Ria Joy, if we can get her to come from Seattle, Cori Schauer Proposed length: 4-6 hours Deliverable:  
* Document Appmaker audience segmentation & analysis
* Document work plan for feeding audience research into Appmaker product strategy

===Working with the GSMA===
 Goal: design first set of engagements w/ GSMA around Spreadtrum phone, Appmaker, Webmaker. Plus produce a 15 slide aligment deck for internal stakeholders MoFo point: Mark (+Ben) SF  local contacts: Pete Scanlon, Ria Joy, Rick  Fant (a meeting at some point?), someone from  Bill Walker org, someone  from Christopher Lee org, Irina Sandu (voice?)  David Palomino (voice?) Proposed length: 4-6 hours Deliverable:  * Ship internal slide deck on the mobile development opportunity for Mozilla  * Scope 3 actionable demo collaborations between MoCo + MoFo 
===Review and iterate Webmaker.org information architecture===
 Goal: Take stock of all the pages on webmaker.org. Are they serving our needs? Where are there gaps? How might we improve our information architecture to support new pages like /explore and profiles? And how can we measure if its working? Lead: Cassie Collaborators: Matt, Kat, Kate, Adam Deliverable: A complete list of all current pages with "jobs" and notes on next steps for each Resource: Google doc: [https://docs.google.com/spreadsheets/d/1ejFHysKOLEGXynU6ZUQgUKn5AVlNgqDBtjrTyM8Zbk4/edit#gid=0 Every Page Has a Job] 

===Email like a Bawse===
 Goal: Now that we are sending out emails based on user events, let's make sure that they're as effective as can be. Lead: Andrea: Collaborators: Jbuck (infra), Aki (figure out HTML emails), Sabrina (design), Drushka (words) Deliverables: * Review existing emails for engagement ladder * Add "email drafting" to the Encyclopedia Best Practica * Design attractive HTML emails sent from Webmaker.org * Build proper HTML email delivery for Webmaker postal service 

=== Building a QA Community ===
Lead: Jbuck 
The QA community has begun to make tests for Webmaker.org (see https://github.com/mozilla/webmaker-tests/issues/37#issuecomment-41444213)
Let's discuss with the QA team how we can build a great community of testers, and also, how to be great at tests.
 
Collaborators: rbillings, JP, Cade 
Deliverables: A set of tickets about what to test next.
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/9csx7tfm.png

AllHands/Funnel Inside

2014-04-25T23:50:33Z

Brett Gaylor:

[[File:Funnel Inside.png|225px|right]]
===Learning from Users: getting good at usability testing===
 Let's do usability testing on our engagement ladder, to see where people are getting stuck and increase our conversation rate. Our engagement ladder is everything. We're asking users to perform a mall number of key calls to action and (like signing up for a   Webmaker  account, sharing a teaching kit, entering an event into our platform, etc.) How do we do smart usability testing against these tasks so we can see where users are getting stuck -- and capture quick wins to increase our conversion rate?  Context: http://mzl.la/Pu9ulB + http://openmatt.org/2014/04/04/product_testing/ Lead: Cassie/Karen Smith Collaborators: Cori Schauer  + Tony Santos (User research) + Kat Deliverable: Run a usability test for account creation, event creation, and the new /explore page. 
===Prepping the Webmaker/explore writing sprint===
Prepping for a book sprint to create an open "textbook" or "cookbook" for teaching web literacy. Let's get our roadmap ready for shipping awesome Webmaker teaching curriculum. Toronto will host a writing sprint May 7,8,9 to complete webmaker.org/explore.  Recognizing this piece of content is crucial to our successful launch this summer, we need to hit the ground running. We will make sure each attendees has an assigned Web Lit competency and  that the work is scoped so we can spend a full three days writing Lead (for prep and logistics): Matt Collaborators: Kat, Michelle, Claw, Cassie, Kate, Drushka, Fuzzy Deliverable: Document our roadmap. For shipping the textbook, plus celebrating the community contributing to it. (Kat's Webmaker series) 

===Prototyping together===
'''How to tell and sell the difference between prototype and product'''. Let's work out a process for how we turn prototypes into product that will keep us agile while allowing us to meet our current commitments. We did great work last quarter turning the Web Lit Map into an exciting content direction.  We've got great new extensions for the browser,  3rd   party app integration and more coming up. Let's keep this going,  and  also be clear about expectations for sales, partnerships, and   productization. Lead: Brett 
Collaborators: Atul, WebmakerUX team, Doug, Paula, Dev team, Fuzzy, Chloe, Mike Larrson, Jess Deliverable:  * Documentation for the life cycle of a prototype.  * Documentation for how to talk about and "sell" key current protoypes like the Web Lit Mapper.  

===Appmaker: Getting Input on User Value&nbsp===
 Goal: test Appmaker strategy against MoCo market research team analysis of the opportunity and need. Plus review user demographics and operators in each  Firefox OS market. We think there are gains in combining platform, marketplace, digital literacy. Are we teed up to provide value here? 
MoFo point: Bobby (+Ben) SF local  contacts: Ria Joy, if we can get her to come from Seattle, Cori Schauer Proposed length: 4-6 hours Deliverable:  
* Document Appmaker audience segmentation & analysis
* Document work plan for feeding audience research into Appmaker product strategy

===Working with the GSMA===
 Goal: design first set of engagements w/ GSMA around Spreadtrum phone, Appmaker, Webmaker. Plus produce a 15 slide aligment deck for internal stakeholders MoFo point: Mark (+Ben) SF  local contacts: Pete Scanlon, Ria Joy, Rick  Fant (a meeting at some point?), someone from  Bill Walker org, someone  from Christopher Lee org, Irina Sandu (voice?)  David Palomino (voice?) Proposed length: 4-6 hours Deliverable:  * Ship internal slide deck on the mobile development opportunity for Mozilla  * Scope 3 actionable demo collaborations between MoCo + MoFo 
===Review and iterate Webmaker.org information architecture===
 Goal: Take stock of all the pages on webmaker.org. Are they serving our needs? Where are there gaps? How might we improve our information architecture to support new pages like /explore and profiles? And how can we measure if its working? Lead: Cassie Collaborators: Matt, Kat, Kate, Adam Deliverable: A complete list of all current pages with "jobs" and notes on next steps for each Resource: Google doc: [https://docs.google.com/spreadsheets/d/1ejFHysKOLEGXynU6ZUQgUKn5AVlNgqDBtjrTyM8Zbk4/edit#gid=0 Every Page Has a Job] 

===Email like a Bawse===
 Goal: Now that we are sending out emails based on user events, let's make sure that they're as effective as can be. Lead: Andrea: Collaborators: Jbuck (infra), Aki (figure out HTML emails), Sabrina (design), Drushka (words) Deliverables: * Review existing emails for engagement ladder * Add "email drafting" to the Encyclopedia Best Practica * Design attractive HTML emails sent from Webmaker.org * Build proper HTML email delivery for Webmaker postal service 

=== Building a QA Community ===
Lead: Jbuck
The QA community has begun to make tests for Webmaker.org (see https://github.com/mozilla/webmaker-tests/issues/37#issuecomment-41444213)
Let's discuss with the QA team how we can build a great community of testers, and also, how to be great at tests.
Collaborators: rbillings, JP, Cade
Deliverables: A set of tickets about what to test next.
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/9csx7tfm.png

AllHands/Funnel Feeding

2014-04-25T23:40:38Z

Brett Gaylor: /* Building a diverse pool of Webmaker contributors */

[[File:Funnel Feeding.png|300px|right]]
===Getting Real About Marketing + Press===
 This is critical. We have to pour as many people into the top of our funnel as possible. Press is a huge and proven way of doing  this. For example, if we landed two Lifehacker articles per quarter, we'd be tripling our users. We  don't currently have solid press kits/marketing kits for our products. Let's make some. Plus work out the details for how we're going to pitch Webmaker to press going forward.  Lead: Erica S and Lainie  Collaborators: Amira, Erin K, Kaitlin T, Erika D, Sabrina, Dave Steer, Hannah Note: Dan Sinker and Erin Kisane could probably also help tremendously, as could MoCo Comms and Marketing folks Time Window: 3-4 hours +1 GM  + CL +1AMC +BG Deliverables:  * press kit for Webmaker, Maker Party and Training Launch  * press kit for Open News  * press kit for Science Lab Out of scope for All Hands: * Document how to leverage MoCo PR resources * Press strategy for launching "Web Literacy Textbook" launch * Ship press kit for Hive * List of friendly educator press * Comms plan for Webmaker Training launch https://bugzilla.mozilla.org/show_bug.cgi?id=997376 https://bugzilla.mozilla.org/show_bug.cgi?id=997376 * Press strategy for Maker Party launch 
===Partnerships: becoming a closing machine===
 We now work from an integrated pipeline. It contains partners that bring us funding, contributors, or both. This means two things: (i) further integrating our recruitment, product, and management of partners, and (ii) become a closing machine. Goal: Cultural: Shift to being 'closers that care'. Practical: Log and start to action all of our leads. Account for managed growth through grants. Lead: Ben Moskowitz Collaborators: Geoff MacDougall, Matt Thompson, Hannah, Lynn Melander Moore, Amira Dhalla Time Window: 2 hours Deliverable: Prototype an interface between Webmaker requirements and Fundraising lead generation QUESTION: what does that deliverable mean? What are we going to document or make? +1 (GM) 
===Going Global: Three new markets for Webmaker in 2014===
 What they need from us and how we'll win. We have funded partnerships planned in Bangladesh, Brazil and more. Let's focus on where we are funded and do it well. Show where geographically anchored / regional funding is; talk about creating more visibility  about the data we have; leverage planned Maker Parties in these key locales; and measure where in the world Mozilla can make impact. Lead: Ben Moskowitz; Adam Lofting Collaborators: Michelle, Chris, Geoff, An-Me, Amira +1 (BG) +1 (MT)+1AMC +1 BM +1 (PLD) Deliverable: Document our plan for new markets ( and link to it here: https://wiki.mozilla.org/Webmaker/Markets https://wiki.mozilla.org/Webmaker/Markets ) Deliverable: Document a plan for informed, data-based decision making on global expansion <ul><li>Note: Synch this with the market and comms research MoCo is already doing </li></ul>
===Driving Mozilla-wide participation in Maker Party===
 From Open News to the Science Lab and beyond, let's make sure this year's Maker Party includes all areas of MoFo. This can also include how to leverage upcoming MozCamps, plus  Mozilla's new "gathering plan" for distributed events. Let's also pick a few likely MoCo groups and document with them what they might do as well.  Lead: Amira/Michelle Collaborators: Winston, WPR folks for Mozilla-spaces events Deliverable:  Open News and Science Lab document what they're going to do for Maker Party  Document with MDN what they might do as part of Maker Party Draft a Maker Party story and CTAs targeted directly at Mozilla community members <ul><li>(could be a draft WordPress landing page on the new Maker Party site. Then shipped to Mozilla.org or elsewhere.) </li></ul>
===Converting Maker Party event participants into contributors===
 How do we turn Webmaker and Maker Party event participants into users, supporters and contributors? This is one of the most important things we can do towards our 10k contributor goal this year. And it's hard. It will take a cross-team approach with engineers, community team and partnership teams working together. Let's get the key stakeholders together to agree on strategy and document a cross-team sprint together here:  https://wiki.mozilla.org/Webmaker/Events Lead: Brett + Matt Required: Brett, Matt, Amira, Gavin, Cassie Requested: Michelle, Kate Hudson, Lainie Context and reading: https://etherpad.mozilla.org/Events Deliverable: Get consensus with stakeholders. Then document our events roadmap. https://etherpad.mozilla.org/Events https://wiki.mozilla.org/Webmaker/Events 
===Project:Trust -- Mozilla Campaign Coordination===
 Trust is an emerging theme in many campaigns going on across Mozilla: marketing, advocacy, policy, engagement, education. The leads of the campaigns have agreed to start meeting to coordinate the work, maybe ship a shared platform or two. This is the first meeting of that group. Lead: Geoff MacDougall Collaborators: Dave Steer, Erica Sackin, Andrea Wood, Mary Ellen Muckerman, Eric Petitt, Michelle Thorne, Alex Fowler SF local  contacts: Dave Steer, Eric Petitt Proposed length: 90 mins Deliverable: Document our plan and next steps for leveraging Trust campaigns +1 (GM; this is going to happen) +1AMC 
===Maker Party: Real Life User Stories (the theatrical experience)===
 Let's role-play to see how ready we are. We've all spent a number of months building systems, content, funnels, and tools that let us engage, support, and provide value to our many  types of users, supporters, and contributors. On July 15th those  systems, content, and funnels will be put to the test. We need to  rehearse and drill our processes. This session will see us act out (literally)  the user stories in our engagement ladder work, making sure none of the users we need to engage run into  walls or black holes. Lead: Geoffrey MacDougall Collaborators: Amira Dhalla, Chris Lawrence, Matt Thompson Proposed Length: A morning Deliverable: A captivating theatrical experience directed by Geoffrey MacDougall, featuring a full cast of MoFos. Add to our current Engagement Ladder user stories where necessary. Triaged and prioritized  here: http://mzl.la/contribution_pathways 
===Hive Documentation===
 Goal: Ship pages of the Hive Cookbook. Documenting and outlining existing Hive practices, strategies, goals and thinking onto the Mozilla Wiki. Started here https://wiki.mozilla.org/Webmaker/Hive Lead: Chris L, Leah, Sam Katherine Collaborators: Robert, Elsa, Julia, Lainie, Karen Non MOFO invitee: Zakyia Harris Proposed length: 1/2 day Deliverables:   * Ship new Hive Cookbook pages for Hive Chicago, Toronto and NYC.  * Update main Hive Landing page and begin building out further Hive resource pages like FAQ 

===Webmaker + MDN: prepping for May workweek===
 Goal:  Determine, plot and start hacking on easy wins in preparation for the end of May     MDN/Webmaker workweek. Plus document larger strategic goals for collaborating with MDN going forward. Discuss the Thimble roadmap (and Thimble tutorials in particular) and see how MDN needs can be included. MoFo lead: Laura/Brett SF local contacts: Ali Proposed length: 1/4 day Deliverables:  * Train MDN staff to create Thimble tutorials.  * Update MDN staff on product vision for Thimble and Brackets.  * Transfer knowledge in creating MakeAPI galleries 
===New Communities Co-design session: make a page on mozilla.org===
 Lead: Dan/Erin Kissane Collaborators: Kaitlin, Dave, Studio MoFo Local SF contact: Jen Bersch (mozilla.org PM) Goal:  Collaborate & sprint on making a one-pager "New Communities" page  on Mozilla.org. Plus getting "News" and "Science" added to the  Mozilla.org "get involved" page. http://www.mozilla.org/contribute/ This can be a great way to tell the story around what Mozilla is doing  in these new spaces, plus drive referral traffic and contributors to  those projects.  time window: 6hrs, max  +1 DS +1 (KT) Deliverable: Ship the page. With copy and design that follows Mozilla.org style Write copy for getting "News" added to the "Get Involved" page Write copy for getting "Science" added to the "Get Involved" page  File the tickets with MoCo colleagues to get that work shipped to mozilla.org 
=== Building a diverse pool of Webmaker contributors ===
Beginning first with our code contributors, we want to ensure that all contributors feel welcome in our open source project. Let's first examine what condititions and guidelines we should establish, where we're doing well, and we're we need to improve. Then we'll turn this into an inviting "one stop shopping"page at developer.webmaker.org that can onboard new code contributors.

Lead::Kate 
Deliverables: 
Draft of Webmaker code contributor guidelines 
Prototype of developer.webmaker.org

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/pjvdd1t5.png

AllHands/Funnel Feeding

2014-04-25T23:40:24Z

Brett Gaylor: /* Building a diverse pool of Webmaker contributors */

[[File:Funnel Feeding.png|300px|right]]
===Getting Real About Marketing + Press===
 This is critical. We have to pour as many people into the top of our funnel as possible. Press is a huge and proven way of doing  this. For example, if we landed two Lifehacker articles per quarter, we'd be tripling our users. We  don't currently have solid press kits/marketing kits for our products. Let's make some. Plus work out the details for how we're going to pitch Webmaker to press going forward.  Lead: Erica S and Lainie  Collaborators: Amira, Erin K, Kaitlin T, Erika D, Sabrina, Dave Steer, Hannah Note: Dan Sinker and Erin Kisane could probably also help tremendously, as could MoCo Comms and Marketing folks Time Window: 3-4 hours +1 GM  + CL +1AMC +BG Deliverables:  * press kit for Webmaker, Maker Party and Training Launch  * press kit for Open News  * press kit for Science Lab Out of scope for All Hands: * Document how to leverage MoCo PR resources * Press strategy for launching "Web Literacy Textbook" launch * Ship press kit for Hive * List of friendly educator press * Comms plan for Webmaker Training launch https://bugzilla.mozilla.org/show_bug.cgi?id=997376 https://bugzilla.mozilla.org/show_bug.cgi?id=997376 * Press strategy for Maker Party launch 
===Partnerships: becoming a closing machine===
 We now work from an integrated pipeline. It contains partners that bring us funding, contributors, or both. This means two things: (i) further integrating our recruitment, product, and management of partners, and (ii) become a closing machine. Goal: Cultural: Shift to being 'closers that care'. Practical: Log and start to action all of our leads. Account for managed growth through grants. Lead: Ben Moskowitz Collaborators: Geoff MacDougall, Matt Thompson, Hannah, Lynn Melander Moore, Amira Dhalla Time Window: 2 hours Deliverable: Prototype an interface between Webmaker requirements and Fundraising lead generation QUESTION: what does that deliverable mean? What are we going to document or make? +1 (GM) 
===Going Global: Three new markets for Webmaker in 2014===
 What they need from us and how we'll win. We have funded partnerships planned in Bangladesh, Brazil and more. Let's focus on where we are funded and do it well. Show where geographically anchored / regional funding is; talk about creating more visibility  about the data we have; leverage planned Maker Parties in these key locales; and measure where in the world Mozilla can make impact. Lead: Ben Moskowitz; Adam Lofting Collaborators: Michelle, Chris, Geoff, An-Me, Amira +1 (BG) +1 (MT)+1AMC +1 BM +1 (PLD) Deliverable: Document our plan for new markets ( and link to it here: https://wiki.mozilla.org/Webmaker/Markets https://wiki.mozilla.org/Webmaker/Markets ) Deliverable: Document a plan for informed, data-based decision making on global expansion <ul><li>Note: Synch this with the market and comms research MoCo is already doing </li></ul>
===Driving Mozilla-wide participation in Maker Party===
 From Open News to the Science Lab and beyond, let's make sure this year's Maker Party includes all areas of MoFo. This can also include how to leverage upcoming MozCamps, plus  Mozilla's new "gathering plan" for distributed events. Let's also pick a few likely MoCo groups and document with them what they might do as well.  Lead: Amira/Michelle Collaborators: Winston, WPR folks for Mozilla-spaces events Deliverable:  Open News and Science Lab document what they're going to do for Maker Party  Document with MDN what they might do as part of Maker Party Draft a Maker Party story and CTAs targeted directly at Mozilla community members <ul><li>(could be a draft WordPress landing page on the new Maker Party site. Then shipped to Mozilla.org or elsewhere.) </li></ul>
===Converting Maker Party event participants into contributors===
 How do we turn Webmaker and Maker Party event participants into users, supporters and contributors? This is one of the most important things we can do towards our 10k contributor goal this year. And it's hard. It will take a cross-team approach with engineers, community team and partnership teams working together. Let's get the key stakeholders together to agree on strategy and document a cross-team sprint together here:  https://wiki.mozilla.org/Webmaker/Events Lead: Brett + Matt Required: Brett, Matt, Amira, Gavin, Cassie Requested: Michelle, Kate Hudson, Lainie Context and reading: https://etherpad.mozilla.org/Events Deliverable: Get consensus with stakeholders. Then document our events roadmap. https://etherpad.mozilla.org/Events https://wiki.mozilla.org/Webmaker/Events 
===Project:Trust -- Mozilla Campaign Coordination===
 Trust is an emerging theme in many campaigns going on across Mozilla: marketing, advocacy, policy, engagement, education. The leads of the campaigns have agreed to start meeting to coordinate the work, maybe ship a shared platform or two. This is the first meeting of that group. Lead: Geoff MacDougall Collaborators: Dave Steer, Erica Sackin, Andrea Wood, Mary Ellen Muckerman, Eric Petitt, Michelle Thorne, Alex Fowler SF local  contacts: Dave Steer, Eric Petitt Proposed length: 90 mins Deliverable: Document our plan and next steps for leveraging Trust campaigns +1 (GM; this is going to happen) +1AMC 
===Maker Party: Real Life User Stories (the theatrical experience)===
 Let's role-play to see how ready we are. We've all spent a number of months building systems, content, funnels, and tools that let us engage, support, and provide value to our many  types of users, supporters, and contributors. On July 15th those  systems, content, and funnels will be put to the test. We need to  rehearse and drill our processes. This session will see us act out (literally)  the user stories in our engagement ladder work, making sure none of the users we need to engage run into  walls or black holes. Lead: Geoffrey MacDougall Collaborators: Amira Dhalla, Chris Lawrence, Matt Thompson Proposed Length: A morning Deliverable: A captivating theatrical experience directed by Geoffrey MacDougall, featuring a full cast of MoFos. Add to our current Engagement Ladder user stories where necessary. Triaged and prioritized  here: http://mzl.la/contribution_pathways 
===Hive Documentation===
 Goal: Ship pages of the Hive Cookbook. Documenting and outlining existing Hive practices, strategies, goals and thinking onto the Mozilla Wiki. Started here https://wiki.mozilla.org/Webmaker/Hive Lead: Chris L, Leah, Sam Katherine Collaborators: Robert, Elsa, Julia, Lainie, Karen Non MOFO invitee: Zakyia Harris Proposed length: 1/2 day Deliverables:   * Ship new Hive Cookbook pages for Hive Chicago, Toronto and NYC.  * Update main Hive Landing page and begin building out further Hive resource pages like FAQ 

===Webmaker + MDN: prepping for May workweek===
 Goal:  Determine, plot and start hacking on easy wins in preparation for the end of May     MDN/Webmaker workweek. Plus document larger strategic goals for collaborating with MDN going forward. Discuss the Thimble roadmap (and Thimble tutorials in particular) and see how MDN needs can be included. MoFo lead: Laura/Brett SF local contacts: Ali Proposed length: 1/4 day Deliverables:  * Train MDN staff to create Thimble tutorials.  * Update MDN staff on product vision for Thimble and Brackets.  * Transfer knowledge in creating MakeAPI galleries 
===New Communities Co-design session: make a page on mozilla.org===
 Lead: Dan/Erin Kissane Collaborators: Kaitlin, Dave, Studio MoFo Local SF contact: Jen Bersch (mozilla.org PM) Goal:  Collaborate & sprint on making a one-pager "New Communities" page  on Mozilla.org. Plus getting "News" and "Science" added to the  Mozilla.org "get involved" page. http://www.mozilla.org/contribute/ This can be a great way to tell the story around what Mozilla is doing  in these new spaces, plus drive referral traffic and contributors to  those projects.  time window: 6hrs, max  +1 DS +1 (KT) Deliverable: Ship the page. With copy and design that follows Mozilla.org style Write copy for getting "News" added to the "Get Involved" page Write copy for getting "Science" added to the "Get Involved" page  File the tickets with MoCo colleagues to get that work shipped to mozilla.org 
=== Building a diverse pool of Webmaker contributors ===
Beginning first with our code contributors, we want to ensure that all contributors feel welcome in our open source project. Let's first examine what condititions and guidelines we should establish, where we're doing well, and we're we need to improve. Then we'll turn this into an inviting "one stop shopping"page at developer.webmaker.org that can onboard new code contributors.

Lead::Kate 
Deliverables: 
Draft of Webmaker code contributor guidelines
Prototype of developer.webmaker.org

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/pjvdd1t5.png

AllHands/Funnel Feeding

2014-04-25T23:08:29Z

Brett Gaylor:

[[File:Funnel Feeding.png|300px|right]]
===Getting Real About Marketing + Press===
 This is critical. We have to pour as many people into the top of our funnel as possible. Press is a huge and proven way of doing  this. For example, if we landed two Lifehacker articles per quarter, we'd be tripling our users. We  don't currently have solid press kits/marketing kits for our products. Let's make some. Plus work out the details for how we're going to pitch Webmaker to press going forward.  Lead: Erica S and Lainie  Collaborators: Amira, Erin K, Kaitlin T, Erika D, Sabrina, Dave Steer, Hannah Note: Dan Sinker and Erin Kisane could probably also help tremendously, as could MoCo Comms and Marketing folks Time Window: 3-4 hours +1 GM  + CL +1AMC +BG Deliverables:  * press kit for Webmaker, Maker Party and Training Launch  * press kit for Open News  * press kit for Science Lab Out of scope for All Hands: * Document how to leverage MoCo PR resources * Press strategy for launching "Web Literacy Textbook" launch * Ship press kit for Hive * List of friendly educator press * Comms plan for Webmaker Training launch https://bugzilla.mozilla.org/show_bug.cgi?id=997376 https://bugzilla.mozilla.org/show_bug.cgi?id=997376 * Press strategy for Maker Party launch 
===Partnerships: becoming a closing machine===
 We now work from an integrated pipeline. It contains partners that bring us funding, contributors, or both. This means two things: (i) further integrating our recruitment, product, and management of partners, and (ii) become a closing machine. Goal: Cultural: Shift to being 'closers that care'. Practical: Log and start to action all of our leads. Account for managed growth through grants. Lead: Ben Moskowitz Collaborators: Geoff MacDougall, Matt Thompson, Hannah, Lynn Melander Moore, Amira Dhalla Time Window: 2 hours Deliverable: Prototype an interface between Webmaker requirements and Fundraising lead generation QUESTION: what does that deliverable mean? What are we going to document or make? +1 (GM) 
===Going Global: Three new markets for Webmaker in 2014===
 What they need from us and how we'll win. We have funded partnerships planned in Bangladesh, Brazil and more. Let's focus on where we are funded and do it well. Show where geographically anchored / regional funding is; talk about creating more visibility  about the data we have; leverage planned Maker Parties in these key locales; and measure where in the world Mozilla can make impact. Lead: Ben Moskowitz; Adam Lofting Collaborators: Michelle, Chris, Geoff, An-Me, Amira +1 (BG) +1 (MT)+1AMC +1 BM +1 (PLD) Deliverable: Document our plan for new markets ( and link to it here: https://wiki.mozilla.org/Webmaker/Markets https://wiki.mozilla.org/Webmaker/Markets ) Deliverable: Document a plan for informed, data-based decision making on global expansion <ul><li>Note: Synch this with the market and comms research MoCo is already doing </li></ul>
===Driving Mozilla-wide participation in Maker Party===
 From Open News to the Science Lab and beyond, let's make sure this year's Maker Party includes all areas of MoFo. This can also include how to leverage upcoming MozCamps, plus  Mozilla's new "gathering plan" for distributed events. Let's also pick a few likely MoCo groups and document with them what they might do as well.  Lead: Amira/Michelle Collaborators: Winston, WPR folks for Mozilla-spaces events Deliverable:  Open News and Science Lab document what they're going to do for Maker Party  Document with MDN what they might do as part of Maker Party Draft a Maker Party story and CTAs targeted directly at Mozilla community members <ul><li>(could be a draft WordPress landing page on the new Maker Party site. Then shipped to Mozilla.org or elsewhere.) </li></ul>
===Converting Maker Party event participants into contributors===
 How do we turn Webmaker and Maker Party event participants into users, supporters and contributors? This is one of the most important things we can do towards our 10k contributor goal this year. And it's hard. It will take a cross-team approach with engineers, community team and partnership teams working together. Let's get the key stakeholders together to agree on strategy and document a cross-team sprint together here:  https://wiki.mozilla.org/Webmaker/Events Lead: Brett + Matt Required: Brett, Matt, Amira, Gavin, Cassie Requested: Michelle, Kate Hudson, Lainie Context and reading: https://etherpad.mozilla.org/Events Deliverable: Get consensus with stakeholders. Then document our events roadmap. https://etherpad.mozilla.org/Events https://wiki.mozilla.org/Webmaker/Events 
===Project:Trust -- Mozilla Campaign Coordination===
 Trust is an emerging theme in many campaigns going on across Mozilla: marketing, advocacy, policy, engagement, education. The leads of the campaigns have agreed to start meeting to coordinate the work, maybe ship a shared platform or two. This is the first meeting of that group. Lead: Geoff MacDougall Collaborators: Dave Steer, Erica Sackin, Andrea Wood, Mary Ellen Muckerman, Eric Petitt, Michelle Thorne, Alex Fowler SF local  contacts: Dave Steer, Eric Petitt Proposed length: 90 mins Deliverable: Document our plan and next steps for leveraging Trust campaigns +1 (GM; this is going to happen) +1AMC 
===Maker Party: Real Life User Stories (the theatrical experience)===
 Let's role-play to see how ready we are. We've all spent a number of months building systems, content, funnels, and tools that let us engage, support, and provide value to our many  types of users, supporters, and contributors. On July 15th those  systems, content, and funnels will be put to the test. We need to  rehearse and drill our processes. This session will see us act out (literally)  the user stories in our engagement ladder work, making sure none of the users we need to engage run into  walls or black holes. Lead: Geoffrey MacDougall Collaborators: Amira Dhalla, Chris Lawrence, Matt Thompson Proposed Length: A morning Deliverable: A captivating theatrical experience directed by Geoffrey MacDougall, featuring a full cast of MoFos. Add to our current Engagement Ladder user stories where necessary. Triaged and prioritized  here: http://mzl.la/contribution_pathways 
===Hive Documentation===
 Goal: Ship pages of the Hive Cookbook. Documenting and outlining existing Hive practices, strategies, goals and thinking onto the Mozilla Wiki. Started here https://wiki.mozilla.org/Webmaker/Hive Lead: Chris L, Leah, Sam Katherine Collaborators: Robert, Elsa, Julia, Lainie, Karen Non MOFO invitee: Zakyia Harris Proposed length: 1/2 day Deliverables:   * Ship new Hive Cookbook pages for Hive Chicago, Toronto and NYC.  * Update main Hive Landing page and begin building out further Hive resource pages like FAQ 

===Webmaker + MDN: prepping for May workweek===
 Goal:  Determine, plot and start hacking on easy wins in preparation for the end of May     MDN/Webmaker workweek. Plus document larger strategic goals for collaborating with MDN going forward. Discuss the Thimble roadmap (and Thimble tutorials in particular) and see how MDN needs can be included. MoFo lead: Laura/Brett SF local contacts: Ali Proposed length: 1/4 day Deliverables:  * Train MDN staff to create Thimble tutorials.  * Update MDN staff on product vision for Thimble and Brackets.  * Transfer knowledge in creating MakeAPI galleries 
===New Communities Co-design session: make a page on mozilla.org===
 Lead: Dan/Erin Kissane Collaborators: Kaitlin, Dave, Studio MoFo Local SF contact: Jen Bersch (mozilla.org PM) Goal:  Collaborate & sprint on making a one-pager "New Communities" page  on Mozilla.org. Plus getting "News" and "Science" added to the  Mozilla.org "get involved" page. http://www.mozilla.org/contribute/ This can be a great way to tell the story around what Mozilla is doing  in these new spaces, plus drive referral traffic and contributors to  those projects.  time window: 6hrs, max  +1 DS +1 (KT) Deliverable: Ship the page. With copy and design that follows Mozilla.org style Write copy for getting "News" added to the "Get Involved" page Write copy for getting "Science" added to the "Get Involved" page  File the tickets with MoCo colleagues to get that work shipped to mozilla.org 
=== Building a diverse pool of Webmaker contributors ===
Beginning first with our code contributors, we want to ensure that all contributors feel welcome in our open source project. Let's first examine what condititions and guidelines we should establish, where we're doing well, and we're we need to improve. Then we'll turn this into an inviting "one stop shopping"

Deliverables: 
Draft of Webmaker code contributor guidelines

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/pjvdd1t5.png