All Hands/2016 Hawaii/electivesubmissions: Difference between revisions

no edit summary
No edit summary
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
=='''Hawaii Electives Submissions For Voting'''==
=='''FINAL LIST IN SCHED. Hawaii Electives Submissions For Voting'''==
<p>Descriptions for the 72 proposed [https://wiki.mozilla.org/All_Hands/2016_Hawaii/electives electives for the Hawaii All Hands] are below. Please [https://www.surveygizmo.com/s3/3123546/Electives-in-Hawaii-December-2016 '''vote] for up to 10 you want to attend in Hawaii by Friday October 28.</p>'''  
* This is not the final list. Please see [https://hawaiiallhands2016.sched.org/ Sched] for [https://hawaiiallhands2016.sched.org/overview/type/Elective final list of Hawaii Electives].
* <p>Descriptions for the 72 proposed [https://wiki.mozilla.org/All_Hands/2016_Hawaii/electives electives for the Hawaii All Hands] are below. Please [https://www.surveygizmo.com/s3/3123546/Electives-in-Hawaii-December-2016 '''vote] for up to 10 you want to attend in Hawaii by Friday October 28.</p>'''  
* Vote in order of your preference: top choice first, etc.
* Vote in order of your preference: top choice first, etc.


Line 22: Line 23:
** Category: People track - Tech Speakers program works with our community of technical volunteers to increase their skill as public speakers, trainers, and facilitators.  We will talk about the speaker training process we use, and if time and interest allow, we will break into collaborative groups to practice short talks/constructive feedback. (see below, turnout will prob determine whether we are more presentation or collaborative in our focus).</BLOCKQUOTE>  
** Category: People track - Tech Speakers program works with our community of technical volunteers to increase their skill as public speakers, trainers, and facilitators.  We will talk about the speaker training process we use, and if time and interest allow, we will break into collaborative groups to practice short talks/constructive feedback. (see below, turnout will prob determine whether we are more presentation or collaborative in our focus).</BLOCKQUOTE>  


===People 3: Community Participation Guidelines Evolution===
===People 3: What We Commit To: Community Participation Guidelines Evolution===
* Presenter: [https://mozillians.org/en-US/u/lshapiro/ Larissa Shapiro]
* Presenter: [https://mozillians.org/en-US/u/lshapiro/ Larissa Shapiro]
* Description: As Mozillians, our [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines] guide us in how we treat each other. Over the years we've gotten feedback that the guidelines are hard to act on and enforce. As part of our diversity and inclusion strategy, we're revising them to act on feedback. Come and learn about the revisions and give feedback and suggestions and be part of building a more inclusive Mozilla.
* Description: As Mozillians, our [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines] guide us in how we treat each other. Over the years we've gotten feedback that the guidelines are hard to act on and enforce. As part of our diversity and inclusion strategy, we're revising them to act on feedback. Come and learn about the revisions and give feedback and suggestions and be part of building a more inclusive Mozilla.
Line 53: Line 54:
* Presenters: [https://mozillians.org/en-US/u/hmitsch/ Henrik Mitsch] and [https://mozillians.org/en-US/u/mvankleeck/ Michael Van Kleeck]
* Presenters: [https://mozillians.org/en-US/u/hmitsch/ Henrik Mitsch] and [https://mozillians.org/en-US/u/mvankleeck/ Michael Van Kleeck]
* Description:  
* Description:  
<BLOCKQUOTE>In 2017, we’re making collaboration better by promoting a set of common tools for use by paid staff and volunteers. Common tools can empower all Mozillians to focus on our mission with fewer barriers between paid staff and volunteers of all kinds.
<BLOCKQUOTE>In 2017, we’re making collaboration better by promoting a set of common tools for use by paid staff and volunteers. These common tools will enable innovation and radical participation among staff and volunteer Mozillians.


We want to hear how you collaborate today, and what challenges you face when combining staff and volunteer efforts. Let’s make volunteering for Mozilla an easier and more rewarding practice through the use of common tools.
We want to hear how you collaborate today, and what challenges you face when combining staff and volunteer efforts. Let’s make contributing to Mozilla an easy and rewarding practice through the use of shared tools.


By the end of the session participants will be able to
By the end of the session participants will be able to:
* understand the 2017 CoCo strategy (collaboration, sharing, discussions)
* understand the 2017 CoCo strategy (document collaboration, information sharing, discussion platform)
* review and expand the use cases for CoCo at Mozilla and beyond
* review and expand these CoCo use cases for Mozilla and beyond
* mob-prioritize implementation plans for 2017
* mob-prioritize implementation plans for 2017


Come join our session and make it easier for all Mozillians to collaborate. Through common tools, we’ll be able to tackle more mission-driven initiatives in 2017 and beyond.</BLOCKQUOTE>
Come join our session and make it easier for all Mozillians to collaborate, participate and innovate. Through a shared set of tools we will be more effective and feel better about contributing to our mission-driven initiatives in 2017 and beyond.</BLOCKQUOTE>


===People 10: Become a Mozilla Media Trained Rockstar===
===People 10: Become a Mozilla Media Trained Rockstar===
Line 118: Line 119:
* Presenter: [https://mozillians.org/en-US/u/mchris/ Chris Riley]
* Presenter: [https://mozillians.org/en-US/u/mchris/ Chris Riley]
* Description: At Mozilla, we tackle centralization and integrated vertical silos primarily through our engineering. But we could do more with non-technical teams, including but not limited to public policy, to advance this key Mozilla issue. The policy team will share our current thinking on ways we can contribute. And we hope others who join will share their current work and plans as well, so we can get and give each other feedback, and coordinate better across the org.
* Description: At Mozilla, we tackle centralization and integrated vertical silos primarily through our engineering. But we could do more with non-technical teams, including but not limited to public policy, to advance this key Mozilla issue. The policy team will share our current thinking on ways we can contribute. And we hope others who join will share their current work and plans as well, so we can get and give each other feedback, and coordinate better across the org.
===People 20: Drivers of Engagement for Mozilla's European staff===
* Presenter: [https://mozillians.org/en-US/u/djst/ David Tenser]
* Description: The pattern of scores for European staff in the employee engagement survey show a distinct pattern that's different the global results. We ran an investigation of the experience for employees in Europe in London, Paris, Berlin and for those who work remotely in the European timezone. We'll share the highlights in this session.


=Products=
=Products=
Line 157: Line 162:


===Products 8: Defining Firefox Product Strategy===
===Products 8: Defining Firefox Product Strategy===
* Presenter: [https://mozillians.org/en-US/u/pdolanjski/ Peter Dolanjski]
* Presenter: [https://mozillians.org/en-US/u/barbara/ Barbara Bermes] and [https://mozillians.org/en-US/u/pdolanjski/ Peter Dolanjski]
* Description: How do we decide on the direction to take Firefox in, anyways?  Hear about the Core Browser Product Management team's approach to defining Firefox product strategy.
* Description: How do we decide on the direction to take Firefox in, anyways?  Hear about the Core Browser Product Management team's approach to defining Firefox product strategy.


Confirmed users
1,262

edits