Confirmed users
9,624
edits
(Created page with "Mozilla Contributor Badges<br /><b>Goal: Share the cohesive vision for the united Mozilla badge system.</b> (Including Mozilla-wide, team/p...") |
No edit summary |
||
| Line 1: | Line 1: | ||
Mozilla Contributor Badges<br | ===Mozilla Contributor Badges=== | ||
<br | |||
/><b>Goal: Share the cohesive vision for the united Mozilla badge system.</b> (Including Mozilla-wide, team/product, and community-issued badges.) We'll explain visual design templates, system planning, and more around getting started. Proposed sessions include:<br | /><b>Goal: Share the cohesive vision for the united Mozilla badge system.</b> (Including Mozilla-wide, team/product, and community-issued badges.) We'll explain visual design templates, system planning, and more around getting started. Proposed sessions include:<br | ||
/><b>Lead</b>: Emily<br | /><b>Lead</b>: Emily<br | ||
| Line 17: | Line 18: | ||
/></li></ul | /></li></ul | ||
></li></ul | ></li></ul | ||
>What are our new communities programs and what are they up to?<br | > | ||
===What are our new communities programs and what are they up to?=== | |||
<br | |||
/>Updates & Discussions about what's happening in OpenNews, OpenScience, and the new Open Web Fellows program.<br | />Updates & Discussions about what's happening in OpenNews, OpenScience, and the new Open Web Fellows program.<br | ||
/><b>Lead</b>: Dan + Kaitlin, Dave<br | /><b>Lead</b>: Dan + Kaitlin, Dave<br | ||
| Line 28: | Line 31: | ||
/><br | /><br | ||
/><br | /><br | ||
/>How to MoFo: tips and tricks for cross-team sprints<br | /> | ||
===How to MoFo: tips and tricks for cross-team sprints=== | |||
<br | |||
/><b>Goal: create more standardized work sprint process across MoFo</b>. To work efficiently together, we need to be planning our sprints in a similar manner. Let's do RACI, meetings, planning etc with a common process so we're operating efficiently. Then we'll put some of this into practice for some of our existing sprints on the Webmaker wiki.<br | /><b>Goal: create more standardized work sprint process across MoFo</b>. To work efficiently together, we need to be planning our sprints in a similar manner. Let's do RACI, meetings, planning etc with a common process so we're operating efficiently. Then we'll put some of this into practice for some of our existing sprints on the Webmaker wiki.<br | ||
/><b>Lead</b>: Matt<br | /><b>Lead</b>: Matt<br | ||
| Line 35: | Line 40: | ||
/><br | /><br | ||
/><br | /><br | ||
/>Device and browser compatability: what's the story?<br | /> | ||
===Device and browser compatability: what's the story?=== | |||
<br | |||
/>Our front end web dev team needs a document that outlines our device support. Aki will lead a process to document fact-based decisions.<br | />Our front end web dev team needs a document that outlines our device support. Aki will lead a process to document fact-based decisions.<br | ||
/><b>Lead</b>: Aki<br | /><b>Lead</b>: Aki<br | ||
| Line 44: | Line 51: | ||
/><b>Lead</b>: Kate<br | /><b>Lead</b>: Kate<br | ||
/><br | /><br | ||
/>Whimsy for the win! How can we design more engaging & playful products ?<br | /> | ||
===Whimsy for the win! How can we design more engaging & playful products?=== | |||
<br | |||
/><b>Goal: Understand the basics behind playful design theory -- and how it can make our user experiences more engaging and irresistible</b>. Great design and fun experiences are a key part of why people want to engage and build with us. In this session we will make hands-on prototypes for adding more whimsy across our products, community platforms and events.<br | /><b>Goal: Understand the basics behind playful design theory -- and how it can make our user experiences more engaging and irresistible</b>. Great design and fun experiences are a key part of why people want to engage and build with us. In this session we will make hands-on prototypes for adding more whimsy across our products, community platforms and events.<br | ||
/><b>Lead</b>: Chloe, Cassie<br | /><b>Lead</b>: Chloe, Cassie<br | ||
/><b>Collaborators</b>: Leah G, Luc, Kat, Michelle T., Erika D, David A<br | /><b>Collaborators</b>: Leah G, Luc, Kat, Michelle T., Erika D, David A<br | ||
/><br | /><br | ||
/>Media Trainings  | /> | ||
===Media Trainings === | |||
<br | |||
/><b>Goal</b>: Uplevel skills of media spokespeople and bloggers/social media folks <br | /><b>Goal</b>: Uplevel skills of media spokespeople and bloggers/social media folks <br | ||
/><b>Lead</b>: Erica S, Sydney <br | /><b>Lead</b>: Erica S, Sydney <br | ||
| Line 55: | Line 66: | ||
/><b>Time Window:</b> 3 1-2 hour sessions <br | /><b>Time Window:</b> 3 1-2 hour sessions <br | ||
/><br | /><br | ||
/>Federal funding: dos and don'ts<br | /> | ||
===Federal funding: dos and don'ts=== | |||
<br | |||
/><b>Goal</b>:<b> Give people working on projects funded by federal funds the tools and info needed to properly manage those projects as per federal guidelines</b>. (It will be fun, we promise!) Let's also share what we learned during the NSF site visit.<br | /><b>Goal</b>:<b> Give people working on projects funded by federal funds the tools and info needed to properly manage those projects as per federal guidelines</b>. (It will be fun, we promise!) Let's also share what we learned during the NSF site visit.<br | ||
/><b>Lead</b>: Ruzanna<br | /><b>Lead</b>: Ruzanna<br | ||
| Line 62: | Line 75: | ||
/><br | /><br | ||
/><br | /><br | ||
/>Manager Support Brownbag<br | /> | ||
===Manager Support Brownbag=== | |||
<br | |||
/><b>Goal: provide (new) managers with insight and tools to effectively manage</b>. Highlight policies and processes that managers need to know. Provide space for open discussion about needs, questions, worries, feedback<br | /><b>Goal: provide (new) managers with insight and tools to effectively manage</b>. Highlight policies and processes that managers need to know. Provide space for open discussion about needs, questions, worries, feedback<br | ||
/><b>Lead</b>: Angela<br | /><b>Lead</b>: Angela<br | ||
| Line 69: | Line 84: | ||
/><br | /><br | ||
/><br | /><br | ||
/>HR office hours<br | /> | ||
===HR office hours=== | |||
<br | |||
/><b>Ask a question, get more info, or give feedback on HR issues and policies, experiences.</b><br | /><b>Ask a question, get more info, or give feedback on HR issues and policies, experiences.</b><br | ||
/>Angela P is on call for the whole week. Angela King from MoCo HR is also available on Thursday. Plus there's an HR/Ops feedback session on Monday.<br | />Angela P is on call for the whole week. Angela King from MoCo HR is also available on Thursday. Plus there's an HR/Ops feedback session on Monday.<br | ||
| Line 83: | Line 100: | ||
/><br | /><br | ||
/><br | /><br | ||
/>Navigating Web-Literacy With Badge Pathways<br | /> | ||
===Navigating Web-Literacy With Badge Pathways=== | |||
<br | |||
/><b>Goal</b>: Create web literacy pathways for our Discover prototype.<br | /><b>Goal</b>: Create web literacy pathways for our Discover prototype.<br | ||
/><b>Deliverables</b>: A web literacy pathway including a set of badges in the Discovery tool. <br | /><b>Deliverables</b>: A web literacy pathway including a set of badges in the Discovery tool. <br | ||
| Line 91: | Line 110: | ||
/><br | /><br | ||
/><br | /><br | ||
/>Demos and Product Pitches  | /> | ||
===Demos and Product Pitches === | |||
<br | |||
/><b>Goal: Product managers and designers showing off their new pitches</b>. Plus getting interested parties to help sharpen our product thinking.<br | /><b>Goal: Product managers and designers showing off their new pitches</b>. Plus getting interested parties to help sharpen our product thinking.<br | ||
/><b>Lead</b>: David Ascher<br | /><b>Lead</b>: David Ascher<br | ||