MozillaWiki

AllHands: Difference between revisions

Page Discussion

AllHands (view source)

Revision as of 15:11, 11 April 2018

2,240 bytes added ,  11 April 2018
this is not the allhands you're looking for
(this is not the allhands you're looking for)
 
(17 intermediate revisions by 9 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==
===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>


===Contributor Metrics: connecting the threads===
===Contributor Metrics: connecting the threads===
Line 97: Line 83:
</div>
</div>
</onlyinclude>
</onlyinclude>


===Getting real about press and marketing: Press Kits===
===Getting real about press and marketing: Press Kits===
Line 205: Line 190:
</div>
</div>
</onlyinclude>
</onlyinclude>


=== Mozfest: Roadmap and Brainstorm ===
=== Mozfest: Roadmap and Brainstorm ===
Line 226: Line 210:
</onlyinclude>
</onlyinclude>


===Ford Foundation The Web We Want Proposal===
===Ford Foundation: The Web We Want Proposal===
* Anytime
* Anytime
*'''Lead''': Lynn
*'''Lead''': Lynn
Line 254: Line 238:
</onlyinclude>
</onlyinclude>


==Wed==
<br>
<br>
===Hive Badges MVP: Determining the criteria of the Hive Community Member badge===
===Hive Badges MVP: Determining the criteria of the Hive Community Member badge===
Line 302: 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>https://etherpad.mozilla.org/learningfromusers</b><br
/><b>Meeting: https://etherpad.mozilla.org/learningfromusers and Design Research Lab plans: https://etherpad.mozilla.org/webmakerdesignresearch</b><br
/><b>Deliverables: </b>
/><b>Deliverables: </b>
* Run a usability test for account creation, event creation, and the new /explore page  
* Run a usability test for account creation, event creation, and the new /explore page  
Line 379: 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 504: Line 487:
</div>
</div>
</onlyinclude>
</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===
===Hive CHI Wordpress MVP: Building out an MVP wordpress blog for Hive Chicago===
Line 544: Line 535:
}</bugzilla><div style="align:left;"></onlyinclude>
}</bugzilla><div style="align:left;"></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 571: 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 665: 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 676: Line 672:
<bugzilla>
<bugzilla>
{
{
"whiteboard": "[allhands][mofoco]",
"whiteboard": "[allhands][supportopen]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"maxrows":"50",
Line 705: 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 724: 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/971266...1192183"