Confirmed users
4,243
edits
Summit2013/Sessions: Difference between revisions
no edit summary
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. | ||