Moving to Wordpress (finally)

I've been meaning to move this blow to Wordpress for a while now. Labour Day weekends being good for such things, I have finally done it. For future postings, you should go to:

If you are following me using a feed reader, use this link:

The reasons for moving are many and mostly feature related. Pop up previews. Shortcodes. Nicer editing interface. And people like Helen keep berating me. So, it's done now.

PS. Most of my posts imported perfectly on Wordpress, but a few didn't. Most of these have been fixed. I will get to still broken ones soon. Feel free to email me if you find broken stuff.

Under the Hood: Open Source @ gov.za

As he wrapped up, Aslam Raffee reflected: "We've done very well in terms of setting policy, but very poorly at implementation. We've got to fix that." Aslam is one of three people leading to roll out of South Africa's government-wide commitment to open source. And he's willing to admit: making it work ain't easy.

Aslam

At Open Everything Cape Town, Aslam spent an hour talking with Matt Buckland and Steve Song about how the open source policy roll out is going. The policy basically states that all systems used to run the Government of South Africa must be based on open standards and should use open source software wherever possible. As you can hear the podcast below, he was at once honest about the challenges of making this idea real and optimistic about the future ...

Aslam2

On the upside, the Government of South Africa seems to be 'making the market' by insisting that all departments have open document format (ODF) capability by the end of the year. Microsoft -- which had previously given a 'no way' -- is now on a fast track to integrating to ODF into Word. It seems there are alot of Word users in South Africa who still want to be able to do business with government. Also, there has been good traction on things like open standards and avoiding lock-in with big tenders in areas like government document management. The result is that these systems are most likely to be open source.

On the downside, there is simply a huge amount of ignorance and entropy. Asked if he could give an example of where they're struggling to get people to 'be open', Aslam cited the Independent Election Comission's brand new web site. When you go to the site in Firefox (I just did), you get this message:

Welcome to the IEC web site! Our server detected that you are using a Browser or Operating System (e.g. Netscape, Mozilla Firefox, etc) which is currently incompatible with our site.This web site is designed for Microsoft Internet Explorer versions 4 and above on Microsoft Windows. The IEC is currently in the process of enhancing the web site so that it will also cater for other browsers. We apologize for the inconvenience caused. Please click on the image below to download the latest version of Internet Explorer.

Even more notably, the 'currently in the process of enhancing' language didn't even exist until a bunch of people blogged about this on Friday. It's tough to be proud of your government's commitment to open standards -- and equal access to all citizens -- with stuff like this.

The other big barrier to implementation is skills.The number of skilled open source developers and support people needed to roll out the government's plan just don't exist. Fixing this is partly a waiting game, as it depends on what the education system does ... and what's taught in classrooms is exempt from the open source policy as it isn't about 'government administration systems'. 

Thanks to Aslam, Matt, Steve and everyone at Open Everything for making this conversation real. I learned a great deal.

The podcast above just includes Aslam's main talk and the interview by Steve and Matt. You can hear a longer version including another 20 mins of audience questions here (bad audio in some parts).

Cape Town: Rebooting the Open Everything Intro

The vibe and ideas at Friday's Open Everything Cape Town were super sparky. A nice mix of well known open source projects (South African gov't open source policy) and novel new ideas (Free Culture House). A good balance of techie and non-techie, with a bias of creative media and open education types. And amazing food, service and atmosphere from Bird's Cafe. Fun and learning all around.

Toaster

One of the weaknesses of the Toronto event was the set up. People said they wanted a bit more of 'what's open really mean?' and 'why is it interesting?' to set the stage. Philipp and I took at this by introing the Cape Town event with this slide show ...

Open Everything Cape Town
View SlideShare presentation or Upload your own.

It's not a bad way to spend 20 mins if you want to get the basic idea of what these events focus on. However, it still doesn't have the zing it needs. Anriette suggested 'dig more into the values side of things'. I agree. Also, I just think it needs to be shorter. And, I need to talk slower. Comments very much welcomed.

Of course, the real juice of the event wasn't Philipp and I -- it was all the speedgeekers and the open source in government talk by Aslam Rafee. I'll be posting on this stuff over the coming days.

PS. Tino Kreutzer has posted some great photos to Flickr, including the one of the Freedom Toaster speedgeek that I included above.

How We Work Remix: Notes From a Small Foundation

If you've been following this blog, you'll know that one of my Shuttleworth open philanthropy experiments was the 'How We Work' club. This is basically a quarterly pizza lunch where the whole organization reflects on an important aspect of how we function as a foundation (e.g. making sure everything is under an open license). The conversations focus on what's working, what's not and how things could be better. I then write up a blog posting and an article so that the rest of the world can learn from the discussion.

Img_6773

This week's pie noshing chat focused on a highly recursive topic: how is the How We Work club working? Somewhat surprisingly to me, the answer was a unanimous 'it's working well' ... or, at least, 'it's quite useful'. 

The first thing that people seem to appreciate is checking our rhetoric against reality. Our discussions on open licensing are a case in point. We'd been saying 'we're doing a better job on open licensing' for while. Sitting down to talk about it underlined the fact that we actually hadn't finished or published our new Open Resources Policy. And, putting a deadline on writing up an article forced us to actually get the policy done (or, at least, for me to harangue Karen and Andrew constantly :)). The result was that we actually delivered what we said we'd been doing: offering a clear open licensing policy that the world could see and our partners could review.

Talking through the open licensing policy also surfaced the fact that we didn't have consensus on which licenses to promote (share-alike) and who should own intellectual property (external partners or the foundation). An hour of forceful conversation went a long way to showing where the differences were, and helping us construct some common ground. As a result, we ended up with clearer language on license flexibility (share alike is the default, but arguments can be made for slightly more or less open licenses). Also, we created room for different options around IP stewardship (the draft policy had the foundation owning everything). These were important changes that both improved the policy and made sure we had a document that was more widely supported by the team.

The other thing that people appreciate is the opportunity to think through 'how we work now' against the backdrop of mistakes we've made in the past. Strategy at the Shuttleworth Foundation definitely has a heavy dose of emergence. Which is a nice way to say: we're willing to make mistakes and then hack things to make them better response. The licensing policy emerged at least in part from problems with our laissez faire 'just use an open license' approach. Similarly, the fellowship program grew from frustration with having to invent a 'project' to fund for every smart person we wanted to work with. Looking back at the things that shaped current practices has helped us all get on the page about 'why we are who we are'. Hopefully, it will also result in useful lessons for other small foundations.

Img_6783

Of course, there are some things that are broken about the How We Work process. For example, all of the writing sits with one person (me). Different people have different expertise and passions. It's likely we'd get better material if the person who cares most about a topic were to write it up. Also, there is a fair bit of brokenness in our follow up and promotion process. We did nothing to get the Open Resources Policy article out there other than putting it up on our site. We need to flog stuff like this more widely.

Despite the fact that I'm heading off into the open philanthropy sunset, the How We Work club will continue, albeit under a new name: Notes From a Small Foundation. There is a general feeling that this is more about 'what we're learning' than simply 'how we work'. The new name reflects that. Karien will be leading the charge on this new version, with different people facilitating and writing up a session every couple of months. Upcoming topics include 'IRC, wikis and internal communications' (Steve S) and 'project exit strategies' (Helen). It'll be fun (and a bit sad) to watch this next chapter unfold from afar.

Moving to Mozilla

It's official: I will be joining the Mozilla Foundation in late September to take on the role of executive director.

I am totally psyched about this. Mozilla is a new kind of foundation, one with with participation, transparency and innovation at its very roots. It's not just about giving out grants or making bold statements (although these are useful things to do), but also about getting large numbers of people involved in making things. In particular, things that make the Internet more open. For someone obsessed with reinventing how foundations work, there could be no more exciting job than this.

Of course, I am also a wee bit sad. Moving to Mozilla means leaving my Shuttleworth Foundation and telecentre.org work behind. The people at these two organizations have inspired and challenged me in the most wonderful ways possible. More importantly, they've proven to me that little changes to the way we work – like blogging about stuff that normally gets stuck in internal reports – can really help to open up the work of grant making and world changing. My hope is to stay connected to all of these people as an informal advisor and supporter.

Between now and September 22 (my official start date), I will have my head down finishing up my work on the Shuttleworth open philanthropy file. I'll also be running Open Everything events in South Africa, Canada and Singapore. My mind is already spinning with thoughts of Mozilla -- I've been talking to people in the Mozilla community about the foundation for many months now. Even so, I really need to take this time to make sure these things all wrap up properly. Once they're done, I'll dive head first into Mozilla work, including the continuing conversation about the future of the foundation. I can't wait.

Open Everything Cape Town this Friday!

I met with The Amazing Philipp Schmidt over the weekend to prep for Open Everything Cape Town. The event is happening this Friday at Bird's Boutique Cafe. It's an amazing venue. High ceilings and tons of light. And scrumptious homemade everything. 

Img_6763

We spent about an hour going over the agenda. Philipp and Helen (also co-organizing) have done amazing job getting people to present at the event. The speedgeek list looks like this:

Couchsurfing by Mandy Messina
27 Dinners by Dave Duarte
UWC's Rip. Mix. Learn. by someone from UWC
Mail and Guardian Thought Leader by Matthew Buckland
Siyavula / FHSST by Sarah Blyth
QuirkE Marketing by Rob Stokes
Dabba / Village Telco by Steve Song
Ultimate Holiday Planner by Terence Lapidus
Missing Link by Rich Mulholland
Creative R&D by Steve Kromberg

Also, we're likely to have an insider view on how the South African Government's open source adoption project happened ... and how it's rolling out. I promise to podcast if it happens.

If you're in Cape Town and interested, make sure to sign up on the wiki ASAP. It feels like there is alot of buzz around this event. And space is limited.

Mozillian brainpower and passion. Yay!

As the old saying goes: 'There's nothing like getting stuck behind a rockslide with 400 of your closest friends.' Okay, maybe it's not an old saying yet ... but it will be as people mythologize and remember the 2008 Firefox Plus Summit -- float planes, candles and all.

Img_6737  

And mythologize they should. The brainpower and passion gathered at the Mozilla event was truly awesome. What's more, it wasn't just technology brainpower and passion (although it was certainly that in spades). Everyone I met to was just as stoked to talk about broader values like openness, the internet and community as they were about mobile browsers and data in the cloud. This is what drives it all. While this isn't really surprising, feeling this kind of passion emanate off 400 living, breathing human beings is waaaaaaaaaay more real than just thinking about it in the abstract. Amazing, really.

Img_6713

More concretely: there were many of great conversations at the Summit about both Mozilla's evolving identity and Mozilla Foundation 2.0. I will post in detail on these topics when I return from off-the-grid holidays in a couple of weeks. In the meantime, thanks to everyone I met for such a warm welcome to the Mozilla community. I am really hoping I have something useful to contribute.

Prototyping the open ed revolution

Frank Hecker has a series of posts up today on 'Mozilla and the Future of Education'. It's a bit of a thought experiment to imagine what Mozilla might do if it dipped it's toe further into the education pond. The line I like most is:

Mozilla Foundation could also work with others to change the entire manner in which the next generation of software developers is educated.

That's a great vision! Why? Because it could flow from Mozilla doing something related to its core needs (running more Mozilla developer courses) while at the same time contributing to the growth of a whole new way of working (collaborative global apprenticeship as a way to do computer studies).

This 'solve a concrete problem -> create something more broadly and mind blowingly useful as a side effect' itself seems part of the Mozilla DNA. The module ownership system is something that was created to meet a particular need. It's now something that has directly and indirectly influenced how all sorts of people work well beyond the boundaries of Mozilla.

The trick is: make sure to think about both 'what' and 'how' Mozilla engages with education. The 'what' could be quite simple and close to home. Computer studies courses on Mozilla development, and maybe even some courses on design for open source at art colleges or the history and economics of the open internet for communications students. However, making sure that the 'how' is built around open, collaborative materials and pedagogy means the Mozilla is already protoyping the open education revolution as it goes about its everyday business. That would be fun.

PS. I hope this is coherent. I have a cold! :(

A few concrete things Mozilla Foundation might do

Looking back over dozens of online and over-beer conversations, it's clear the Mozilla Foundation can play an important role in the world. This role is not to oversee or second guess the people producing Firefox, Thunderbird, SeaMonkey, XUL and other technologies that fulfill Mozilla's mission of keeping the internet open. Meddling with this work doesn't help anyone. However, the foundation can and should build on this excellent work. It can fill gaps (accessibility). It can connect dots (amongst Mozilla communities). And it can reach out to new groups of people with something to contribute (the next million Mozillians). These are basically things that make Mozilla stronger, but are beyond and between what's already going on.

The question is: what does this look like concretely? Of all the blog postings from the last few weeks, David Boswell took the best kick at this can. Offer grants and collect donations (yes, and more strategically). Build bridges between people using Mozilla technologies in their own work (yes, and how it happens matters alot). Promote what Mozilla communities are doing (yes, but how do we do it well?). Use our broader community as a laboratory (for sure, and that was what I was dreaming of here). I totally agree that the foundation should be doing stuff like this.

Sorry for repeat posting this. I figured it was important context.

Most of these things focus on the second layer of Mitchell's community spheres (what she calls 'community of action' and I call 'community of practice' ... we need to get clear on this language). This is the domain of shared tools and practices, which is a critical place for the foundation to play. However, as I have talked to Mozilla people, many have also emphasized things the foundation could do at the outer layers and even at the core of these spheres. I've listed a few here.

At the centre of the sphere sit communities producing Mozilla technology products. As above, it's not the foundation's job to do or meddle with this work. However, it can do things that build a better environment for the people creating these products. A good example is growing the number of colleges and universities offering community-based Mozilla courses like the one at Seneca. Work like this has the potential to benefit a wide variety of Mozilla communities through code contributions and, more importantly, a bigger contributor talent pool. However, people with heads down on individual products don't have time to grow something like this, especially as it takes long term investment and nurturing. The foundation could champion this kind of work in open source education -- and also further efforts in areas like accessibility and technology research -- in a way that benefits core Mozilla communities over the medium and long term.

At the very outer layer of the sphere is a vast community of users: 180 million people who interact with the internet everyday through Mozilla products. These are some of the most likely people in the world to care for and champion the open internet. Yet, a good chunk of them probably don't know what the open internet is and why it matters. The foundation could play a role in changing this. It could help people understand the issues emerging around data in the cloud. It could explain the role neutral networks play in driving innovation, commerce and community. And it could do these sorts of things in a way that activates, involves and showcases people from across Mozilla's many communities (think: FirefoxFlicks).

Reaching out like this to casual users of Mozilla products creates the opportunity not only to educate but also to engage. Some percentage of people touched through this sort of outreach will move into Mozilla's community of interest (the next layer from the edge). They will want to take action in some way. As David Eaves suggests, initial steps to support people like these could be quite simple:

a) greet these newcomers and make them feel welcome; and b) (create) some capacity to point them in the direction of a variety of institutions, organizations, projects and activities, where they can channel their energy.

The foundation could also give these people a simple way to demonstrate their willingness to contribute to the open internet. Maybe this is simply signing a pledge to shows how their work contributes to the goals of the Mozilla Manifesto. Or maybe it is something else. In some ways, the specific approach doesn't matter. What matters is that people feel a sense of belonging ... and that they feel encouraged to stretch themselves to contribute in even more concrete ways. Maybe these people are part of the community laboratory that David B. describes? Who knows? The point is to invite them in and find out.

This is not intended as a definitive list of things the foundation could do. Far from it. Instead, it is meant as an experiment: I wanted to see what it would look like if listed concrete things the foundation could do to add value in all the main spheres where Mozilla communities work.

Of course, the idea with an experiment like this is to create a starting point for seeking further ideas and advice. So: what else? What are the concrete things the foundation can be doing between and beyond existing efforts that also add value to the Mozilla community? I am hoping that the Air Mozilla tomorrow will provide a first chance to take this conversation further. I have no doubt there will be many more.

PS. Sorry for repeating the picture from my previous post. I felt it was worth showing the circles again as context ... knowing that this is my view and we still more discussion on these.

Me and Mozilla

Over the past few months, I've been musing a fair bit about Mozilla. The main reason for this is now widely known: I'm hoping to take on the role of Executive Director at the Mozilla Foundation. On Wednesday, Mitchell, Asa and I will be on Air Mozilla to meet the community and get advice on what a successful future for the Foundation would look like.

Mozshirt

This conversation started with a simple itch to contribute. Reading a post by Mitchell back in March, it struck me that Mozilla was facing many of the same questions I've been struggling with for years. I wasn't yet thinking 'I want to be executive director' ... just that there was some interesting intersections here. I wrote this mail:

Mitchell

A few days back, I read your post about the ED hiring process. I haven't stopped thinking about the Mozilla Foundation since. I'm convinced I've got something to offer Mozilla as it charts it's future.

For the past four years, I've been asking: how do you build an effective foundation, NGO network or social movement with open source thinking built right into its DNA?

In 2005, I started and led a $26 million initiative that mixed grantmaking and community building to connect grassroots technology activists in emerging economies. After passing that off last year, I joined the Shuttleworth Foundation in South Africa to help integrate transparency, networks and iterative learning more deeply into their day-to-day work.

In both cases, I've really struggled with the right balance of organizational models: vibrant open source project; catalytic social investor; bottom-up mass movement. From the little I've read online, it seems like the Mozilla Foundation is currently grappling with this same question.

This question is an important one. We have the chance to weave the values of openness, innovation and opportunity not only into the Internet, but also into our economy and society as whole. Promoting and protecting these values requires a completely new kind of organization, fueled by emergence, community and creativity.

Building this new kind of organization is what I am committed to and driven by. And, to a great degree, it's what I've been working on for a while now

I believe my experience so far can help the Mozilla Foundation. This help might simply be a conversation. It might be a link between our work at Shuttleworth and the next iteration of Mozilla Foundation. Or, it might mean me stepping up as a Mozilla executive director candidate. I'm not sure yet.

What I know is we've got enough in common that it's worth a chat. I LOVE the work I'm already doing with the Shuttleworth Foundation, and I am not really in job search mode. But, there's an itch here. It's worth scratching.

Cheers ... MS

The dozens of conversations I have had since have been both inspiring and humbling. Not only have the Mozillians I've met so far achieved a great deal, but they've done it with a mix of feet-on-the-ground practicality and big picture vision that I've rarely seen. At the same time, they're constantly asking tough questions like 'how could this be better'? It is quite amazing.

These conversations have left no doubt in my mind: I could contribute -- and learn -- a great deal as Mozilla Foundation executive director. I want to do this. With all my heart.

Of course, these conversations have also left me with many questions. What role should the Foundation play within the broader Mozilla Project? What do existing Mozilla communities need from the Foundation? And how can the Foundation build on and leverage Mozilla technology to reach a broader community of people who want to keep the internet open? I've already asked alot of people these questions and started reflecting on my blog. I am hoping that Wednesday's Air Mozilla will provide a chance to dig deeper and learn what more people think.

In the meantime, I plan to share a few more thoughts on concrete things the Foundation might be doing in each of the 'community circles' mentioned in previous posts. I will post on this tomorrow.

Open Education at OSCON 2008

Danese Cooper has organized what promises to be an excellent conversation about open education at OSCON in Portland. Mark Shuttleworth will be part of the mix. Karien and I prepared some quick background notes for Mark re: what think is exciting in this space and the specific work we're doing. I figured it would be useful to share here:

1. A growing number of people are creating open, collaborative learning content. This is exciting. It not only increases access to knowledge, it also adds more creativity and collaboration to the classroom.

2. While it draws on the values and techniques of open source, open educational content is different. That's the point of the Cape Town Declaration: to define the principles that should guide open education.

  • The Declaration calls for open approaches to content, technology and teaching
  • 1600 people and 165 organizations have signed the declaration since January
  • Signatories include everyone from Jimmy Wales to Desmond Tutu to Peter Gabriel

3. It's also important to do bold, concrete experiments where we figure out the techniques that make open education work. That's why we're creating a set of free, collaborative textbooks for South African schools.

  • Will cover all core subjects in South African curriculum from k-12
  • Focus is not just free beer: the aim is to get teachers to create collaboratively
  • Helping to build a platform standard by working with Connexions at Rice University

Other open edu co-conspirators on the panel: Brian Behlendorf (who will hopefully talk about the super cool and disruptive Seneca / Mozilla open source course model); David Wiley (inventor of the first open content license and open ed super hero); and Bobbi Kurshan (fearless leader of the Curriki revolution). If you're going to OSCON next week, this panel is a must see. Sadly, I won't be there myself.

Unbundling education

One of the highlights of this week's PCF5 conference in London was Richard Heller's presentation on the emerging Peoples Uni.project.

Img_6686 (Modified)

Peoples-Uni offers online professional development courses to public health workers in developing and emerging economies. Interesting enough in it's own right, but more interesting is how they do it:

  1. The focus is on teaching and online facilitation, not materials creation. Which means all the energy goes into responding to student needs. All the materials are off the shelf existing open educational resources from places like Johns Hopkins.
  2. All the instructors are volunteers. The volunteer pool includes: a gaggle of retired professors; recent graduates from a public health masters program in the UK; and 30 health care economists. Heller is having to grapple with the kinds of volunteer management issues common in open source projects, but rarely dealt with in open education.
  3. At the end of each course, students have the option of being accredited through tests administered by the Royal Society of Health. This is the same test that students taking similar courses in formal institutions would get. If they pass, they receive a certificate.

The intersection between 'hacked together volunteer run courses' and 'very serious, buttoned-down assessment and accreditation' is very cool. Right now, almost all education fuses instruction and accreditation. The result is often inflexible, boring instruction driven by the testing process. Unbundling accreditation from instruction changes this. It creates space for innovation on the instruction side, especially when combined with open educational resources. I think we are going to see more of this.

Heller's presentation was one of about 20 on open educational resources, mostly from poorer Commonwealth countries. Which, really, was amazing. All of the presentations are well documented on WikiEducator. It's worth taking a look.

Budapest + Cape Town: What's Open?

During our PCF5 workshop on the Cape Town Declaration, Paul West and I got into a collegial debate about the definition of an 'open educational resource'. He held up a book he's working on and said: "This contains legal advice that I've had vetted, so I want to release it under a no-derivatives Creative Commons license. I think this is an open educational resource. Do you?"

My answer was 'no'. For me, the fundamental test of an open educational resource is whether it is under a license and uses a format that allows remixing. This is how we defined it in the Cape Town Declaration:

Open educational resources should be freely shared through open licenses which facilitate use, revision, translation, improvement and sharing by anyone. Resources should be published in formats that facilitate both use and editing, and that accommodate a diversity of technical platforms.

The real promise of open education rests on this remixability. It's what creates space for increased innovation and creativity in learning.

Of course, there is an important place in education for fixed, authoritative works like the one Paul describes. And, there is no question, releasing these under an open license like CC-ND is a very good thing. However, I would label such documents as 'open access resources' rather than 'open educational resources'.

While may seem like nit-picking, it's important to be clear on the differences here. The stakes are high. The Budapest Declaration defined the minimum spec for an open access resource, which benefited the worlds of education and research tremendously. Cape Town has now set out a spec for open education resources. It may have a similar effect over time, but only if we are clear that open educational resources represent a separate and complimentary tactic to open access. They are about the potential of remixable education.

More on Mozilla: communities, circles and maps

Mitchell and others recently posted about the Mozilla community as a series of concentric circles. These posts make it clear that being a part of a community like Mozilla (or not) isn't a binary switch. Rather, people have varying degrees of involvement and connection. There are different kinds of community members. And, one person might be multiple places in the community at once.

This is a very useful idea. It provides a sort of map to help sort out all the ideas floating around about the evolution of the Mozilla Foundation might do. However, as Mitchell said in her first post, this map only works if the the language and concepts are fairly precise. More conversation is needed to get this point. My take is something like this ...

Img_6676

The centre circle in Mozilla feels like it's about the creation of specific artifacts (a web browser) and outcomes (a world record). For me, this is more than just a 'community of practice'. It's a community that makes things. Matthew Aslett gets close to describing this with 'developer community'. However, it would be great to have a term that incorporates people who create concrete things that aren't code (e.g. documentation or marketing campaigns). Maybe this centre circle is a 'community of production'? I am not sure. Whatever term sits at the centre should be about creating concrete things.

As Mitchell describes it, the next circle is much more in like with what I understand to be a community of practice: a group of people who work in a similar way (shared practices), often for a similar purpose (shared values). A loose association of cabinet makers in Vermont could be a community of practice. They swap ideas. They share local techniques. The might even share specialized tools. But they do not work together on producing a common artifact: they each make their own cabinets. Similarly, there are people and projects who share decision making models (module ownership), tools (Bugzilla) and values (an open Internet and others working on open source) with people producing Mozilla products, but these people are working on their own artifacts and activities. For me, this is what a community of practice looks like.

At the outer edges of the circle, Mitchell's take on 'community of interest' (share Mozilla values) and 'user community' (use Mozilla products) feels spot on. As Gerv points out, the potential in seeing these groups differently -- and helping people move from one to the other -- is huge:

The Community of Interest is formed from people who were in the User Community, but then became aware enough about the project to a) see that we have a mission, b) learn what it is, and c) decide that it’s a good idea. Exactly how we benefit from this will differ from person to person. It may be that ordinary users are more eager to recommend Firefox to their friends. It may be that a politician considers us when involved in patent policy. It may be that a web designer remembers us when his boss asks him to construct an IE-only site “because it’s quicker”.

In some ways, this is a much clearer articulation of what I was trying to get to with my Next Million Mozillians post: finding a way to get people to move from 'Firefox is cool!' to 'Firefox is important!'. Which hopefully leads to some sort of action, even if it is only telling someone else why Firefox and the open Internet matter.

Img_6670

Of course, thinking of Mozilla as a series of circles oversimplifies a little. Just as there is no single open source community, it's likely there is no single Mozilla community. Each part of the circle includes a myriad of people, projects and ideas. And people will often sit within multiple parts of the circle at once as they are working on multiple things. Which is a good thing.

Still, the circles provide a useful framework for thinking thinking through all the ideas people have been putting on the table. Strengthening, supporting and connecting various pieces of Mozilla 'community or production' is a very different activity than moving millions of people from 'user community' to 'community of interest'. Yet, both are important, and both are probably a part of what the Foundation should be doing.

As a part of the broader 'where should the Mozilla Foundation go' discussion, it might be useful to look at specific things the Foundation could do in each of the circles ... and I guess also what the other pieces of the Mozilla Project are doing in each area. I'll come back to this in another post. Unless someone beats me to it.

Mapping open education policy opportunities

Just before leaving for Italy, I spent a day in London talking with friends about the open education policy agenda. The friends in question were Darius Cuplinskas and Melissa Hagemann from the Open Society Institute, James Dalziel from Macquarie University in Australia and Polish activist Jaroslaw Lipszyc. The conversation focused on how to understand and act on opportunities for government policy that supports the principles outlined in the Cape Town Open Education Declaration.

Img_6408

As we knew in advance, both Poland and Australia are fertile ground in terms of open ed. Polish activists like Jaroslaw have gotten the attention of politicians, a few of whom have expressed an interest in building ideas like free textbooks into their platform. And, as the large number of Cape Town signatures from Poland demonstrates, there is a great deal of academic and NGO support. In Australia, the opportunity is mostly around large scale computerization in the schools. As governments across the country roll out this agenda, they will eventually have to deal with the issue of content. James sees this as an opportunity.

Of course, there are lots of unanswered questions about the specifics of moving ahead with these opportunities. How to package and sell concrete open ed policy ideas? How are decisions made? Who are the right allies? We agreed that it would be worth going through a process to answer these questions and map the opportunities in each country. The rough schematic for the map looked like this:

Img_6405

Melissa is currently looking for someone to turn this sketch into a more formal spec for creating the maps. Once she's got a basic outline of what we are looking for, I will post it here. In the mean time, I am going to talk to Shuttleworth colleagues to see whether a similar process might be worthwhile in South Africa.

Scaffolding + support + investment = MoFo?

The Next Million Mozillians post has sparked some interesting ideas: browser plug-ins that make the whole of the web equally about consumption and contribution; simpler community-powered translation for open content and collaboration; helping people like educators who can weave open knowledge into the core of their work. It has also generated some good questions. What do we mean by the open web? And which bits of it is Mozilla Foundation best situated to drive? I'll loop back with an in-depth synthesis of all the comments and posts (keep 'em coming) in a couple of weeks when I am back from Italy.

Mozshort

In the mean time, I want to riff off Frank Hecker's question about how to engage and brainstorm with the Next Million Mozillians. Frank asked:

Why not send the (FF3 Download) pledgees a message and ask them what they'd like to see Mozilla do (if anything) other than shipping Firefox and other products? [snip] If even 1-2% of people responded to such an appeal with useful suggestions, that would still amount to thousands of people providing their personal thoughts, and possibly hundreds of people who were willing to contribute their time in some form as volunteers.

While sending an e-mail to all the Firefox 3 downloaders may not be the right way to engage (I recall a promise not to send follow up mail), it feels like Frank is headed in the right direction. Mozilla has touch points with millions of people on a regular basis. When it makes contact, I could embed simple, discreet opportunities for these people to contribute either opinions or time.

Of course, if it did this, Mozilla could end up with a new problem: too many ideas on the table plus the expectation that it will do something with them all. Getting around this problem -- or, better, turning this problem into an opportunity -- seems like one of the key design challenges for a more broadly focused Mozilla Foundation. How do you enable and encourage large numbers of open web ideas but only dig deep on the ones that fit with the Mozilla DNA?

The answer may be some combo of scaffolding + support + investment that comes in at different stages in the evolution of an idea. Possibly something like this (click here for PDF):

Moz prize funnel

The specific ideas, tools and nomenclature (prizes, wikis, etc) don't matter as much as the levels (scaffolding, support, investment). Scaffolding lets 1000s of people with 1000s of ideas play with ways to improve the open web, but with little or no direct involvement from Mozilla. Mentoring, publicity, travel funds, matching grants and other kinds of in-direct support help the good ideas grow, but with Mozilla only playing a minor role, lending its advice, connections and tiny pots of highly leveraged resources (e.g. travel funds for project meetings). More significant investment and hands on follow through happens only where there are ideas that fit well with Mozilla's DNA, help grow the open web and have the potential to scale wildly.

On the product side, Mozilla already plays across a spectrum like this. Firefox represents a huge investment of time, energy and committment. It is built on large scale community processes that require rigour and hard work. However, Mozilla is also a key player in a bigger ecosystem made up of thousands of people and organizations building tools for the open web that come in all shapes, sizes and levels of ambition. Mozilla -- amongs others -- is a part of the scaffolding that makes this ecosystem possible.

A practical question: could and should Mozilla apply this combo of rigourous, large scale open source thinking plus catalytic ecosystem scaffolding to it moves more broadly into 'ideas that drive the open web' -- open software, videos, data, science, business models, whatever? While my gut says 'yes', I don't quite know what the boundaries are (anything that meets the 'Mozilla DNA test'?) or how it would work exactly (e.g. prizes or grants or something else?).

Which is of course why I wanted to post before taking off for two weeks. I want to know what other people think. Is this a useful way for the Mozilla Foundation to think about its engagement with the Next Million Mozillians? If so, what questions need to be answered first? Are there some places (emerging market countries?) or topics (participation? education? politics 2.0?) that offer better places to start than others?Could the Mozilla Manifesto, further articulated and evolved, provide some of the conceptual scaffolding needed to spark and focus people? I wonder.

Learning from open access

Yesterday, Melissa Hagemann, Eve Gray and I led a workshop called Opening Scholarship at Elpub 2008. Our aim was to dig into a very specific question: what lessons can those of us working on open education learn from the open access to research movement. As the room was filled with experienced open access folks (that's the theme of the conference), it seemed like a good place to ask this.

It turned out we were right. There was three hours of fun and intense conversation about both open access and education. At the end, we brainstormed key takeaways with the group:

  1. Use the 'public access argument'. If public dollars are paying for educational materials, the public should be able to use (and evolve) them freely.
  2. Build coalitions. Bringing researchers, universities and taxpayer rights advocates together under the Alliance for Taxpayer Access banner was critical to the open access NIH victory.
  3. Be strategic about where to focus early open education efforts, looking for areas like vocational training where traditional publishers are weak.
  4. Engage business and think about business models early on. Open access has worked in part because progressive publishers are involved and because there isn't just one business model.
  5. Be patient and explain what you are on about consistently. It's only after years of calm explanations and experimentation that bigger publishers have come to open access.
  6. Invest in early test cases that show what is possible. Do research. Develop metrics. Write up the best cases.
  7. Build a network of champions and evangelists who can talk about these early successes. And make sure to start building leadership in emerging economies early on.

On top off all this, there was also a good deal of reflection on the fact that open education is a different kettle of fish from open access to research. It's not just about getting stuff out there, it's about making it remixable and improvable by communities of teachers. And, by extension, it's also about changing how we teach and learn, and putting students much more in the educational drivers seat.

As one participant said at the end of workshop. "Open education could be much more disruptive than open access was. It could be revolutionary." Yup, I think so.

Shuttleworth open licensing policy now online

A few months back, I posted a draft How We Work article on the Shuttleworth Foundation's open licensing strategy. The basic idea is that we want everything we do and fund to be under an open license. As my article says, this hasn't always worked as we haven't had a clear policy on the matter. Good news: now we do.

Andrew Rens and Karen Gabriels have polished off our Open Resources Statement of Principle. It says things like:

All Agreements entered into by the Foundation which include the creation of resources shall ensure that the resources are open resources, and shall record how the Intellectual Property in the resources is owned and licensed.

and

Resources are open resources when they are available for revision, translation, improvement and sharing under open licences, open standards and in open formats, free of technical protection measures.

This will now flow into an update of our standard grant and consulting contracts, and generally guide us as we go forward. Great work, Andrew and Karen!

With the release of this policy, we've also finalized and polished my article on the topic of open licensing. It's up on the Foundation site in both HTML and PDF.

Agile philanthropy: how our fellowships work

Last month, we sat down to have another How We Work conversation at Shuttleworth Foundation. Under the microscope this time: our Fellowships Program. We're all pretty happy with this program. So, the aim was to reflect on why it seems to be working ... and to find ways to tweak and improve it.

The fellowships idea has a simple genesis: the desire to work with people on the front edge of issues like open education, knowledge and telecom in a way that is at once agile and high impact. Projects and grants sometimes work for this. However, they just as often create a situation where the Foundation is talking to the right people (smart, connected and engaged on the issues that matter to us) in the wrong way (long project negotiations trying to fit round pegs into square holes). The fellowships emerged about 18 months ago so we have a way to make bets not just on projects but also on people. 

We currently have four fellows. Andrew Rens working on access to knowledge and intellectual property. Steve Song on open telecom. Steve Vosloo on communications and analysis (aka 'how education needs to work differently in the 21st century'). And myself with the dual hat of open philanthropy and open education. With the exception of myself, all the fellows work in our Cape Town office alongside the people who manage our grant making and in-house projects.

When Helen, Jason and the four of us fellows reflected on the program last month, some of the things we said were ...

1. The 'make bets on smart people' works for us.

The fellowships are based on the 'make bets on smart people and let them run' model. This approach has bought the Foundation two things: agility (we can move quickly on ideas and issues) and intellectual momentum (I can't think of a better term ... but basically we are moving as a group on the issues that matter to us). Also, we've created a brainstormy hothouse in the office, with ideas bouncing about constantly. This not only has the fellows fueling each other but also feeds projects like Siyavula and Kusasa and the organization as a whole.

2. We're starting to get traction on issues that matter ...

While it's still early days, we're starting to get traction on specific work led by the fellows. Steve Song has gathered people around the beautifully disruptive idea of the village telco. Andrew has helped South Africa drive the openness agenda in the OOXML / ISO discussions. Steve Vosloo is helping to shape the conversation on mother tongue instruction, which is a critical issue in the future of South African education. I helped a group of open education pioneers birth the Cape Town Declaration. These are small scale results, for sure. But are concrete and, more importantly, they represent the kind of things we want to see happening in the world. 

3. ... but follow through is sometimes tough.

On the flip side, we haven't always had perfect follow through on this early traction. If I just look at the Cape Town Declaration, we could have done more to quickly seize the momentum we built with the Declaration launch in January. This could have been fixed in part by me blogging, engaging and pushing more post launch. The fellowships are all about this kind of 'just roll up your sleeves' action. However, our not perfect Cape Town follow through is also related to the fact that we've tried to organize some of our next step activities using grants (watch soon for Open Education News) ... which is a slower way to get things rolling. We need to think about how we elegantly combine grants and fellowship energy in the future. We have an opportunity to move further faster combining these things, but we aren't there yet.

4. Getting the word out is even tougher.

We've also had a tough time sharing and communicating the ideas emerging from the fellows. All of the fellows are blogging, some in high profile places. This is good. There is a blog aggregator. Which is also helpful, although it's not clear who follows it. What's needed now is a better web site that pushes people to this material more aggressively. MOre importantly, we need a better strategy for getting people engaged: more thoughtful links between our e-mail newsletter and our most compelling posts; blogging about other people's work, especially the Foundation's partners; getting other bloggers to link to what we're writing. Small, simple stuff. We need to do it.

5. Paper, podiums and parties are great ... but needs discipline.

The tongue-in-cheek mandate for the fellows program is 'papers, podiums and parties'. Papers = writing and blogging to push thought leadership. Podiums = speaking and evangelizing. Parties = running events and building networks. Tongue-in-cheek or not, this trio actually serves well as a way to check whether we're working on the right things. A quick reflection at the meeting showed that most of us are doing well in one or two areas, but not necessarily in all. Eg. Steve Vosloo's work on mother tongue has a great paper and he's spoken on podiums ... but we need to follow through with some sort of symposium on the topic (a party). We need to be a bit more disciplined about tracking what we are doing in these areas and filling in the gaps.

The bullets above are a gut reflection on the meeting MP3 and my notes, which I just went over last week. I will write a more formal How We Work article on fellowships sometime in July. If you have questions or would like me to dig deeper on any particular points, please post comments here.

The Next Million Mozillians

Last week, David Eaves blogged about the potential for Mozilla to energize -- and maybe even lead -- a mass movement for the open web. My response: hear! hear! More thinking, experimenting, conversing, inventing, definitionizing, evangelizing, politicking, standard-making and party-throwing in the name of the open web is very much needed. And Mozilla is certainly well situated to stir this pot.

firefox shirt.jpg

What would it take to stir the pot? Probably a re-imagined and re-invigorated Mozilla Foundation

Currently, the Foundation acts as steward for Mozilla Corporation and Mozilla Messaging, which are owned by the Foundation but run with their own leadership and resources (I like this model). It supports a handful of other Mozilla software projects. And it gives out a small number of grants related to open source and web accessibility. All of these things contribute to the open web, some (stewarding Firefox!) in a massive way. The Foundation should keep doing these things.

Yet, there is still space for the Foundation to be thinking bigger. Looking for the next risky, audacious, disruptive ideas that will make the open web more useful and more fun. Strengthening not only the technical building blocks of the open web (software and standards), but also the social ones (community and business models)? And, getting ordinary people excited about the open web and why it matters? Which is where this idea of a movement comes in.

If Mozilla stepped into the movement building game, it would clearly have a head start: 170 million people who use Firefox and a killer track record building community.

img_6389.jpg

However, there is also a critical piece missing: the ability to help large numbers (millions?) of people make the shift from being a consumer to being contributor. Not contributors to Mozilla Project code. Or even to documentation or marketing. Rather, imagine 170 million contributors to the project of making the open web stronger, better understood and more resilient. This would be very cool movement indeed.

This week's Downlod Firefox campaign demonstrated that, at least on the company side, Mozilla has the horsepower and respect to galvanize large numbers of people. Over 8 million people downloaded Firefox 3 in a day. In some ways more impressively, 1.6 million pledged to do so in advance. These pledgers care about Mozilla, and want to chip in to making the web more open. This problem is, beyond downloading, there is very little for ordinary, not-so-techie folks to chip in on. 

img_6392.jpg

Mozilla Foundation could change this. It could invite people en masse to help define what we mean by the open web (really, we need to work on this). It could encourage them make videos, mashup pictures and write blog postings that explain the importance of the open web to my grandmother (or my kids). And, over time, it could give people -- geek and non-geek alike -- the scaffolding and encouragement they need to invent new pieces of the open web that have not yet been imagined. Pieces that use openness and participation to make the web better for work / music / life / love / play / the-stuff-that-matters. Imagined this way, the Foundation has the chance to create the next million actively contributing Mozillians. I think it should take that chance.

Which isn't to suggest that Mozilla should drop its driven focus on great, community-built tech products. Not at all. Firefox and other Mozilla products are critical to keeping the web open. However, one can imagine the Foundation as movement yin to the Corporation's awesome product yang. Parts of a whole.

img_6385.jpg

As somebody whose job at Shuttleworth is to make the world better using open source tactics, thinking through this version of the Mozilla Foundation fascinates me. I've shared this fascination with a few Mozillians, asking: if the Foundation were in the movement building business, what would it look like? Where are the geek (and not just Firefox) and non-geek (and not just marketing) sweet spots for the next million contributors? I have to admit, I don't know myself. I have vague hunches (above) and a desire to dig deeper. I'm hoping the Mozillians I am talking to have ideas to share. And maybe you do to. If so, I'd love to hear them. I promise to post again to pull together any good ideas that emerge.