|
|
| (One intermediate revision by the same user not shown) |
| Line 6: |
Line 6: |
| |owner=Mozilla Foundation / Mark Surman | | |owner=Mozilla Foundation / Mark Surman |
| |updated=Jan 13, 2014 | | |updated=Jan 13, 2014 |
| |description=Working plans for Webmaker, Open Badges and other programs managed by Mozilla Foundation | | |description=Working plans for Mozilla Foundation programs including Webmaker |
| }}<section end=summary /> | | }}<section end=summary /> |
|
| |
|
| {{DoNotEdit}} | | {{DoNotEdit}} |
|
| |
|
| '''The Mozilla Foundation team runs three major initiatives: Webmaker, Open Badges and New Communities.''' This wiki houses 2014+ goals, roadmaps and status updates for these initiatives. You can find info on other Mozilla-run projects including Firefox on the [https://wiki.mozilla.org main Mozilla wiki page]. | | '''The Mozilla Foundation team runs a number of major initiatives: Webmaker, Open Badges Open News, Mozilla Science Lab and Mozilla Open Policy Fellows.''' This wiki houses 2014+ goals, roadmaps and status updates for these initiatives. For an overview of overall Mozilla goals for 2014 see [https://wiki.mozilla.org/2014 the main Mozilla 2014 Goals wiki page]. |
|
| |
|
| ==MoFo 2014 Goals== | | ==MoFo 2014 Goals== |
|
| |
|
| MoFo's Webmaker, Open Badges and New Communities initiatives support Mozilla's broader mission of building a web where people know more, do more and do better. These initiatives share two goals for 2014+: | | MoFo initiatives support Mozilla's broader mission of building a web where people know more, do more and do better. These initiatives share two goals for 2014+: |
|
| |
|
| * Goal #1: <b>10x the community actively contributing to our initiatives.</b> With the ultimate goal of getting 1 million new Mozillians by 2023. | | * Goal #1: <b>10x the community actively contributing to our initiatives.</b> With the ultimate goal of getting 1 million new Mozillians by 2023. |
| Line 24: |
Line 24: |
| *** 10k active contributors for MoFo initiatives. | | *** 10k active contributors for MoFo initiatives. |
|
| |
|
| * Goal #2: <b>grow adoption of Webmaker and Open Badges.</b> With the ultimate goal of getting more people to embrace the open technology and culture of the web. | | * Goal #2: <b>grow adoption of Webmaker, </b> the ultimate goal of getting more people to embrace the open technology and culture of the web. |
| **How? | | **How? |
| *** a. make our tools easier to adopt, use and plug into and | | *** a. make our tools easier to adopt, use and plug into and |
| *** b. prioritize lead users 'lead users'. | | *** b. prioritize lead users 'lead users'. |
| ** ''Metric:'' | | ** ''Metric:'' |
| *** A majority of active contributors adopting Webmaker and Open Badges as part of their daily work or integrating into their own web sites. | | *** The Webmaker community to include 10k active contributors teaching web literacy. |
|
| |
|
| As suggested above, '''2014 will include a major focus on lead users''': people already excited about our work. Get them to help us build our products, content and community. And, of course, get them to bring their friends.<br> | | As suggested above, '''2014 will include a major focus on lead users''': people already excited about our work. Get them to help us build our products, content and community. And, of course, get them to bring their friends.<br> |
| Line 36: |
Line 36: |
|
| |
|
| ==2014 Program Goals and Roadmaps== | | ==2014 Program Goals and Roadmaps== |
| | |
| | '''**need to update info below this line - May 26, 2014 (MS)**''' |
|
| |
|
| The wiki pages listed below include detailed goals, roadmaps and status updates for all MoFo run projects. They also include stories that describe each program's vision. | | The wiki pages listed below include detailed goals, roadmaps and status updates for all MoFo run projects. They also include stories that describe each program's vision. |
| Line 75: |
Line 77: |
| * [https://wiki.mozilla.org Main Mozilla Project wiki] | | * [https://wiki.mozilla.org Main Mozilla Project wiki] |
| * [http://www.mozilla.org/en-US/foundation/about/ MoFo board] | | * [http://www.mozilla.org/en-US/foundation/about/ MoFo board] |
|
| |
| == PLEASE MOVE THIS STUFF INTO YOUR PROGRAM PAGES ==
| |
|
| |
| === 2. Open Badges Goals & Strategy ===
| |
| <br>
| |
| Open Badges re-imagines credentials to support a transformed culture of learning where skills,
| |
| interests and achievements are recognized and connected with digital badges to share across the
| |
| web, granting access to jobs, advancement and education.
| |
| <br>
| |
|
| |
| <b>Goals</b>
| |
|
| |
| <b>2.1 Shape:</b> A distributed credentialing system connects greater numbers of people to open technology
| |
| and makes learning, employment and identity on the web more interoperable.<br>
| |
| <b>2.2 Teach:</b> The Open Badge ecosystem has an abundance of quality opportunities to foster and
| |
| recognize learning and teaching experiences that align with Mozilla's values.<br>
| |
| <b>2.3 Build:</b> BadgeKit forms the core technical infrastructure of a vibrant and interoperable open
| |
| ecosystem of learning.<br>
| |
| <b>2.4 Empower:</b> A thriving community of issuers, endorsers and validators recognizes and reinforces
| |
| a culture of learning based on shared digital badges.<br>
| |
|
| |
| === Open Badges Story ===
| |
|
| |
| <b>1. What is Open Badges and why does it matter?</b><br>
| |
| Open Badges is a project that re-imagines credentials to support a transformed culture of learning - one
| |
| where all types of learning, skills, interests and achievements are recognized and connected using digital
| |
| badges that can be shared across the web to unlock access to relevant job opportunities and advancement.
| |
|
| |
| <b>2. How will it shape the world by 2016?</b><br>
| |
| Open Badges is dedicated to recognizing and connecting learning across all contexts, in and out of school,
| |
| allowing learners to gain insight into the skills they need in order to accomplish their goals, capture and
| |
| communicate those skills once they've been obtained, and unlock access to relevant jobs and opportunities
| |
| for advancement.
| |
|
| |
| The Open Badges community has an audacious goal of a transformed culture of learning, employment and
| |
| identity across the web. Throughout 2014-2016, Open Badges will support thousands of issuers, endorsers
| |
| and validators in recognizing learning of all kinds through an open ecosystem of digital badges.
| |
| Subsequently, millions of learners will be able to build a collection of badges that truly represents their
| |
| lifelong learning and skills, and connects them to jobs, credit and other advancement opportunities. By the
| |
| end of 2016, we will see that new culture in action, with open badges issued by over 5,000 organizations,
| |
| impacting over 5 million learners and workers. Badges will be a key way that individuals represent
| |
| themselves online, and will be used in many hiring and admission decisions.
| |
|
| |
| <b>3. Why will people get involved in what we're doing?</b><br>
| |
| Mozilla Open Badges includes both an open standard for badges, as well as free software to make the
| |
| badging experience easy and personal. The shared standard enables openness and interoperability within
| |
| historically siloed credentialing systems. As a result, badges can operate as the key connector to ignite and
| |
| support a culture of learning that works like the web. Beyond the tools, Open Badges thrives on an active
| |
| and growing community who informs and drives this work forward with us.
| |
|
| |
| <b>4. Why will lead users or partners will get involved?</b><br>
| |
| The lead partners for Open Badges, including badge issuers, endorsers and validators, provide valuable
| |
| ways for learners to build upon and demonstrate what they know and can do. Issuers — often teaching
| |
| and learning organizations — benefit by plugging into a broader ecosystem of learning. Their learning
| |
| opportunities, recognition systems and brands will gain exposure beyond their networks, bringing more
| |
| learners, prestige and endorsement. Endorsers and validators have access to a connected ecosystem
| |
| where they support and promote specific skills, and exceptional learning opportunities for each skill.
| |
| Finally, badges are data, and privacy-friendly analytics around impact and outcomes are an attractive driver
| |
| for these contributors.
| |
|
| |
| Employers will benefit from making hiring decisions based on verified skills instead of, or in addition to,
| |
| self-reported resumes. Learners will have the ability to stitch together their learning across multiple
| |
| experiences, access opportunities needed to reach their goals and easily communicate their skills to
| |
| employers.
| |
|
| |
| <b>5. What we're doing in 2014 to move towards this:</b><br>
| |
| Mozilla's role is to shepherd, protect and promote the open standard for badges, to ensure that badges are
| |
| interoperable and have currency in the ecosystem, as well as to build the scaffolding needed for a healthy,
| |
| open badging ecosystem to exist and thrive. This includes open tools to support critical elements of the
| |
| badging experience, and the common interfaces and channels to ensure that a connected ecosystem of
| |
| tools, support and services can exist. In 2014, the Open Badges team will build and release BadgeKit, an
| |
| open tool stack to support the entire badging experience, including defining and issuing badges. We will
| |
| also launch the Badge the World campaign to invite and support a wide diversity of organizations and
| |
| global communities into badging. Finally, we hope to engage more deeply with key global organizations like the United Nations, as well as the U.S. Department of Education, Office of Vocational and Adult Education, the Scottish Qualifications Authority, DigitalME, Statewide Afterschool Networks, and numerous K-12 schools, universities and community colleges to develop important badge systems.
| |
|
| |
| <b>6. Possible revenue opportunities:</b><br>
| |
| In addition to a large and growing community of contributors, the Open Badges work requires a solid set
| |
| of paid contributors as a means to further support the initiative. Revenue opportunities may include
| |
| offering badge system design services to new issuers, offering services on top of BadgeKit like metadata
| |
| caching, featured badges and employer tools, and additional philanthropic grants.
| |
|
| |
| <b>7. Why will Open Badges succeed?</b><br>
| |
| We will succeed with Open Badges because they are the credentials needed to meet a rapidly changing
| |
| world. Credentials have historically been siloed and owned by institutions. The Open Badges project,
| |
| through sound technology and an open web ethos, is well positioned to shift the learning and credentialing
| |
| paradigm towards an open ecosystem. In addition, we have the highest level of institutional knowledge and
| |
| experience with badging in the marketplace, which we can leverage to help organizations build exemplar
| |
| badge systems and educate the growing community on why open (learning, credentials, etc.) is critical to
| |
| our future and to posterity.
| |
|
| |
| === 3.New Communities ===
| |
|
| |
| ==== Open News Goals ====
| |
| OpenNews is building a thriving community of people writing innovative code in journalism. We are helping those people lead and shape where journalism goes in the future.
| |
|
| |
| <br>
| |
| <b>3.1.1 Shape:</b> Guided by the OpenNews community, journalism on the web is transforming how we view the
| |
| web itself.<br>
| |
| <b>3.1.2 Teach:</b> Through Source, SRCCON and newsroom outreach, OpenNews is the leading destination
| |
| for those seeking to understand web development in the newsroom, and for those interested in
| |
| building web-native news.<br>
| |
| <b>3.1.3 Build:</b> Code developed through OpenNews initiatives achieves relevance and is adopted in newsrooms
| |
| and beyond.<br>
| |
| <b>3.1.4 Empower:</b> OpenNews is the central hub for a global community of news developers and
| |
| programmatic journalists. It attracts and trains new members while developing and supporting existing
| |
| leaders.<br>
| |
|
| |
| ==== Open News Story ====
| |
|
| |
| <b>1. What is Open News and why does it matter?</b><br>
| |
| OpenNews is building a thriving community of people writing innovative code in journalism. We are
| |
| helping those people lead and shape where journalism goes in the future.
| |
|
| |
| <b>2. How will it shape the world by 2016?</b><br>
| |
| We envision a world where there are many more curious, civically minded news coders than there are
| |
| today. In this world, open source and the values of the web are baked into how journalism works. It’s easy
| |
| to dive into data, visualize a point, organize a community; it happens every day. Journalism needs these
| |
| people, practices and technologies if it wants to continue to inform citizens and help communities thrive.
| |
| To get there, OpenNews will become the connective tissue in the journalism code community. We'll
| |
| connect people writing innovative code in journalism with their peers so they can learn, solve problems
| |
| and build new tools together. We'll offer onramps for the community to document, improve and spread
| |
| the code they write and the practices they develop to the news industry, the open-source software
| |
| community and the world.
| |
|
| |
| <b>3. Why will people get involved in what were doing?</b><br>
| |
| OpenNews works with a global community of news developers, civic hackers and open-source makers.
| |
| These are loosely tied communities. OpenNews is the first organization to recognize that reaching out to
| |
| these disconnected developer communities and organizing them along the lines that engineers and hackers
| |
| want to engage was a crucial first step in strengthening the overall journalism code community.
| |
|
| |
| <b>4. Why will lead users or partners get involved?</b><br>
| |
| We have designed the OpenNews ecosystem around two core audiences: News Developers and Civic
| |
| Hackers.
| |
|
| |
| Inside newsrooms, we see our core audience as News Developers. News Developers are the people
| |
| actually coding inside the newsroom. This community engages with our events (attending & hosting hack
| |
| days and MozFest), writes for Source (project documentation and learning case studies) and takes part in
| |
| our biweekly community calls. Over time, this community has become a collaborator with OpenNews,
| |
| advocating publicly for our programs and helping to conceive of the new projects we’re undertaking.
| |
| Outside newsrooms, we engage with a broad spectrum of coders that broadly fall into the “Civic Hacker”
| |
| bucket. These people dabble with open data and open-source software, and build hobbyist-level
| |
| visualizations and applications. They engage with us at events, read Source and take part in our biweekly
| |
| community calls. This community is where we find many of our Fellows.
| |
|
| |
| Why these audiences?
| |
|
| |
| These two communities are moving journalism forward on the web. One is doing it inside traditional
| |
| industry structures; the other is doing it independently. When these two communities collaborate (as
| |
| we’ve seen through successful open-source projects like Backbone.js, Django and D3), the impact reaches
| |
| far beyond journalism to the entire web itself. OpenNews regularly enables this collaboration.
| |
|
| |
| <b>5. What we're doing in 2014 to move towards this:</b><br>
| |
| We connect people writing innovative code in journalism with their peers so they can learn, solve
| |
| problems and build new tools together. We offer onramps for the community to document, improve and
| |
| spread the code they write and the practices they develop to the news industry, the open-source software
| |
| community and the world.
| |
|
| |
| We're doing this through the following initiatives:
| |
|
| |
| Knight-Mozilla Fellowships: Our 10 month fellowships connect members of the open-source
| |
| software and civic hacking worlds into newsrooms around the world.
| |
|
| |
| Hack Days: We offer financial and planning support for organizers of journalism-themed hack days
| |
| in their community.
| |
|
| |
| Source: We launched our journalism-code hub in October 2012 after extensive collaborative
| |
| design with the news developer community.
| |
|
| |
| Journalism Code Convenings: The introduction of Journalism Code Convenings, which bring
| |
| together top talent from the news developer world, our Fellows and leading external community
| |
| members to collaborate on code that will be widely shared throughout the journalism-code
| |
| community.
| |
|
| |
| Newsroom Outreach: We're adding in-person learning and discussion opportunities to place our
| |
| fellows, alumni and other leaders in the community into smaller, less tech-heavy newsrooms.
| |
|
| |
| SRCCON: The Source Conference (SRCCON), a hybrid un-conference and hack day to further
| |
| engage the communities we intersect with.
| |
|
| |
| Mozilla Festival: This annual Mozilla event, held in London has featured a “source code for
| |
| journalism” track that attracts both journalism developers and open-source hackers.
| |
|
| |
| <b>6. Possible revenue opportunities:</b>
| |
| We're already generously funded by the Knight Foundation to work on the core programs outlined above.
| |
|
| |
| Long-term revenue opportunities include:
| |
| * expanding our newsroom outreach program and getting separate funding for that
| |
| * getting additional funding for expansion of Source
| |
| * allowing newsrooms to pay full freight for a Fellow
| |
|
| |
| Short-term (or small amount) revenue opportunities include:
| |
| * creating and selling Source Guides to various news technology topics
| |
| * advertising on Source
| |
|
| |
| <b>7. Why we will succeed:</b><br>
| |
| From visualizations produced for the 2012 Elections in the storytelling of the New York Times’ Pulitzer
| |
| Prize winning “Snowfall,” it is clear that we’ve reached the inflection point for web-native journalism.
| |
| OpenNews is the only organization actively engaging and empowering the people doing this work. We’re
| |
| the only ones trying to grow the ranks of news developers while also seeding innovative code outside
| |
| traditional news organizations. While there are other trade organizations that address digital journalism,
| |
| none are actively organizing developers in the way that these communities natively operate. OpenNews
| |
| does. When done right, this community doesn’t simply impact journalism in the long run, but the entire
| |
| web itself. Fundamental architectures of the modern web — Django, Backbone, Underscore, D3 and
| |
| others — have been built in the newsroom first. Better organizing this community and harnessing its true
| |
| potential has impact far beyond journalism.
| |
|
| |
| ==== Mozilla Science Lab's Goals ====
| |
|
| |
| The Science Lab connects the open science community and empowers researchers, coders, funders and other partners to make research more like the web: open, collaborative and accessible.
| |
|
| |
| <b>3.2.1 Shape:</b> The Science Lab and its partners are influencing the culture of science by demonstrating new
| |
| and open ways to conduct research on the web.<br>
| |
| <b>3.2.2 Teach:</b> Researchers have the skills to conduct more science on the web, and are training others with
| |
| programs like Software Carpentry.<br>
| |
| <b>3.2.3 Build:</b> Through community building, educational programs and technical prototyping, the Science Lab
| |
| supports and strengthens the open research community.<br>
| |
| <b>3.2.4 Empower:</b> The Science Lab connects the research community, making science more open,
| |
| collaborative and reproducible.<br>
| |
|
| |
| ==== Mozilla Science Lab's Story ====
| |
|
| |
| <b>1. What is the Science Lab and why does it matter?</b><br>
| |
| The Science Lab connects the open science community and empowers researchers, coders, funders and
| |
| other partners to make research more like the web: open, collaborative and accessible.
| |
|
| |
| <b>2. How will it shape the world by 2016?</b><br>
| |
| The Science Lab intends to transform the culture of science by demonstrating the power of open-source,
| |
| interoperable technology. Over the next two years, the Science Lab will build prototypes, produce
| |
| resources and connect researchers and coders to foster the growth of the open science ecosystem. By
| |
| 2016, this community will include more than 250 networked instructors, equipped with relevant, quality
| |
| teaching resources.
| |
|
| |
| <b>3. Why will get involved in what we're doing?</b><br>
| |
| Scientific research relies on building upon other people's work, yet researchers are not armed with the
| |
| tools, resources or culture to work openly. By bringing the characteristics of the web — accessibility,
| |
| openness and interoperability — to science, the Science Lab will attract innovative researchers and
| |
| institutions working to advance science both technologically and culturally.
| |
|
| |
| Around the world, a lot of effort is being put into developing tools, practices, implementations and polices
| |
| around open research. What’s lacking is stewardship, the means for others to get involved (this includes
| |
| educational barriers) and the linking of disparate communities to work together towards their common
| |
| goal. The Science Lab is building communities of practice and technical prototypes to show what the web
| |
| enables. This allows us to support the activity that's currently taking place, and help do it at scale.
| |
|
| |
| <b>4.Why will lead users or partners get involved?</b><br>
| |
| Leaders in the emerging open science community see the Science Lab as a way to amplify their reach and
| |
| impact. Mozilla's history of working to support the open web, as well as its non-profit status, makes it an
| |
| attractive partner for the research community. The Science Lab represents the intersection of technical
| |
| and educational leadership, and offers a powerful demonstration of how Mozilla's values can shape and
| |
| scale a community.
| |
|
| |
| <b>What we're doing or building in 2014 to move towards this:</b><br>
| |
| The Science Lab is generating awareness around issues in open research by doing, not just showing. The
| |
| Code Review Pilot and the "Code as a Research Object" project are examples of how we build technical
| |
| bridges between existing tools and infrastructures in the open, while also generating a discussion with the
| |
| community and working to test implementations and develop a community standard.
| |
|
| |
| <b>Possible revenue opportunities / short and long term:</b><br>
| |
| We are currently supported by the Alfred P. Sloan Foundation on a 2-year grant for the program. We are
| |
| in discussion to submit for additional funding from the foundation in early 2014, which will secure core
| |
| funding for the program through 2016. We also are in the process of reaching out to other foundations in this space for core support, as well as programmatic funding.
| |
|
| |
| For our educational work, we are exploring models to help support Software Carpentry through event
| |
| sponsorship and arrangements with host universities. The aim is to pursue core sponsorship from each
| |
| event, which will offset the cost of creating and maintaining curriculum, train-the-trainer programs and
| |
| personnel costs.
| |
|
| |
| Longer term, we are looking to work with foundations and universities to support educational and
| |
| technical work that will help grow and empower the open research community, as well as build compelling
| |
| tools and prototypes.
| |
|
| |
| <b>Why will we succeed?</b><br>
| |
| The Science Lab is part of Mozilla's ongoing and evolving mission to shape communities around openness.
| |
| The Science Lab will serve as a connector for the open science community, helping researchers acquire
| |
| the skills needed to do more science on the web, build tools to make research more efficient, and foster
| |
| best practices.
| |
|
| |
| ==== Policy Program Goals ====
| |
|
| |
| In 2014, we will build a nascent framework and apparatus that exists to respond to policy threats to the open web. Policy Fellows will lead issue-based projects from within regulatory and political bodies to attract continued funding and resources.
| |
|
| |
| <b>3.3.1 Shape:</b> A well-resourced, distributed network of talented individuals protects the open nature of the
| |
| web against uninformed and potentially damaging regulations and commercial practices.<br>
| |
| <b>3.3.2 Teach:</b> The Policy Program uses policy issues to promote a web that is open and protected.<br>
| |
| <b>3.3.3 Build:</b> A nascent framework and apparatus exists to respond to policy threats to the open web. Policy
| |
| Fellows lead issue-based projects from within regulatory and political bodies to attract continued
| |
| funding and resources.<br>
| |
| <b>3.3.4 Empower:</b> A compelling public campaign around privacy with an effective call-to-action engages people
| |
| on policy issues.<br>
| |