MozillaWiki

AllHands: Difference between revisions

Page Discussion

AllHands (view source)

Revision as of 15:11, 11 April 2018

8,340 bytes added ,  11 April 2018
this is not the allhands you're looking for
(this is not the allhands you're looking for)
 
(37 intermediate revisions by 17 users not shown)
Line 1: Line 1:
[[File:AllHandsRise.png|600px]]
<div style="padding:1em; font-size:1.5em; font-weight:bold; background: yellow">
This page is an archive of the 2014 Q1 Mozilla Foundation All Hands.
 
For Mozilla All Hands meetings 2014 December to present, see:
* [[All Hands]]
</div>
 
----
[[File:Crazy-mofos.gif]]
=MoFo 2014 All Hands=
=MoFo 2014 All Hands=
* '''Schedule'''   https://etherpad.mozilla.org/allhands2014schedule
* '''What we got done''' https://wiki.mozilla.org/AllHands/Done
* '''Logistics'''  https://etherpad.mozilla.org/All-Hands-logistics
* '''Why we did it''' https://wiki.mozilla.org/AllHands/Story
* '''Story''' https://wiki.mozilla.org/AllHands/Story
* '''Demos''' https://etherpad.mozilla.org/All-Hands-demos
* '''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]=
 
=[https://wiki.mozilla.org/AllHands/Workshops Workshops]=
[[File:Workshops.png|200px|left]]<br><br><br><br><br><br><br><br><br><br><br>
[[File:Workshops.png|200px|left]]<br><br><br><br><br><br><br><br><br><br><br>


=Scrum=
=What we worked on=
==Tues==
 
===Contributor Metrics: connecting the threads===
===Contributor Metrics: connecting the threads===
<b>When</b>: Tues 10:00-12:00 (this scheduled time is a moco/mofo catch-up meeting)<br>
<b>When</b>: Tues 10:00-12:00 (this scheduled time is a moco/mofo catch-up meeting)<br>
Line 37: Line 42:
===Going Global: Three new markets for Webmaker in 2014===
===Going Global: Three new markets for Webmaker in 2014===
<b>When:</b> Tues (anytime)<br>
<b>When:</b> Tues (anytime)<br>
<br/><b>What they need from us and how we'll win</b>. 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&nbsp; about the data we have; leverage planned Maker Parties in these key locales; and measure where in the world Mozilla can make impact.<br
<br/><b>What they need from us and how we'll win</b>. 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&nbsp; 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.<br
/><b>Lead</b>: Ben Moskowitz; Adam Lofting<br
/><b>Lead</b>: Ben Moskowitz; Adam Lofting<br
/><b>Collaborators</b>: Michelle, Chris, Geoff, An-Me, Amira<br
/><b>Collaborators</b>: Kat, Karen, Michelle, Chris, Geoff, An-Me, Amira<br
/>
/>
<b>[http://mzl.la/1hASFMO Tag]</b>: [allhands][global]
<b>[http://mzl.la/1hASFMO Tag]</b>: [allhands][global]
Line 78: Line 83:
</div>
</div>
</onlyinclude>
</onlyinclude>


===Getting real about press and marketing: Press Kits===
===Getting real about press and marketing: Press Kits===
Line 123: Line 127:
</onlyinclude>
</onlyinclude>


==Wed==
===Documentation and process: How we support our engagement work ===
<b>Time</b>: Tuesday morning<br
/>
<b>Lead</b>: Erika Owens, Leah Gilliam<br
/><b>Collaborators</b>: <br
/><b>Local SF contact</b>: <br
/><b>Goal</b>We'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.<br
/>'''Length''':? <br
/>
'''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 ===
<br/><b>From Open News to the Science Lab and beyond, let's make sure this year's Maker Party includes all areas of MoFo</b>. This can also include how to leverage upcoming MozCamps, plus&nbsp; 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.&nbsp;<br
/><b>Lead</b>: Amira/Michelle<br
/><b>Collaborators: </b>Winston, WPR folks for Mozilla-spaces events<br
/>
<b>[http://mzl.la/PEbrMr Tag]</b>: [allhands][mozmakerparty]<br>
<b>When:</b> Tuesday afternoon. Talk to Winston & WPR separately<br>
<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.<br>
<b>'''Lead''': </b>Laura<br>
<b>'''Collaborators''': </b>Lainie, Mozilla Reps, Cassie, Jbuck, Michelle, William<br>
<b>Tags</b>: [allhands][training]<br>
<b>When and where</b>: Tuesday morning, community space <br>
<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.''' <br>
<b>'''Lead''': </b>Sarah, Misty, Michelle<br>
<b>'''Collaborators''': </b>Anyone who wants to drop in!<br>
<b>Tags</b>: [allhands] [mozfest]<br>
<b>When and where</b>: Tuesday afternoon, Foxhole open space <br>
<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>
 
<br>
===Hive Badges MVP: Determining the criteria of the Hive Community Member badge===
<b>Time</b>: 9:30 Wednesday
<br/><b>At the Summit to Reconnect Learning in Redwood City this past February, we pledged to ship Hive badges by summer 2014.</b> 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.
<br/><b>Context</b>: https://omnignorant.makes.org/thimble/hive-global-badges-update-march-24-2014
<br/><b>Lead</b>: Robert Friedman
<br/><b>Collaborators</b>: Leah, Kathryn, Kari, Lindsey, Sam, CLAW
<br/><b>Etherpad</b>: https://etherpad.mozilla.org/hivebadges2
<br/><b>Deliverable: </b>This, completed: https://docs.google.com/a/mozillafoundation.org/spreadsheets/d/1RqzHo1GXZeRiFGMQvntAQvuR2i76GaZsO87XkfZN0pk/edit
<br/><b>Tags</b>: [allhands] [Hive] [hivebadges]
<br>
<br>
<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===
===Fill the Funnel, MoFos. Shipping the Maker Party Marketing Plan===
<b>Time</b>: 9:30 Wednesday
<b>Time</b>: 9:30 Wednesday
Line 148: Line 285:
===Learning from Users: usability testing our Engagement Ladder===
===Learning from Users: usability testing our Engagement Ladder===
<b>Time</b>: 9:30 Wednesday
<b>Time</b>: 9:30 Wednesday
<br/><b>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</b>. 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?&nbsp;<br
<br/><b>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</b>. 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? And most importantly, beyond usability, what are the different kinds of design research we can now do, and how do we work with MoCo to mature those methods?<br
/><b>Context</b>: https://wiki.mozilla.org/Webmaker/Engagement_Ladder + [http://openmatt.org/2014/04/04/product_testing/ blog post on Q2 Product Testing]<br
/><b>Context</b>: https://wiki.mozilla.org/Webmaker/Engagement_Ladder + [http://openmatt.org/2014/04/04/product_testing/ blog post on Q2 Product Testing]<br
/><b>Lead</b>: Cassie, Karen Smith<br
/><b>Lead</b>: Cassie, Karen Smith, Kat<br
/><b>Collaborators</b>: Cori Schauer + Tony Santos (User research) + Kat<br
/><b>Collaborators</b>: Cori Schauer (MoCo), Tony Santos (MoCo User research), Sabrina<br
/><b>Deliverable: </b>Run a usability test for account creation, event creation, and the new /explore page.<br>
/><b>Meeting: https://etherpad.mozilla.org/learningfromusers and Design Research Lab plans: https://etherpad.mozilla.org/webmakerdesignresearch</b><br
/><b>Deliverables: </b>
* 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 <br>
<b>Tags</b>: [allhands] [usability]
<b>Tags</b>: [allhands] [usability]
<onlyinclude>
<onlyinclude>
Line 184: Line 325:
{
{
"whiteboard": "[allhands] [appmaker]",
"whiteboard": "[allhands] [appmaker]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>
===Navigating Web Literacy with badges===
<b>Time: 9:30 Wednesday</b><br>
<br/><b>Goal:</b> create an MVP for Web Literacy badge pathways.<br />
<b>MoFo point:</b> Chloe, Doug<br /><b>Length: 2-3 hours</b><br>
<b>Collaborators</b>: Mike L, Lucas, Andrew, Jess, Atul, Laura, Kat, Michelle<br />
<b>Tags:</b> [allhands] [pathways]
<br
/><b>Deliverables:&nbsp; </b>
* 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",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"maxrows":"50",
Line 197: Line 362:
<b>Lead</b>: Dan/Erin Kissane<br
<b>Lead</b>: Dan/Erin Kissane<br
/><b>Collaborators</b>: Kaitlin, Dave, Studio MoFo<br
/><b>Collaborators</b>: Kaitlin, Dave, Studio MoFo<br
/><b>Local SF contact</b>: Holly Hastbritt (mozilla.org PM)<br
/><b>Local SF contact</b>: Holly Hastbritt (mozilla.org UX)<br
/><b>Goal</b>:&nbsp; Collaborate &amp; sprint on making a one-pager "New Communities" page&nbsp; on Mozilla.org. Plus getting "News" and "Science" added to the&nbsp; 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&nbsp; in these new spaces, plus drive referral traffic and contributors to&nbsp; those projects.&nbsp;<br
/><b>Goal</b>:&nbsp; Collaborate &amp; sprint on making a one-pager "New Communities" page&nbsp; on Mozilla.org. Plus getting "News" and "Science" added to the&nbsp; 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&nbsp; in these new spaces, plus drive referral traffic and contributors to&nbsp; those projects.&nbsp; <b>Update!!</b>: After internal discussion and a follow-up discussion with MoCo's Larissa and Holly, we refocused our efforts on a few specific interventions in Mozilla.org before the planned redesign takes place, plus ongoing collaboration/input into the redesign. The Etherpad is a much better representation of our work than are the Bugzilla entries, which reflect our initial understanding of the project.<br
/>'''Length''': 6hrs, max<br
/>'''Length''': 6hrs, max<br
/>
/>
Line 216: Line 381:


===[https://developer.mozilla.org/en-US MDN] + Webmaker: prepping for May workweek===
===[https://developer.mozilla.org/en-US MDN] + Webmaker: prepping for May workweek===
<b>Time:</b>Wednesday 1:30
<b>Time:</b>Wednesday 2:30
<br/><b>Goal:&nbsp; Determine, plot and start hacking on easy wins in preparation for the end of May MDN/Webmaker workweek</b>. 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.<br
<br/><b>Goal:&nbsp; Determine, plot and start hacking on easy wins in preparation for the end of May MDN/Webmaker workweek</b>. 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.<br
/><b>MoFo lead</b>: Laura/Brett<br
/><b>MoFo lead</b>: Laura/Brett<br
Line 315: Line 480:
{
{
"whiteboard": "[allhands][trust]",
"whiteboard": "[allhands][trust]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>
===How do I know what I want to do now?===
<b>Time</b>: lunch-ish time Wednesday
<br/><b>Goal:</b> A lot of our projects are in flux: growing, changing, people in new roles. As individuals, how do we figure out how we can best support our projects? If you've gone through this process before and have tips, or are going through it now and want to talk through questions/concerns/ideas with your colleagues, let's chat! The goal is for people to feel more able to sketch out their roles and discuss their ideas with their teammates/supervisor.
<br/><b>Lead</b>: Erika O.<br
/><b>Collaborators</b>: anyone!<br
/>
<b>Tags</b>: [allhands] [planning]
===Hive CHI Wordpress MVP: Building out an MVP wordpress blog for Hive Chicago===
<b>Time</b>: 1:30pm Wednesday
<br/><b>It's time for Hive Chicago to catch up with NYC and TOR by launching a dynamic online presence at hivechicago.org</b>. 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.
<br/><b>Context</b>: this crappy old site http://www.hivechicago.org
<br/><b>Lead</b>: Robert Friedman
<br/><b>Collaborators</b>: Elsa, Sam, CLAW, Lainie
<br/><b>Implementation Plan</b>: https://docs.google.com/spreadsheet/ccc?key=0Aq0GxL3v7LxvdDV0T0RnTWJDNEV0V0M4aVJFeUtvQXc&usp=sharing
<br/><b>Website Copy:</b>: https://drive.google.com/a/mozilla.com/folderview?id=0B-EZWDUirQ46RGRvZUgtN1hsQWM&usp=sharing
<br/><b>Deliverable: </b>A blog! http://hivechicago.cnkt.ca/wp-admin/
<br/><b>Tags</b>: [allhands] [Hive] [HiveCHI]
<br>
<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"whiteboard": "[allhands] [Hive] [HiveCHI]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"maxrows":"50",
Line 338: Line 535:
}</bugzilla><div style="align:left;"></onlyinclude>
}</bugzilla><div style="align:left;"></onlyinclude>


===Documentation and process: How we support our engagement work ===
<b>Time</b>: Wednesday<br
/>
<b>Lead</b>: Erika Owens<br
/><b>Collaborators</b>: <br
/><b>Local SF contact</b>: <br
/><b>Goal</b>We'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.<br
/>'''Length''':? <br
/>
'''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>
==Anytime / Unscheduled==
===Getting real about Marketing and Press===
===Getting real about Marketing and Press===
<br/><b>This is critical. We have to pour as many people into the top of our funnel as possible. </b>Press is a huge and proven way of doing&nbsp; this. For example, if we landed two Lifehacker articles per quarter, we'd be tripling our users. We&nbsp; 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.&nbsp;<br
<br/><b>This is critical. We have to pour as many people into the top of our funnel as possible. </b>Press is a huge and proven way of doing&nbsp; this. For example, if we landed two Lifehacker articles per quarter, we'd be tripling our users. We&nbsp; 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.&nbsp;<br
Line 387: Line 561:
/>'''Collaborators''': Robert, Elsa, Julia, Lainie, Karen<br
/>'''Collaborators''': Robert, Elsa, Julia, Lainie, Karen<br
/>
/>
/>'''When''': Anytime, 1/2 day<br
'''When''': Anytime, 1/2 day<br
/>
/>
'''Tag''': [allhands][hive]<br>
'''Tag''': [allhands][hive]<br>
<b>Deliverables</b>:<br/>
<b>Deliverables</b>:<br/>
https://wiki.mozilla.org/Webmaker/Hive<br/>
https://wiki.mozilla.org/Webmaker/HiveCookBook<br/>
<b>Etherpads</b>:<br/>
https://hive.etherpad.mozilla.org/newlandingpage<br/>
https://etherpad.mozilla.org/allhands2014-hivecookbookmvp<br/>
https://etherpad.mozilla.org/allhandsapril2014-hivefaq<br/>
<onlyinclude>
<onlyinclude>
<div style="align:left;">
<div style="align:left;">
Line 419: Line 599:
}
}
</bugzilla>
</bugzilla>
===Maker Party: Driving Mozilla-wide participation ===
<br/><b>From Open News to the Science Lab and beyond, let's make sure this year's Maker Party includes all areas of MoFo</b>. This can also include how to leverage upcoming MozCamps, plus&nbsp; 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.&nbsp;<br
/><b>Lead</b>: Amira/Michelle<br
/><b>Collaborators: </b>Winston, WPR folks for Mozilla-spaces events<br
/>
<b>[http://mzl.la/PEbrMr Tag]</b>: [allhands][mozmakerparty]<br>
<b>When:</b> Anytime. Talk to Winston & WPR separately<br>
<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>


=== Code contribution: guidelines and one-stop shopping ===
=== Code contribution: guidelines and one-stop shopping ===
Line 450: Line 610:
{
{
"whiteboard": "[allhands][codecontrib]",
"whiteboard": "[allhands][codecontrib]",
"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.<br>
<b>'''Lead''': </b>Laura<br>
<b>'''Collaborators''': </b>Lainie, Mozilla Reps, Cassie, Jbuck, Michelle, William<br>
<b>Tags</b>: [allhands][training]<br>
<b>When</b>: Anytime<br>
<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"whiteboard": "[allhands][training]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"maxrows":"50",
Line 520: Line 661:
</onlyinclude>
</onlyinclude>


===MoFo / MoCo Collaborations===
===Support Open / Community Quilt===
<br/><b>Goal: Collaborate with our awesome MoCo colleauges</b>.<br/>
<br/><b>Goal: Collaborate with our awesome MoCo colleauges to scope the next iteration of the [http://fuzzyfox.github.com/supportopen Support Open Quilt]</b>.<br/>
'''Lead''': <br/>
'''Lead''': FuzzyFox<br/>
'''Collaborators''': <br/>
'''Collaborators Requested''': Dino, Andrea, Lainie, Jennifer Bertsch, Chris More, Winnie Aoieong<br/>
'''When''': Anytime, list in bug clearly<br/>
'''When''': Anytime, list in bug clearly<br/>
'''Tag''': [allhands][mofoco]<br>
'''Tag''': [allhands][supportopen]<br>
<b>Deliverables</b>:<br/>
<b>Deliverables</b>:<br/>
<onlyinclude>
<onlyinclude>
Line 531: Line 672:
<bugzilla>
<bugzilla>
{
{
"whiteboard": "[allhands][mofoco]",
"whiteboard": "[allhands][supportopen]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>
 
===Brainstorm better name for programs under "new communities"===
<br/><b>Goal: Come up with a name that better captures what's going on</b>. Also check this out: https://etherpad.mozilla.org/sinker-newcommunities<br/>
'''Lead''': Erin? Dave S? Kay?<br/>
'''Collaborators''': All y'all<br/>
'''When''': Anytime<br/>
'''Tag''': [allhands][betternaming]<br>
<b>Deliverables</b>: A new name<br/>
<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"whiteboard": "[allhands][betternaming]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"maxrows":"50",
Line 540: Line 701:
</onlyinclude>
</onlyinclude>


== Thursday ==
===Maker Party: Real Life User Stories===
===Maker Party: Real Life User Stories===
<br/><b>Let's role-play to see how ready we are</b>. 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&nbsp; 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)&nbsp; 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. <br
<br/><b>Let's role-play to see how ready we are</b>. 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&nbsp; 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)&nbsp; 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. <br
Line 559: Line 719:
</onlyinclude>
</onlyinclude>


===Storytelling: Tips and Tricks===
<br/><b>We all tell stories. Let's do a teach-in on how to do that well</b>. We'll sit down and go over best practices for writing and public speaking, and how to make sure what you're saying is compelling.<br>
<b>Lead</b>: Erica Sackin<br>
<b>Collaborators</b>: Erin Kissanebr <br>
<b>When</b>: Thursday Lunch <br>
<onlyinclude>
<div style="align:left;">
<bugzilla>
{
"whiteboard": "[allhands] [storytelling]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</div>
</onlyinclude>


===DevOps: Making it easier to make===
<b>When</b>: All day, every day<br>
<b>Goal:&nbsp; Increase efficiency, safety, and ease of pushing code</b>.<br
/><b>MoFo point</b>: JP&nbsp;<br
/>
<b>Bugzilla tags</b>: [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>


https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/pjvdd1t5.png
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/pjvdd1t5.png
Tantek
canmove, Confirmed users
2,675

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/970930...1192183"