May 20, 2013 § 3 Comments
Open Badges started as a modest experiment: build open source badge issuing software for ourselves and others. As momentum around this experiment has grown, it feels like the opportunity is bigger: we could build openness and user empowerment into how learning — and professional identity — work all across the web. With Open Badges 1.0 out there in the world, now is the right time to ask: where next for Mozilla and badges?
When Mozilla and MacArthur Foundation first started work on Open Badges about 18 months ago, the plan was to build a badge interchange standard (like SMTP for skills) and a collection of open source software for issuing and sharing badges (Badge Backpack, Open Badger, etc.). We’ve built all these things. And we’ve put up a reference implementation that Mozilla and others are using. This was really the limit of our original plan: build some basic open tech for badges and put it out there in the world.
The thing is: there has been way more excitement and pick up of badges than we expected. Even though Open Badges only launched officially in March, there are already over 800 unique providers who have issued almost 100,000 badges. We are also starting to see the development of city-wide systems where learners can pick up hundreds of different badges from across dozens of learning orgs and combine them all into a single profile. Chicago is the first city to do this (June 1), but Philadelphia and San Francisco are not far behind. And, this is just the tip of the iceberg: orgs like the Clinton Global Initiative and the National Science Foundation are focusing on badges in a way that is likely to drive even more educators to pick up the Open Badges standard, making their badges interoperable with others.
Of course, the fact that educators and policy makers are interested in badges doesn’t represent a victory in itself. It just shows momentum and buzz. The real opportunity — and the real impact — comes when learners and employers get excited about badges. Mozilla never planned to build offerings for these audiences. Increasingly, it feels like we should.
In the Internet era, people learn things online and out of school all the time. Whether you want to make a web page, knit a sweater or get better at calculus, the internet makes it easy to learn on your own or with a group of friends outside of a school setting. However, there is no good way to get credentials or recognition for this kind of learning. And, even if there was, there is no trusted, verifiable way to plug that recognition into Facebook, About.me and other places that make up your online identity. People have no good way to show ‘what they know’ online.
Similarly, employers are increasingly turning to the internet to find talent. They use sites like LinkedIn that let you search online resumes. Or, increasingly, to sites like Gild and TalentBin that use data mining to find potential hires. The problem: these services do not offer granular or variable skills profiles. And, with some of them, there are significant issues around privacy: people are being offered up as potential hires without even knowing that these sites are collecting data about them.
Mozilla could offer a distributed, open source and privacy-friendly solution to problems like these. We could help learners show their skills in all their online profiles and also help employers search for talent reliably. However, to do so, we’d have to build a Firefox-quality offering for learners and employers on top of Open Badges. While this hasn’t been our focus up til now, I’m thinking more and more that this is something we should consider.
In some ways, there is a parallel to Gecko and Firefox. Gecko provides the underlying platform for shaping standards around our vision of the web. But we need a popular consumer offering like Firefox if we want this vision to actually become relevant in the market. Right now, with Open Badges, we’re mostly just playing at the underlying standards layer. If we really want to shape how learning and professional identity work on the web, we probably need to build our own offerings directly for the people who most want and need badges.
Now is the time to be looking at where the opportunity is in this space. Momentum and demand is amongst educators is growing. More and more start ups are appearing in the badges, portfolio and skills spaces. And likelihood that badges will be important for learners and employers is growing. We need to be asking ourselves: how can Mozilla — and its values — shape this space?
With this in mind, Erin Knight is leading an effort over the next few months to look at different badges product options. She’ll be providing updates on her blog. And I’ll be summarizing here as well. If you have ideas on where Mozilla should go on all of this, we’d love to have you involved as we think this through. Comments here on this post are a good place to start.
July 2, 2012 § 7 Comments
We want everyone to tap into the full creative power of the web. That’s the point of Mozilla Webmaker. Part of this is about people: building a global community of webmakers. But another essential element is building tools that both invite people to make cool things on the web and that help them learn how the web works. Last week, we released early versions of two of these tools: Thimble and Popcorn. This post offers background on these tools plus musings on next steps.
A month or two back, Free Software Foundation Chief Counsel Eben Moglen said: “We made the web easy to read, but we didn’t make the web easy to write. Facebook took advantage of this gap.” This is a useful way to look at the challenges the web now faces.
Over a billion people are now on social networks. They use these networks to create and share (awesome!). But they do so only on the terms social networks offer them. Most people have neither the tools nor the skills to tap into the unbounded creative potential of the web (e.g. I want to change how this app works, let me hack it). This seems like something worth fixing.
The goal of Mozilla Webmaker is exactly this: to move people from being users of the web to being makers of the web. While part of this move is about new skills and attitudes, another part has to be about tools and content. Specifically: tools and content that make it easier to create using the full power of the web. Easier to customize a blog template. Easier to add a data layer to a video. Easier to hack a game. And so on. As Mozilla begins to build tools like this, I see three big buckets of things we need to get done:
- Build a foundation: Thimble + Popcorn as way to test our making + learning thesis (2012)
- Build with the community: add in badges, get community adding content and code (2012+)
Of course, this isn’t just about Mozilla: we’re already working with Tumblr, Codecademy and many others who are also building tools that encourage making and learning. But Mozilla does have a clear role to play here, especially around tools that build in the design principle of ‘making as learning’ from the beginning. This is our focus.
Step 1 – Build a foundation
Quickly ship tools that test our webmaker thinking: this was our plan with Thimble and Popcorn. Earlier this year, we agreed we needed to try out our ‘people learn by making’ thesis soon and in the real world.
With this in mind, we designed very simple tools with a collection of ‘hackable’ projects at the centre. Each project is a web page or interactive video template that gives people a) a starting point for making something and b) instructions that help you learn while making.
In Thimble, for example, each project is a single, simple HTML page. All pages include code comments that suggest what part of the page you might hack and what techniques to use. Eg. <!– This is a comment. These comments tell you what to do. The next section is a <H1> header. Edit the text within the header tags to change what words are on the web page. –> Thimble currently includes about a dozen making + learning templates that teach basic HTML and CSS while letting you make a meme, kill zombies or remix an animal from the London Zoo.
In Popcorn, the focus is much more on learning the mechanics of the web while also learning how to tell stories in new ways. The core element of a Popcorn project is a video wrapped in an HTML page template. You are invited to tell your own story by manipulating the video and the template. For example, with the Robots template, you design your own Robot invasion movie by adding in Google maps (learn how APIs work + target the robots at your home town), by changing the words the robots say (learn about variables and speech synthesis), or by adding in pictures of people and places the robots will target (learn about links and embedding). Similar templates exist where you can make your own web newscast or create a VH1-style pop up layer on top of your video.
Popcorn and Thimble share a common design philosophy. They start from the premise that remix and making are central to how people have always learned the web. The web is an open, view source world where it’s easy to see a technique in action and then copy it. We’re trying to make that even easier and more explicit by offering tools and pre-made projects that help people learn by making. We think this approach is especially promising for the 1 billion+ people on social media who clearly like to express themselves on online but have no plans of becoming a capital P ‘programmer’. For these people, the starter content we’re offering will be much more important than the tools themselves.
Our goal for this 1st step in the Mozilla Webmaker tool roll out: test this making + learning thesis. See if people like what we’ve made so far. Evaluate whether they are learning anything and what they are learning (see ‘badges’, below). We’ll do this testing and evaluating over the next six months while also shipping improvements plus new content for Thimble and Popcorn.
Step 2 – Build with community
Our next big priority needs to be building Mozilla Webmaker with a community. There are two parts to this: a) building basic tools that offer value to people who want to make, learn or teach and b) creating an architecture of participation that makes it easy for people to contribute content and code. We’ve already started on a) (see above), now we need to get moving on b).
We’ve got a few early wins. Some of the best Thimble projects came from the hack jam we held with NESTA in London about a month ago. Popcorn already has a base of open source code contributors. And, of course, we’ve got well over 500 people who have stepped up to organize a #mozparty this summer. These are big contributions already.
What we don’t yet have is a systematic way for more people to get involved, especially on content, code and localization. As an example: we want to get to a place where large numbers of people contribute Thimble and Popcorn projects for other people to make / learn on top of. I believe that this sort of community-made content will be key to the growth of Mozilla Webmaker. Unfortunately, we don’t have a good way for people to do this yet.
As a first step towards fixing this, we’re going to create an easy way for people to propose Webmaker.org and Thimble content simply by posting it to a Mozilla wiki. We’re working on the specifics right now, but the ideas is that people can review / refine / discuss stuff there, and then we can port the best stuff to our main sites when it’s ready. Obviously, we need something easier and more robust over the longer term: a gallery or repository where anyone can post content ideas into the Mozilla Webmaker universe. We also need easier ways into the code side of our projects. These are both things we’re thinking through with the aim of making progress this year. We’re very open to your ideas.
We also need a way to see who’s who in the community: to know what people are working on; to find people with particular skills; to find people with similar interests. This starts with simple communications tools like the new webmaker mailing list and the #mozparty Twitter hashtag. But we need something more robust and something that works across alot of platforms if we want Mozilla Webmaker to scale.
This is where Mozilla Webmaker badges come in. By the end of 2012, we plan to offer badges to recognize the skills that people have learned and that recognize contributions to the community. The skill badges will include things like “I understand HTML basics” and “I’ve helped 5 friends learn CSS”. We’re still working out the specifics. The contribution badges will recognize those who have helped others and those who have contributed learning content and code. This will give people within the Webmaker community an easy way to signal each other — to know who knows what and who is into what. More importantly, it will also give people a way to show what they learned and for us to monitor what and whether people are learning.
We’re starting work on this 2nd step right now, building a more systematic architecture of participation in parallel with our efforts to test and improve our first set of tools.
Step 3 – Make the app world hackable
Our third big step for Mozilla Webmaker tools has to be ‘teaching real programming‘ — getting people to the point where they can create or remix a game, app, etc. We chose to start Mozilla Webmaker with a focus on HTML and video so we could test our making and learning thesis using basic content that almost anyone on the web can make. But, our ultimate goal is to let people control, configure and create all corners of their digital lives. Games. Apps. Social networks. Civic participation sites. Science projects. And so on. At some point, that means teaching programming, or making programming easier to do.
Our plan for 2012 is to explore both paths. We’re working with Codecademy to get their content on Webmaker.org and to encourage people to use their courses as part of #mozparty. This gives people a ‘learn real code in the abstract’ option. We’ll likely do the same with Meemoo, Blockly and other promising tools: write them up on Webmaker.org; encourage people to use them; and then ask people to feedback on what they observed. This is a good way to promote the work of allies who also want to teach the world to code while at the same time investigating whether there are gaps a tool like Thimble++ could play.
There are already a couple of places where I think Mozilla-made tools — and Mozilla’s learning philosophy — could add value in the ‘learn programming space’. One opportunity is in the realm of hackable games: HTML5 games which are designed from the ground up to be modified. People could be invited to change the game mechanics and or to bring in content from across the web. E.g. imagine grabbing your friend’s picture from Facebook and mapping it onto a rock in Angry Birds. Another opportunity is in mobile apps, especially those designed for rich on-the-fly HTML5 content creation. Eg. imagine a Popcorn-enabled Boot-to-Gecko phone that pulled in all kinds of contextual content and data on the fly, feeding a ready to edit package of content back to your laptop via the web. We’ll explore ideas like these this year at a blue sky and maybe even prototyping level to see what’s possible.
My guess is that this 3rd step in the Mozilla Webmaker tool effort won’t really move into high gear until early 2013. There are a number of experiments planned for later in 2012, but these are mainly about seeing what’s possible and giving us enough insight that we can develop a solid roadmap for our work in this space.
Admittedly, this is a pretty big dream. Mozilla Webmaker is ambitious on purpose. We need this kind of ambition if we want a world where we all understand and can shape our digital lives.
But we also need a plan to turn ambition into reality. We made the beginnings of a plan when we launched Mozilla Webmaker earlier this year (you can read it here). I’ll post a review of where we’re at with this plan sometime in later July, including how what we’ve learned from tools like Thimble and Popcorn is helping us evolve the plan.
In the meantime, there is one thing we know for sure: Mozilla is way too small to take on the Webmaker vision on its own. As I said above, we need to a) figure out how we can provide something valuable to others who want to teach the world to code and b) get at least some of these people working with us directly to create the tools, content and community for webmakers. Finding ways to work with people who share our vision (is this you?) is the number one priority of the Mozilla Webmaker team right now.
Which leads me to two closing asks: let us know if any of the work we’re doing on Mozilla Webmaker tools can help you + let us know if you want to help. It’s not always easy to find your way in. We know that and can help. The best place to start is on the Webmaker mailing list or our weekly community conference call. You can also just post a comment here or send me email. Just show up, put up your hand and say ‘I want help / how can I help?’ Someone on the Mozilla Webmaker team will be there to help you figure it out from there.
November 22, 2011 § 26 Comments
Building a generation of web makers has been a big topic of conversation recently. This was the theme of our recent Mozilla Festival. And it was the topic of a conversation I led on my blog. Moving people from using the web to making the web is becoming a major focus for Mozilla.
At the most recent Mozilla Foundation board meeting, we dug into the question: what concrete things can we do in 2012 to tackle our big picture goals around web makers? I’ve pulled together board slides plus a summary of our emerging plans in this slidecast:
These slides (PDF / WebM video) represent a first cut at a Mozilla Foundation plan for 2012. Over the coming weeks, we’ll be hashing out more details and asking for ideas from people who want to get involved.
If you don’t have time for the full 30 minute slidecast, here is a summary of essential points:
- What started out as Mozilla Drumbeat has evolved into a series of ‘learning labs’ for web makers: a mix of learning programs and software tools for people who create things on the web.
- In 2012, we plan to grow the community and reach of the most successful of these learning labs: Popcorn (video); MoJo (journalism); and Hive (teens).
- We also plan to strengthen our best software and learning offerings, such as PopcornMaker, Hackasaurus and School of Webcraft. We’ll integrate these into all of our learning labs.
- A new effort for 2012 will be developing Mozilla web literacy badges: a way to get recognized for developing skills and contributing to a community within a learning lab.
- For all of this to succeed, Mozilla will need to get better at making software for web makers need and also build up strength in the learning arena. We’ve got great people in both areas, but we’ll need more.
These plans are a direct result of a Mozilla Foundation program leads meeting this summer (‘the hedgehog summit’) as well as the feedback a series of blog postings I did earlier this fall (‘creating a web literate planet‘).
While this conversation has been going on for many months now, these are still early stage plans. They are very much designed to evolve as we dig into the details and start work over coming weeks and months.
If you have ideas and want to get involved, the best channel is our weekly web makers community call on Tuesday (formerly the Drumbeat call). Also, feel free to post comments here.
October 5, 2011 § 28 Comments
I want to us create a web literate planet. One where almost everyone — filmmakers, teachers, scientists, artists, bankers — understands what’s going under the hood on the web. Can take things apart. Remix them. Express what they want the web to be. Since starting Mozilla Drumbeat 18 months ago, I have seen that there is a thirst for this.
This thirst shows up partly in ideas: people calling out for web literacy, and in particular for a world where everyone knows at least a little code. Douglas Rushkoff is an example:
When we gained literacy, we learned not just how to read but to write. And as we now moved into an increasingly digital reality, we must learn not just how to use programs but how to make them.
I experience this thirst even more viscerally when I look at the web makers, including my 11 year old son. He posts video game commentaries online everyday. He craves creating things on the web. Yet, increasingly, he bumps up against the black box of YouTube, unable to take it apart, understand it or reconfigure how it works. He is not fully web literate.
As outlined in a number of posts recently, I believe Mozilla can play a leading role in creating a web literate planet. Concretely, I think Mozilla can — and should — build out a major P2P learning initiative that teaches web skills and web literacy to coders and non-coders alike. We should also take an active role building up the whole ecosystem of orgs emerging around web literacy and innovative, web-like learning.
With the aim of focusing (and firing up) a conversation on these ideas, I’ve written a summary of all my posts so far here. My major points have been:
Post #1: Our biggest achievement in the first 18 months of Drumbeat has been carving out a new way for Mozilla to work: teaching and building things with people I call ‘web makers’. The next thing we should do is build on this particular aspect of Drumbeat.
Post #2: The people I am calling web makers are teachers, filmmakers, journalists, artists, scientists, game makers and curious kids who a) want to be part of what Mozilla is doing and b) are making things using the open building blocks that are the web.
Post #3: We need to teach the world to code. Or, more specifically, we need to mentor web makers on a massive scale, giving them new skills to make their corners of the web more creative, participatory and open-ended. We need a big community of mentors to do this.
Post #4: We’ve noticed something: impressive learning happens when people get to make something new and innovative. If we want to drive learning, we also need to build a lab where people are invited to tinker, make and invent future pieces of the web.
Post #5: At the foundation of all this, we need a P2P pedagogy built around friendship and passion for a particular topic or interest (e.g. hip hop). Our mantra might be: people learn at Mozilla by building exciting things on the web with their friends.
Post #6: To make this concrete: we need a clear simple Mozilla learning program that anyone can dive into, no matter their age or skill level. This starts with the best bits of Drumbeat: Hackasaurus, School of Webcraft, MoJo, etc.. And is wrapped in a system of Mozilla badges that recognize the most skilled and generous community members.
What I am proposing is building a global P2P learning institution, tinkering lab and web skills certification system into the core of Mozilla’s work. Which raises the question, doesn’t this already exist? Partly yes, but mostly no.
Lots of people teach about computers. Few people teach about the web. For school age kids, the bulk of the focus remains on basic office apps and watching out for cyberbullies. And, for adults, the most popular out of school tech programs still continue to be things like the MCSE and Cisco Academy. Technical, but not very webbish, and certainly not at all helpful to the web makers.
Similarly, many people talk about educational innovation on the web. Few are trying build web-like learning experiences where making, tinkering and collaboration are at the core. You can see this in the myriad of e-learning and open educational resource sites that simply present videotaped classroom lectures. They aren’t even aiming a P2P pedagogy that works like the web.
Luckily, there are pioneers who are pushing forward on both web literacy and p2p pedagogy. Projects like Code Academy, Young Rewired State and CodeNow are teaching people great web coding skills. And people like Howard Rheingold, Cathy Davidson, Philipp Schmidt, Katie Salen, Dave Humphrey and everyone in MacArthur’s broader digital media and learning community are building learning experiences that work like the web. These are Mozilla’s allies, people we can both learn from and support as we build out a broader ecosystem around all of these ideas.
For now, we have a question: should Mozilla go big in learning? And how? The role we can play in teaching web skills and web literacy at a massive scale is clear, at least to me. And there is huge potential to contribute more broadly to learning innovation with things like Open Badges. But, as we deliberate on where to go next with Drumbeat, are these the right places to focus our energy?
PS. If you want to read more detail, I’ve posted all of my posts on this topic on a single page here.
September 30, 2011 § 12 Comments
I’ve talked about Mozilla going big in learning quite a bit recently. Specifically, I’ve talked about making Mozilla the biggest, most innovative technology learning organization on the planet. I’ve also talked about the importance of doing this in a Mozilla-like way, with P2P pedagogy and strong focus on making. The question now is: how?
The first step is fairly easy, or at least obvious: roll the best bits of Drumbeat into a single, coherent program designed to teach web culture and web skills at a global scale. This includes the clearly educational bits like Hackasaurus and School of Webcraft. But it also includes media and innovation programs like Web Made Movies and MoJo that are already helping new kinds of people learn, tinker and make things on the web. And, of course, it includes Open Badges as a basis for offering recognition and credit for what people have learned.
My personal opinion is that it’s time for us to focus in this way. What we’re hearing from you is that we need to relentlessly focus on the small number of things we can be best in the world at. This is what separates all great organizations from merely good ones.
The harder part is defining what a ‘Mozilla goes big in learning’ program would look not as a loose set of programs, but rather as a cohesive whole. Based on dozens of discussions and comments on my blog, I’ve put together a high level straw man outline. It looks like this:
Mozilla wants to spread web culture and skills at a massive scale
by being the biggest, most innovative tech learning org on the planet.
We’ll drive this through:
- top quality Mozilla web literacy and web skills content for all ages
- a community-run lab where learners and inventors make things together
- a global community of webmakers who learn and mentor with each other
- Mozilla Badges that recognize skills, achievement and contribution
- P2P learning and making, building on Mozilla’s collaborative way of working
These last two bits point to something critical: if we want to create a vibrant community of learners and mentors, we need to build a recognition system that rewards the best and most generous people in this community. When I think of the social scaffolding for this community — and for the learning programs I describe above — I imagine something like this:
The idea: give people a clear way to advance through Mozilla learning programs and labs, and then recognize their achievements and contributions through badges. This not only provides a way to incent learning and mentoring, it will also help us build the next generation of Mozilla community leaders.
The good news: we already have a head start. The best bits of Drumbeat give us a set of learning programs, software and community from which to build. Once we strengthen and systematize these things, we can snap them into a bigger learning offering like the one I am describing. We can then build up more content, a mentor network and Mozilla web skills badges system on top of these foundations that we’ve built through Drumbeat.
Of course, we haven’t yet decided if this is what we want to do. There is huge opportunity in learning: Mozilla could help millions of people gain the literacy and skills they need to shape how the web works in their own lives and careers. However, dedicating ourselves to learning at this scale would be a big bet. It would take significant time, resources and patience.
I want to start a broader conversation over the next few weeks to help deliberate and iterate on these ideas. It starts with the simple questions: Should Mozilla go big in learning? and What would that look like? I’ll do a summary post early next week as a way to focus this conversation. However, I’d be happy to hear people’s thoughts a comments on this post in the meantime.
September 27, 2011 § 7 Comments
Friendship is a powerful force for learning. Especially friendship built around a shared interest or passion. Space travel. Cooking. Technology. Gardening. Whatever. We tend to gather, explore, make, play — and learn — with friends who also share our passions. As people like Mimi Ito have shown with research: friendship and interests drive learning.
Mozilla’s learning programs should to be designed around this combination of friendship and passion. Our mantra might be: people learn at Mozilla by building exciting things on the web with their friends. Notionally, all of our learning programs need to be built around a P2P pedagogy with a big emphasis on making things and expressing your passion. Or, as our friends at MacArthur often say to me, we need to be doing ‘connected learning’.
Funnily enough, the importance of friendship came up in the debate about ‘Mozilla as teacher’ vs. ‘Mozilla as mentor’ in response to one of my recent posts. Ken Saunders said:
I suppose that mentor seems like (and may be) a friendlier, perhaps even more modest word. I’ve had many mentors who were also my friends, but few teachers that were.
Ken’s pointing to something critical here, even if indirectly: what makes the existing Mozilla community tick is a sense of common cause, collegiality, helping each other out, inventing and building things together. Friendship.
We need to keep this idea of friendship at the core of what Mozilla in learning. The good news is that a collegial P2P learning spirit is already built into what we’ve been doing with programs like School of Webcraft and Hackasaurus. What we need to do now is figure out how to be more systematic, how to do this with some scale.
Mentorship is likely one of the keys: encouraging senior community members to befriend and help others learn. The idea is to use friendship and shared interest to connect people with different experience levels. We’ve talked about building this kind of mentorship program like this with Hackasaurus and other youth-oriented programs. It’ll probably be one of the first new things we push on in 2012, alongside a badges program for web skills.
Interest and passion are the other side of this learning coin. Given our goal is to teach people web skills and web culture, we need to tap into their other interests: e.g., use their interest in gardening to teach them about the web. This may sound crazy or hard, this recent video about our work with the Bay Area Video Coalition reminded me we’re already doing it:
We’re also working with the New Youth City Learning Network (more on this soon) to connect kids who are interested in science, art, poetry, hip hop, etc. with web technology that lets them express themselves. This is interest-based learning.
Through Drumbeat we’ve already started to connected with interest-based communities: teachers; journalists; filmmakers; artists; etc. These people want Mozilla to help them learn how to apply the culture and skills of the web to their own domain. Many of them have also said they want to help Mozilla in return. These are the sort of new community leaders and mentors we’ll need if Mozilla wants to go big in learning.
One question still looms: what does Mozilla going big in learning look like? I’m going to take shot at that in my next post. In the mean time, I’m interested to hear from people whether what I’ve written hear addresses some of the concerns people raised around my ‘Mozilla as teacher’ post.
September 15, 2011 § 5 Comments
Today we announced Mozilla’s Open Badge Infrastructure project, an effort to make it easy to issue and share digital learning badges across the web.
Open Badges is a response to this trend: an open specification and APIs that provide any organization the basic building blocks they need to offer badges in a standard, interoperable manner.
If we’re successful, the benefits to learners will be tremendous. Open Badges will let you gather badges from any site on the internet, combining them into a story about what you know and what you’ve achieved. There is a real chance to create learning that works more like the web.
Also, this sort of badge collection may eventually become a central part of online reputation, helping you get a job, find collaborators and build prestige. This is another reason Mozilla wants to build an open badge format: it can show the real potential of open identity tools on the web.
Released today, the first Open Badges beta was developed by Brian Brennan and Erin Knight, with support from Dan Mills and Ben Adida in Mozilla Labs. It includes a badge format spec, APIs and reference implementation for ‘badge backpack’ software. It also builds on other Mozilla open identity technology like Browser ID. Our first implementation will be as part of School of Webcraft, an initiative Mozilla runs jointly with P2PU.
Today’s announcement coincides with the launch of a $2 million badges for learning competition funded by MacArthur Foundation and run by HASTAC. Earlier this week, MacArthur approved a $1 million grant to Mozilla to work on the Open Badges Infrastructure, a platform that will be used by all winners of the competition.
US Secretary of Education Arne Duncan, MacArthur Foundation VP Programs Julia Stasch and Mozilla Executive Director Mark Surman spoke at the competition launch in Washington DC earlier today. Here is the MacArthur Foundation press release.
Cross-posted from Mozilla blog.
July 12, 2011 § 3 Comments
As announced in another post, we’ve created the Mozilla Open Badges project to tap into the huge potential for badges as a way to incent and recognize learning online.
For Mozilla, there is an additional opportunity: badges may well become a significant part of our online reputation and identity. We could use our work on identity to speed up Open Badges, and use Open Badges to promote our thinking about identity.
Open Badges is built around this dual learning + identity goal set. Early plans are outlined in this presentation (pdf) that I gave to the Mozilla Foundation board last month (9 mins):
Erin Knight will be taking on the role of Open Badges Product Manager, which includes broad leadership on this project as well as continued work on the School of Webcraft badges pilot. Brian Brennan is technical lead for the project. Dan Mills and Mike Hanson are technical advisors.
Given the early stage, there are many details we’re still working out. However, things we already know we want to do include:
- Alpha badge backpack plus end-to-end demo planned for deployment on P2PU in Q3 2011.
- Seeking badge issuing partners through Q3 – Q4 2011. White House Office of Science and Tech / Dept. of Education may be interested.
- Release beta / firm metadata spec by January 2012.
- Work with MacArthur partner projects on more end-to-end deployments Q1 – Q3 2012.
- Related: badge issuers publish to our system / creating widgets to re-publish to 3rd parties. Also, infrastructure and UX more robust.
- Q3 2012(?): encourage wide adoption of ‘backpack’.
If you’ve got ideas or feedback, or if you have a badge project you want to hook into this, please contact Erin or I. Or visit the Open Badges Wiki.
July 12, 2011 § 5 Comments
Over the last 6 months, the potential of ‘badges’ to incent and recognize learning online has been a hot topic for many of us at Mozilla.
We’re in the early stages of creating the Mozilla Open Badges project to tap into the huge potential here. I’ve done a high level presentation (pdf) on the concept quite a few times recently. Here is a webcast version (19 mins):
As you’ll see from the slides, Open Badges is something we’re doing in close association with partners in the learning innovation space: MacArthur, P2PU, HASTAC, New Youth City Learning, Digital Youth Network and many others.
Open Badges Product Manager Erin Knight wrote this paper providing in depth thinking about badgess and learning. Matt Thompson summarized Erin’s work in a series of simple badge overview documents.
I’d love your comments and feedback on the overall concept. It’s still early days — we’re really keen to get input, ways to improve and especially suggestions of badge issuing partners to work with.