Summit2013/Sessions: Difference between revisions
No edit summary |
No edit summary |
||
| Line 59: | Line 59: | ||
Track: Purpose and Strategy | Track: Purpose and Strategy | ||
Put practically and short term: how our values show up in the app ecosystem or social network (where the users are now). And, in the long term, how do our values show up in big data, internet of things and other upcoming ecosystems. | Put practically and short term: how our values show up in the app ecosystem or social network (where the users are now). And, in the long term, how do our values show up in big data, internet of things and other upcoming ecosystems. | ||
What would it look like to build a mobile apps and content ecosystem based literally on the ideas in the Nature of Mozilla? What features and marketing approaches would you include? How would we most effectively balance building, teaching and shaping markets? Where do local communities fit in as part of building this? Can they help build a long tail app ecosystem where we really see local diversity? | What would it look like to build a mobile apps and content ecosystem based literally on the ideas in the Nature of Mozilla? What features and marketing approaches would you include? How would we most effectively balance building, teaching and shaping markets? Where do local communities fit in as part of building this? Can they help build a long tail app ecosystem where we really see local diversity? | ||
| Line 77: | Line 76: | ||
Track: Purpose and Strategy | Track: Purpose and Strategy | ||
A large, interactive session to explore the web we're championing.What do we mean by "the web"? Is it a technology? A set of values? (also, how is it different from the Internet?) What are the baseline design principles we value most? Privacy? Creativity? User freedom? User Control? Data ownership? Something else? How is the web part of our identity? How do we use our products and our voice to help the broader world--including users--understand the web and become champions with us? | A large, interactive session to explore the web we're championing.What do we mean by "the web"? Is it a technology? A set of values? (also, how is it different from the Internet?) What are the baseline design principles we value most? Privacy? Creativity? User freedom? User Control? Data ownership? Something else? How is the web part of our identity? How do we use our products and our voice to help the broader world--including users--understand the web and become champions with us? | ||
| Line 96: | Line 94: | ||
Track: Purpose and Strategy | Track: Purpose and Strategy | ||
Why the large majority of people on the web should understand how the web works and how are we going to empower them to make it. How we can teach the everyday internet users more skills to improve their online experience and understand how the web works. | Why the large majority of people on the web should understand how the web works and how are we going to empower them to make it. How we can teach the everyday internet users more skills to improve their online experience and understand how the web works. | ||
| Line 113: | Line 110: | ||
Track: Purpose and Strategy | Track: Purpose and Strategy | ||
A hands-on session to define the identity of Mozillians, historically and as we evolve. Towards building scope and identity as a community. Consider new domains, like news and science. Do partners count? Who do we count? What are we trying to build? Who are we inviting? | A hands-on session to define the identity of Mozillians, historically and as we evolve. Towards building scope and identity as a community. Consider new domains, like news and science. Do partners count? Who do we count? What are we trying to build? Who are we inviting? | ||
| Line 129: | Line 125: | ||
Track: Product and Technology | Track: Product and Technology | ||
The strategy and vision for what Firefox OS is trying to accomplish, what markets it's heading for, as well as showcasing the technology and features. | The strategy and vision for what Firefox OS is trying to accomplish, what markets it's heading for, as well as showcasing the technology and features. | ||
| Line 148: | Line 142: | ||
Track: Product and Technology | Track: Product and Technology | ||
A discussion on how we combine our desire for excellent products, services and UX with leading privacy and security characteristics that advance trust, sustainability and safety for people. | A discussion on how we combine our desire for excellent products, services and UX with leading privacy and security characteristics that advance trust, sustainability and safety for people. | ||
| Line 166: | Line 159: | ||
Track: Purpose and Strategy | Track: Purpose and Strategy | ||
NEED DESCRIPTION | NEED DESCRIPTION | ||
| Line 183: | Line 175: | ||
Track: Purpose and Strategy | Track: Purpose and Strategy | ||
When there's a conflict between openness and bushinesses requirements, how should we, as individuals, navigate that? What resources do we have available for guidance and help? | When there's a conflict between openness and bushinesses requirements, how should we, as individuals, navigate that? What resources do we have available for guidance and help? | ||
| Line 199: | Line 190: | ||
Track: Purpose and Strategy | Track: Purpose and Strategy | ||
What does Mozilla need to be doing right now, to move the web forward, to do right by our users, and what are the most important factors to consider in planning the next three years? | What does Mozilla need to be doing right now, to move the web forward, to do right by our users, and what are the most important factors to consider in planning the next three years? | ||
| Line 215: | Line 205: | ||
Track: Purpose & Strategy | Track: Purpose & Strategy | ||
NEED DESCRIPTION | NEED DESCRIPTION | ||
| Line 231: | Line 220: | ||
Track: People and Process | Track: People and Process | ||
How does Mozilla hold a discussion on a particular topic that allows expression of positives and negatives in a productive way? This session will build the Mozilla Framework for how to invite feedback, manage the conversation and ensure all parties are acknowledged regardless of their view of the issue. | How does Mozilla hold a discussion on a particular topic that allows expression of positives and negatives in a productive way? This session will build the Mozilla Framework for how to invite feedback, manage the conversation and ensure all parties are acknowledged regardless of their view of the issue. | ||
| Line 247: | Line 235: | ||
Track: People & Process | Track: People & Process | ||
How do we create an experience that captures the history of Mozilla, our values, and what makes us unique in a way that we can transfer these items to new Mozillians and even our partners? | How do we create an experience that captures the history of Mozilla, our values, and what makes us unique in a way that we can transfer these items to new Mozillians and even our partners? | ||
| Line 263: | Line 250: | ||
Track: Purpose & Strategy | Track: Purpose & Strategy | ||
Working Narrative: A creative, "blue sky" session to imagine new kinds of contributors | Working Narrative: A creative, "blue sky" session to imagine new kinds of contributors | ||
| Line 279: | Line 265: | ||
Track: Product & Technology | Track: Product & Technology | ||
A workshop where you learn how to easily make sure that the products you make are as appreciated as you think they should be. | A workshop where you learn how to easily make sure that the products you make are as appreciated as you think they should be. | ||
| Line 295: | Line 280: | ||
Track: Product & Technology | Track: Product & Technology | ||
Introduction to our users - who they are, what they do, what they need, and how Mozilla can do this. | Introduction to our users - who they are, what they do, what they need, and how Mozilla can do this. | ||
| Line 312: | Line 296: | ||
Track: Product & Technology | Track: Product & Technology | ||
Web browsers were designed around yesterday's reality of computer hardware. Servo is a rethinking of the architecture of browsers to accommodate the hardware of today and tomorrow: multiple CPU's and powerful GPU's, and with limited power consumption. What's more, Servo is being built in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust], a new programming language designed to support faster and safer development practices. | Web browsers were designed around yesterday's reality of computer hardware. Servo is a rethinking of the architecture of browsers to accommodate the hardware of today and tomorrow: multiple CPU's and powerful GPU's, and with limited power consumption. What's more, Servo is being built in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust], a new programming language designed to support faster and safer development practices. | ||
| Line 327: | Line 310: | ||
Track: Product & Technology | Track: Product & Technology | ||
Alternate title: What's not going to change in 2018? What motivations our users will still hold in 10-15 years? | Alternate title: What's not going to change in 2018? What motivations our users will still hold in 10-15 years? | ||
| Line 346: | Line 327: | ||
Track: Product & Technology | Track: Product & Technology | ||
Powerful interests are creating silos of content and private walled gardens on the web. What can Mozilla do to open these silos up or create new more open alternatives? How do we need to understand how these competitors work for markets and consumers? | Powerful interests are creating silos of content and private walled gardens on the web. What can Mozilla do to open these silos up or create new more open alternatives? How do we need to understand how these competitors work for markets and consumers? | ||
| Line 365: | Line 344: | ||
Web developers are a key community for Mozilla. Our competitors are building sophisticated developer tools, API's, and platform technologies. How can we maintain a close and symbiotic relationship with web developers? How do we meet their needs, and how do we get them signed up for Mozilla's mission? | Web developers are a key community for Mozilla. Our competitors are building sophisticated developer tools, API's, and platform technologies. How can we maintain a close and symbiotic relationship with web developers? How do we meet their needs, and how do we get them signed up for Mozilla's mission? | ||
Facilitators: | Facilitators: | ||
| Line 382: | Line 359: | ||
The success of the internet depends on commercial activity as well as individual self-expression. To make that work means that we need to understand the perspectives of different stakeholders, from phone manufacturers, to phone companies, to media companies, to consumers. | The success of the internet depends on commercial activity as well as individual self-expression. To make that work means that we need to understand the perspectives of different stakeholders, from phone manufacturers, to phone companies, to media companies, to consumers. | ||
Facilitators: | Facilitators: | ||
| Line 398: | Line 373: | ||
Track: Product and Technology | Track: Product and Technology | ||
If we're to have the kind of massive impact on the internet that we hope to, we have to ask ourselves whether our structure and processes will get us there. If we want to facilitate innovation at the edges and focus on recognizing good ideas rather than having them, how should we relate to web innovators around the world? | If we're to have the kind of massive impact on the internet that we hope to, we have to ask ourselves whether our structure and processes will get us there. If we want to facilitate innovation at the edges and focus on recognizing good ideas rather than having them, how should we relate to web innovators around the world? | ||
| Line 413: | Line 387: | ||
Track: Product and Technology | Track: Product and Technology | ||
Webmaker is the brand that we're using to tell a new generation of web citizens that the web is theirs to grab, shape and remix. We'll show you what that looks like, and get you activated to help in that effort! | Webmaker is the brand that we're using to tell a new generation of web citizens that the web is theirs to grab, shape and remix. We'll show you what that looks like, and get you activated to help in that effort! | ||
| Line 433: | Line 405: | ||
Track: Purpose and Strategy | Track: Purpose and Strategy | ||
A well-facilitated inquiry and skillshare on distributed leadership. Skills Learned: Leadership, Conflict Resolution, Facilitating distributed meetings/planning/group actions. Potential Outline of Session: | A well-facilitated inquiry and skillshare on distributed leadership. Skills Learned: Leadership, Conflict Resolution, Facilitating distributed meetings/planning/group actions. Potential Outline of Session: | ||
# Nature of Mozilla -- one pillar is human capability; more mozillians moving the mission forward | # Nature of Mozilla -- one pillar is human capability; more mozillians moving the mission forward | ||
| Line 453: | Line 424: | ||
Track: Purpose and Strategy | Track: Purpose and Strategy | ||
Four breakout sessions with a joint shareback round. Determine what winning looks like as measured by Mozilla's four pillars of activity. Tools, roadmap and things you can do when you return home. How you can adapt the 3-year plan to your local context and the projects you care about. How you can multiply the mission. Skills Learned: Metrics, Building Open into your Project, How to Identify the NoM in your ideas & highlight/promote/grow those | Four breakout sessions with a joint shareback round. Determine what winning looks like as measured by Mozilla's four pillars of activity. Tools, roadmap and things you can do when you return home. How you can adapt the 3-year plan to your local context and the projects you care about. How you can multiply the mission. Skills Learned: Metrics, Building Open into your Project, How to Identify the NoM in your ideas & highlight/promote/grow those | ||
| Line 469: | Line 439: | ||
Track: People and Process | Track: People and Process | ||
A structure for Mozilla to engage our community and reach decisions. Collaboratively building a framework that enables Mozilla to reach decisions in a distributed decentralized organization. This session will determine an agreed upon best practice framework for inviting discussion, acknowledging user input, and reaching a decision amidst a variety of feedback. | A structure for Mozilla to engage our community and reach decisions. Collaboratively building a framework that enables Mozilla to reach decisions in a distributed decentralized organization. This session will determine an agreed upon best practice framework for inviting discussion, acknowledging user input, and reaching a decision amidst a variety of feedback. | ||
| Line 501: | Line 470: | ||
Track: People and Process | Track: People and Process | ||
The topic of tooling seems to be a frequent one. Let's discuss the needs of the various members of the community and determine if there are shared tools in which we as a community should invest. | The topic of tooling seems to be a frequent one. Let's discuss the needs of the various members of the community and determine if there are shared tools in which we as a community should invest. | ||
| Line 517: | Line 485: | ||
Track: People and Process | Track: People and Process | ||
How to stay open at Mozilla while meeting our needs: Creating a shared understanding of how Mozilla can work in a closed environment and a roadmap for introducing open concepts to our partners. | How to stay open at Mozilla while meeting our needs: Creating a shared understanding of how Mozilla can work in a closed environment and a roadmap for introducing open concepts to our partners. | ||
| Line 533: | Line 500: | ||
Track: People and Process | Track: People and Process | ||
Workshop to share tips and tricks for how recognize contributors to your project that would cover badges, swag, events and more. Also hack on the draft Recognition Guide at https://wiki.mozilla.org/Contribute/Recognition | Workshop to share tips and tricks for how recognize contributors to your project that would cover badges, swag, events and more. Also hack on the draft Recognition Guide at https://wiki.mozilla.org/Contribute/Recognition | ||
| Line 540: | Line 506: | ||
:Toronto: Jeff Beatty (Community Building for l10n) | :Toronto: Jeff Beatty (Community Building for l10n) | ||
:Santa Clara: Rosana Ardila (Community Builder for SUMO) | :Santa Clara: Rosana Ardila (Community Builder for SUMO) | ||
Session Wiki Page: | Session Wiki Page: | ||
| Line 565: | Line 515: | ||
Track: Product and Technology | Track: Product and Technology | ||
Mozilla has a proud history of championing user control of data, but there are both huge user benefits and competitive pressures to having some cloud-enabled data and services. How should Mozilla approach this problem in a way that pushes the mission forward while being pragmatic to the needs of the market? | Mozilla has a proud history of championing user control of data, but there are both huge user benefits and competitive pressures to having some cloud-enabled data and services. How should Mozilla approach this problem in a way that pushes the mission forward while being pragmatic to the needs of the market? | ||
| Line 581: | Line 530: | ||
Track: Product and Technology | Track: Product and Technology | ||
The web is poised to become a platform for games, which opens up opportunities for new markets and independent developers. With WebGL, asm.js, and key web API's like Pointer Lock, audio, and video, Mozilla is making the future of web gaming a reality, and creating an open alternative to proprietary technologies like Google's NaCl and Chrome. | The web is poised to become a platform for games, which opens up opportunities for new markets and independent developers. With WebGL, asm.js, and key web API's like Pointer Lock, audio, and video, Mozilla is making the future of web gaming a reality, and creating an open alternative to proprietary technologies like Google's NaCl and Chrome. | ||
| Line 597: | Line 545: | ||
Track: Product and Technology | Track: Product and Technology | ||
Working Narrative: With OpenBadges, Mozilla has a combination of technology and market-shaping partners which could shift how people learn, get recognized for their skills, and level up in the game of life. Learn about the OpenBadges project and what it's shooting for. | Working Narrative: With OpenBadges, Mozilla has a combination of technology and market-shaping partners which could shift how people learn, get recognized for their skills, and level up in the game of life. Learn about the OpenBadges project and what it's shooting for. | ||
Revision as of 21:54, 11 September 2013
What are Supporting Sessions?
Call for Facilitators
We need facilitators for the supporting sessions! Anyone can be a facilitator. Here is the list of sessions currently on the agenda for the Mozilla Summit 2013, with facilitators at each location. More information on expectations of facilitators can be found on the Session Facilitators wiki.
Each proposed session has its own etherpad for discussion and description, if you click through to it. Please add to that pad if you want to suggest specific questions to be addressed within the session.
Also note there will be open sessions on site which can be signed up for when we are at the summit, "Unconference" style. For more information about how to sign-up to host an open session, please see our FAQ.
How to Sign-up?
See a session that you would like to facilitate? If so, please place your name by the appropriate location next to the session (listed below) on this wiki page.
Please note that the deadline to sign-up has now passed. If you would like to help facilitate a session, please reach out directly to the named session facilitator.
Can I Co-facilitate?
In general, if you want to Co-facilitate a session, it is frequently possible, reach out to the track owner or to the facilitators themselves.
Who are the Track Owners?
[Track Owners] for the Summit Are:
- Mike Hoye (irc: mhoye), People and Process Track, office hours: 2-3 PM Eastern (6-7 PM UTC)
- [Lawrence Mandel] (irc: lmandel), Purpose and Strategy Track, office hours: Monday and Tuesday 11-12am Eastern Time.
- [Larisa Shapiro] (irc: lshapiro), Product and Technology Track (and the Innovation Fair) office hours: M-W-F 9-10am Pacific Time
You can also reach us at:
- IRC: #mozsummit
- Vidyo (during office hours): Summit Track Owners room
Can't meet during the designated office hours? No problem. Just ping us and we'll set up an alternate time just for you. :)
Don't know who to reach out to? Here is a list of sessions as they align with the Tracks.
Deadline to Sign-up
The deadline has now been extended - you can add yourself to a session until 12pm Pacific September 11, 2013. Please sign up!
After this time, those sessions that do not have a designated facilitator will become open sessions.
Any Questions?
If you have any additional questions, please feel free to reach out to a Track Owner or read through our FAQ.
Sessions that need Facilitators
- Please note that those sessions that already have facilitators are not included on this list. If you are interested in co-facilitating a session that already has a facilitator, please reach out to them directly.
Friday
Ecosystems in our Image
Friday, 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)
Track: Purpose and Strategy
Put practically and short term: how our values show up in the app ecosystem or social network (where the users are now). And, in the long term, how do our values show up in big data, internet of things and other upcoming ecosystems. What would it look like to build a mobile apps and content ecosystem based literally on the ideas in the Nature of Mozilla? What features and marketing approaches would you include? How would we most effectively balance building, teaching and shaping markets? Where do local communities fit in as part of building this? Can they help build a long tail app ecosystem where we really see local diversity?
Facilitators:
- Brussels: [need facilitator], [co-facilitator welcome]
- Toronto: Chris Lawrence, Dan Sinker
- Santa Clara: Alina Mierlus, Erika Owens
Session Wiki Page:
The Web We Want
Friday, 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)
Track: Purpose and Strategy
A large, interactive session to explore the web we're championing.What do we mean by "the web"? Is it a technology? A set of values? (also, how is it different from the Internet?) What are the baseline design principles we value most? Privacy? Creativity? User freedom? User Control? Data ownership? Something else? How is the web part of our identity? How do we use our products and our voice to help the broader world--including users--understand the web and become champions with us?
Facilitators:
- Santa Clara: Asa Dotzler, Tantek Çelik
- Brussels: Larissa Co, Ozten, User:AlisonW
- Toronto: Potch, Mike Collins
Session Wiki Page:
Afterwards:
- I've proposed an IndieWeb Hackspace on the Summit2013 Experiences wiki page for those that want to actively hack on their own websites and create the web we want by example. - Tantek (talk)
Building a Web Literate World
Friday, 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)
Track: Purpose and Strategy
Why the large majority of people on the web should understand how the web works and how are we going to empower them to make it. How we can teach the everyday internet users more skills to improve their online experience and understand how the web works.
Facilitators:
- Toronto: Marc Lesser, MOUSE, Julia Vallera, Lyre Calliope
- Santa Clara, Sandraghassen Subbaraya Pillai, Ankit Gadgil
- Brussels: Christos Bacharakis, Michael Köhler, Ibrahima SARR
Session Wiki Page:
What does "Mozillian" mean?
Friday, 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)
Track: Purpose and Strategy
A hands-on session to define the identity of Mozillians, historically and as we evolve. Towards building scope and identity as a community. Consider new domains, like news and science. Do partners count? Who do we count? What are we trying to build? Who are we inviting?
Facilitators:
- Brussels: Gervase Markham, Wilson Guaraca, Ioana Chiorean
- Toronto: Guillermo Movia, Andrew (feer56)- Will do second session @2:45
- Santa Clara: Sujith Reddy (would like co facilitator), [co-facilitator welcome]
Session Wiki Page:
How Firefox OS could change the next in 10 years
Friday, 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)
Track: Product and Technology
The strategy and vision for what Firefox OS is trying to accomplish, what markets it's heading for, as well as showcasing the technology and features.
Facilitators:
- Brussels: Chris Lee, Bill Maggs
- Toronto: Peter Dolanjski, [co-facilitator welcome]
- Santa Clara: Sandip Kamat, Christian Heilmann
Session Wiki Page:
Privacy, Security, and Data: Pragmatic Innovations for Users and the Web
Friday, 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)
Track: Product and Technology
A discussion on how we combine our desire for excellent products, services and UX with leading privacy and security characteristics that advance trust, sustainability and safety for people.
Facilitators:
- Brussels: Stacy Martin / Garrett Robinson or Brian Smith / [Coates' team rep]
- Toronto: Alex Fowler / Camilo Viecco or Monica Chew / [Coates' team rep]
- Santa Clara: Alina Hua / Sid Stamm / [Coates' team rep]
Session Wiki Page:
Saturday
Building through Brand
Saturday, 1:30-3:30
Track: Purpose and Strategy
NEED DESCRIPTION
Facilitators (Pete Scanlon to coordinate):
- Brussels: Ioana Chiorean, [co-facilitator welcome]
- Toronto: Winston Bowden, [co-facilitator welcome]
- Santa Clara: Sakina Groth, [co-facilitator welcome]
Session Wiki Page:
Practicing Open
Saturday, 1:30-3:30 pm
Track: Purpose and Strategy
When there's a conflict between openness and bushinesses requirements, how should we, as individuals, navigate that? What resources do we have available for guidance and help?
Facilitators:
- Toronto: Emma Irwin, Lawrence Kissuki, David Humphrey
- Brussels: Ioana Chiorean, Gervase Markham
- Santa Clara: Sakina Groth
Session Wiki Page:
Mozilla: Winning the Next Three Years
Saturday, 1:30-3:30pm (yes, this one is longer, co-facilitators encouraged)
Track: Purpose and Strategy
What does Mozilla need to be doing right now, to move the web forward, to do right by our users, and what are the most important factors to consider in planning the next three years?
Facilitators:
- Brussels: [need facilitator]
- Toronto: Mark Surman
- Santa Clara: [need facilitator]
Session Wiki Page:
Winning through Product: Applying the Lessons of Firefox Today
Saturday, 1:30 - 3:30pm
Track: Purpose & Strategy
NEED DESCRIPTION
Facilitators:
- Brussels: [need facilitator]
- Toronto: Armen Zambrano
- Santa Clara: [need facilitator]
Session Wiki Page:
Building a Framework to enable Mozilla to effectively communicate across our community
Saturday, 1:30-3:30pm (yes, this one is longer, co-facilitators encouraged)
Track: People and Process
How does Mozilla hold a discussion on a particular topic that allows expression of positives and negatives in a productive way? This session will build the Mozilla Framework for how to invite feedback, manage the conversation and ensure all parties are acknowledged regardless of their view of the issue.
Facilitators:
- Brussels: [need facilitator]
- Toronto: Lainie Delcoursy
- Santa Clara: Kathryn Meisner
Session Wiki Page:
Defining and Packaging a Mozilla Core experience for onboarding
Saturday, 1:30-3:30pm (yes, this one is longer)
Track: People & Process
How do we create an experience that captures the history of Mozilla, our values, and what makes us unique in a way that we can transfer these items to new Mozillians and even our partners?
Facilitators:
- Brussels: Rubén Martín [:Nukeador] (one of the Mozilla Hispano mentors that runs the onboarding process for new contributors)
- Toronto: Amie Tyrrel, Amira Dhalla
- Santa Clara: Ankit Gadgil
Session Wiki Page:
What would a million Mozillians do?
Saturday, 1:30-3:30pm (yes, this is a longer session)
Track: Purpose & Strategy
Working Narrative: A creative, "blue sky" session to imagine new kinds of contributors
Facilitators:
- Brussels: Brian King (Community Manager for Europe)
- Toronto: Liz Henry (Community Builder for Automation team), [co-facilitator welcome]
- Santa Clara: David Boswell (currently looking into pilot projects to create new functional and regional communities, such as Mozilla Utah and Mozilla knitters)
Session Wiki Page:
Developing empathy for your users
Saturday, 1:30-3:30 (yes, this one is longer)
Track: Product & Technology
A workshop where you learn how to easily make sure that the products you make are as appreciated as you think they should be.
Facilitators:
- Brussels: Larissa Co, Maureen Hanratty
- Toronto: Cori Schauer
- Santa Clara: Bill Selman
Session Wiki Page:
Designing for our users not ourselves
Saturday, 1:30-3:30 (yes, this one is longer)
Track: Product & Technology
Introduction to our users - who they are, what they do, what they need, and how Mozilla can do this.
Facilitators:
- Cori Schauer will be main facilitator for this, and will coordinate the other facilitators.
- Brussels: Gemma & Madhava Zhenshuo & Dominik?
- Toronto: Cori & Bryan Clark (possibly Gregg Lind)
- Santa Clara: Bill Selman & Lindsay Kenzig
Session Wiki Page:
Understanding the Servo strategy
Saturday, 1:30 - 3:30pm
Track: Product & Technology
Web browsers were designed around yesterday's reality of computer hardware. Servo is a rethinking of the architecture of browsers to accommodate the hardware of today and tomorrow: multiple CPU's and powerful GPU's, and with limited power consumption. What's more, Servo is being built in Rust, a new programming language designed to support faster and safer development practices.
Facilitators:
- Brussels: Josh Matthews
- Toronto: Jack Moffitt
- Santa Clara: Patrick Walton
Session Wiki Page:
Who are our users in 2018 and where are they?
Saturday, 4:00 - 6:00pm
Track: Product & Technology
Alternate title: What's not going to change in 2018? What motivations our users will still hold in 10-15 years?
The world is changing, and we need to build products that work for the next billion users. Who are they, and what are they like?
Facilitators:
- Brussels: Yuan Wang, Mary Trombley
- Toronto: Cori Schauer
- Santa Clara: Jinghua Zhang, Bill Selman, Lindsay Kenzig,
Session Wiki Page:
Understanding the product strategies of our competition in the eyes of consumers and working through how to compete intelligently
Saturday, 4:00 - 6:00pm
Track: Product & Technology
Powerful interests are creating silos of content and private walled gardens on the web. What can Mozilla do to open these silos up or create new more open alternatives? How do we need to understand how these competitors work for markets and consumers?
Facilitators:
- Brussels: Patrick Finch [co-facilitator welcome]
- Toronto: Kev Needham, John Jensen
- Santa Clara: Irina Sandu, Sandip Kamat
Session Wiki Page:
Understanding web developers
Saturday, 4:00 - 6:00pm
Track: Product & Technology
Web developers are a key community for Mozilla. Our competitors are building sophisticated developer tools, API's, and platform technologies. How can we maintain a close and symbiotic relationship with web developers? How do we meet their needs, and how do we get them signed up for Mozilla's mission?
Facilitators:
- Brussels: Jeff Griffiths
- Toronto: Stormy Peters
- Santa Clara: Christian Heilmann
Session Wiki Page:
Growing Stakeholders in the Web
Saturday, 4:00 - 6:00pm
Track: Product & Technology
The success of the internet depends on commercial activity as well as individual self-expression. To make that work means that we need to understand the perspectives of different stakeholders, from phone manufacturers, to phone companies, to media companies, to consumers.
Facilitators:
- Brussels: Kat Braybrooke, Patrick Finch can co-facilitate
- Toronto: Marc Lesser, Geoffrey MacDougall
- Santa Clara: [need facilitator] Irina Sandu can co-facilitate at minimum
Session Wiki Page:
The Petri Dish required by scaling innovation
Saturday, 4-6pm
Track: Product and Technology
If we're to have the kind of massive impact on the internet that we hope to, we have to ask ourselves whether our structure and processes will get us there. If we want to facilitate innovation at the edges and focus on recognizing good ideas rather than having them, how should we relate to web innovators around the world?
Facilitators:
- Brussels: David Ascher
- Toronto: Simon Wex
- Santa Clara: Robert Richter
Session Wiki Page:
WebMaker: Getting People to Take Back The Web
Saturday, 4-6 pm
Track: Product and Technology
Webmaker is the brand that we're using to tell a new generation of web citizens that the web is theirs to grab, shape and remix. We'll show you what that looks like, and get you activated to help in that effort!
Facilitators:
- Brussels: Kat Braybrooke, Henrik Mitsch
- Toronto: Amira Dhalla, Chris Lawrence, Matt Thompson
- Santa Clara: Brett Gaylor
Session Wiki Page:
Sunday
Distributed Leadership and decision making
Sunday, 1:15-2:30 pm
Track: Purpose and Strategy
A well-facilitated inquiry and skillshare on distributed leadership. Skills Learned: Leadership, Conflict Resolution, Facilitating distributed meetings/planning/group actions. Potential Outline of Session:
- Nature of Mozilla -- one pillar is human capability; more mozillians moving the mission forward
- history of the huge chunks of mozilla that people made up on on their own and we incorporated into the centralized piece
- Some issues with distributed decision-mkaing: risk, mistakes, surprise, messiness
- What do we do now: how we build more APIs to the centralized part of mozilla?
Facilitators:
- Brussels: Laura Thomson
- Toronto: Regnard Raquedan
- Santa Clara: Alina Mierlus
Session Wiki Page:
Ideas into Action: Next steps for me and my team
Sunday, 1:15-2:30
Track: Purpose and Strategy
Four breakout sessions with a joint shareback round. Determine what winning looks like as measured by Mozilla's four pillars of activity. Tools, roadmap and things you can do when you return home. How you can adapt the 3-year plan to your local context and the projects you care about. How you can multiply the mission. Skills Learned: Metrics, Building Open into your Project, How to Identify the NoM in your ideas & highlight/promote/grow those
Facilitators:
- Brussels: Karen Rudnitski
- Toronto: Larissa Shapiro
- Santa Clara: Ernest Chiang
Session Wiki Page:
Decisions, discussions and debate
Sunday, 1:15-2:30 pm
Track: People and Process
A structure for Mozilla to engage our community and reach decisions. Collaboratively building a framework that enables Mozilla to reach decisions in a distributed decentralized organization. This session will determine an agreed upon best practice framework for inviting discussion, acknowledging user input, and reaching a decision amidst a variety of feedback.
Facilitators:
- Brussels: Gervase Markham, [co-facilitator welcome]
- Toronto: Andrew (feer56) - This is a maybe as my flight leaves at 6:30 PM, Majken Connor
- Santa Clara: [need facilitator]
Session Wiki Page:
Designing your project for participation
Sunday, 1:15-2:30 pm
Track: People and Process
Nearly all projects will benefit from community involvement; however, there are different approaches and best practices that can better enable a project for wider contributions. This session will capture best practices and challenges to build a project with community involvement.
Facilitators:
- Brussels: Laura Hilliger or Michelle Thorne (working with Mozilla Reps to help them deliver the community building workshop content)
- Toronto: David Eaves (creator of the community building workshops that includes a 'Designing your project for participation' module) or Emma Irwin (One of the Mozilla Reps who will be delivering the community building workshop content)
- Santa Clara: Benjamin Kerensa (One of the Mozilla Reps who will be delivering the community building workshop content)
Session Wiki Page:
Community tools - what do we currently have
Sunday, 1:15-2:30 pm
Track: People and Process
The topic of tooling seems to be a frequent one. Let's discuss the needs of the various members of the community and determine if there are shared tools in which we as a community should invest.
Facilitators:
- Brussels: Josh Matthews, William Reynolds (members of the Community Building Systems Working Group)
- Toronto: Michael Hoye, Ricky Rosario (members of the Community Building Systems Working Group)
- Santa Clara: Pierros Papadeas (members of the Community Building Systems Working Group)
Session Wiki Page:
Working with corporate (closed) partners
Sunday, 1:15-2:30 pm
Track: People and Process
How to stay open at Mozilla while meeting our needs: Creating a shared understanding of how Mozilla can work in a closed environment and a roadmap for introducing open concepts to our partners.
Facilitators:
- Santa Clara: Chris Peterson
- Brussels: Dietrich Ayala, Mark Côté
- Toronto: Lawrence Mandel, Lukas Blakk, Bhavana Bajaj
Session Wiki Page:
Workshop on Contributor recognition guide
Sunday, 1:15-2:30 pm
Track: People and Process
Workshop to share tips and tricks for how recognize contributors to your project that would cover badges, swag, events and more. Also hack on the draft Recognition Guide at https://wiki.mozilla.org/Contribute/Recognition
Facilitator:
- Brussels: Janet Swisher (Community Builder for MDN)
- Toronto: Jeff Beatty (Community Building for l10n)
- Santa Clara: Rosana Ardila (Community Builder for SUMO)
Session Wiki Page:
Moderated discussion on how we will think about product opportunities in the cloud
Sunday, 1:15-2:30 pm
Track: Product and Technology
Mozilla has a proud history of championing user control of data, but there are both huge user benefits and competitive pressures to having some cloud-enabled data and services. How should Mozilla approach this problem in a way that pushes the mission forward while being pragmatic to the needs of the market?
Facilitators:
- Brussels: Lloyd Hilaiel
- Toronto: John Jensen
- Santa Clara: Toby Elliott
Session Wiki Page:
The future of web gaming
Sunday, 1:15-2:30 pm
Track: Product and Technology
The web is poised to become a platform for games, which opens up opportunities for new markets and independent developers. With WebGL, asm.js, and key web API's like Pointer Lock, audio, and video, Mozilla is making the future of web gaming a reality, and creating an open alternative to proprietary technologies like Google's NaCl and Chrome.
Facilitators:
- Brussels: Vlad Vukicevic
- Toronto: Martin Best
- Santa Clara: Marco Mucci
Session Wiki Page:
Badges and how they can help rethink education
Sunday, 1:15-2:30 pm
Track: Product and Technology
Working Narrative: With OpenBadges, Mozilla has a combination of technology and market-shaping partners which could shift how people learn, get recognized for their skills, and level up in the game of life. Learn about the OpenBadges project and what it's shooting for.
Facilitators:
- Brussels: Tim Riches, Emily Goligoski
- Toronto: Jess Klein, Meg Cole, Kerrie Lemoie
- Santa Clara: Sunny Lee, Carla Casilli
Session Wiki Page: