August 12, 2010 § 10 Comments
Figuring out who to pay attention to and who to work with is a big challenge in a community like Mozilla. Using the Whistler Science Fair as example, Les Orchard points out the underlying issue — we don’t have a quick way to parse through all the awesome to find out who’s good at what / who’s contributed what / who is doing things relevant to me. This is a common problem in online life overall. We don’t have an easy, portable and reliable way to represent our skills, achievements and social capital.
Over the last two months, I’ve been talking to people about this same challenge in another context — learning and education. Historically, we’ve used degrees and certificates to show what we know. This breaks down online — partly because we have no good way to show these credentials and partly because so much of our learning is now informal that degrees aren’t really relevant. People like P2PU, Remix Learning and others have come same conclusion Les has — we could use online badges to represent these things. Sites like Stack Overflow already use badges like this. We’re going to do the same for the Mozilla / P2PU School of Webcraft.
Which brings me to the experiment I want to do: a digital ‘backpack’ that lets you store and display badges you pick up from many different sites across the web.
Badges can provide a good way for potential friends, collaborators, co-workers and employers to size you up. However, that’s only true if they can associate all your badges with you. You don’t want to send them traipsing around the web to look at sites like P2PU, iRemix and Badger to see your badges. Instead, you want to all the badges from these different places reliably associated with your online identity.
With this in mind, I’ve been talking to Mike Hanson and others about an experiment that displays badges from multiple places as a part of the identity you build up through Firefox. Someone wanting to check you out would see something like this:
At an implementation level, this would work by storing your badges (or references to your badges) in both a personal data vault like Weave and some sort of claims system. It could work something like this:
The main ‘layers’ of this system are the 1. the badge issuer, 2. you and your online identity and 3. badge display and badge viewers. Specific to my proposed experiment are:
- P2PU, Badger and iRemix -> these are places where you *get* a badge for some skill or activity. They act as ‘badge servers’ and would expose all the badges they have awarded to you in a structured and standardized way.
- A personal data vault (e.g. Weave) and a claims system (Mike Hanson is working on a general system like this) -> from a user perspective, these items combine into a ‘personal badge manager’ that you access via identity tools in your browser or on a web site.
- Your identity profile (webfinger?) plus social media sites like LinkedIn -> these display all of your badges and associate them with the rest of your identity.
At a practical level, we need a system like for P2PU School of Webcraft and the kind of badge platform Les is proposing for Mozilla. Connecting badges a version of your online identity the you control also presents a huge opportunity in informal digital learning — everyone working in that space needs something like this as well.
With this in mind, my proposal is to roll out an proof of concept for the idea described above using badges from Mozilla, P2PU and various orgs in the MacArthur Digital Media and Learning Network. I’m going to work with Mike, Les, Philipp, Robert and others on this in the next few months, with the hope of showing the prototype at the Drumbeat Learning, Freedom and the Web Festival in Barcelona this November. If you’ve got ideas or want to help out, please post comments below.
February 13, 2009 § 2 Comments
Just now, I was commenting on my friend Steve’s post on The Yin and Yang of Open. As sometimes happens, the comment grew into a bit of a tome. Or, at least something long enough that I figured I should make it a post instead. So here it is.
Great post, Steve. While I am always waving the flag of open, I am also a big yinyanger. Balance is important.
But, for the most part, I think were already surrounded by enough ‘closed’. Getting to balance is a long way away. So, closed mostly doesn’t need our help.
There are exceptions. Privacy is a big one. We’re losing it quickly. And it’s a pretty critical part of the balance. You need the privacy kind of closed in order to protect most of what we value in freedom and openness.
On the elements of open, I think you mostly have them. The three that I stick to these days are:
1. Transparency: Can you *see* inside something, and understand how it works.
2. Permeability. Can energy / labour / ideas / whatever get in *and* out of the open thing you are talking about.
3. Malleability: Can you shape / remix / make something new. This is similar to Zittrain’s generativity. Or, in layman’s terms, it’s hackability.
… and then iterated and tested by talking to alot of people in alot of ‘what’s open?’ conversations.
A fourth item that may be on the list: permission. As in, you don’t have to ask for it to do something. I am not sure it’s quite the right word. But my colleague Jay suggested it as we were talking about what an open mobile ecosystem would look like. It would be one where you don’t have to ask permission to add new apps, invent new services, and so on. Like the internet.
One small area I disagree: you say ‘openness is not in and of itself a virtue’. Something can be virtuous but, like all things, require moderation and balance. Personally, I see both ‘openness’ and ‘privacy’ as virtues, and don’t see much of a contradiction.
That’s all for this sunny Friday. ‘Hi’ to family and all in Durbanville.
And, to anyone else reading this, happy Friday to you too.
February 11, 2009 § 1 Comment
Over the past few months, Pascal Chevrel has been introducing Gregorio Robles to the world of Mozilla. Gregorio is part of Libresoft.es — a unit of the Universidad Rey Juan Carlos in Madrid that offers a masters degree in free and open source software development. After some discussions and small add ons workshop, Gregorio and Pascal have agreed to develop a Mozilla development course that will run this coming summer.
As a part of my interview series on Mozilla Education, I asked Gregorio to share his thoughts while he was at FOSDEM:
For the non-video-inclined, here is a quick summary of Gregorio’s comments:
- Mozilla is important for education. This is the first time in history where students can learn by working on real live code in an open project. But education is also important for Mozilla. Projects like Mozilla need people who know our technologies, and universities can help solve this problem.
- We already have a masters program on free and open source software, but it is mostly on general topics and technologies. We want to add courses on specific technologies so students can get involved with the community around that technology. Mozilla is a good place to start.
- Our specific plans for Mozilla are to have a face to face week in the summer followed by a longer online component. Students will take on projects where they get to really touch the code and know the Mozilla community.
- In terms of Mozilla’s broader educational effort, the priority should be to get materials done and then to re-use them. I am sure there will be lots of people wanting to use these materials. This will make life easier and make it easier to become a Mozilla contributor.