A quick comment on open, yin and yang

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.

I did a similar exercise to yours here:

http://commonspace.wordpress.com/2008/02/02/open-vs-open-vs-etc/

… 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.

Evolving Shuttleworth theory of change

September 19, 2008 § 1 Comment

One of the first things that I took on in my Shuttleworth open philanthropy gig was to help the team develop a ‘theory of change‘. The aim was two-fold: create a simple compass to guide internal decisions and develop a tool to help the rest of the world understand what we’re up to. Basically, we wanted a snapshot of how our collective brain works as a team.

Well, that was 18 months ago. We’ve had at least two all staffs, a dozen small group chats and countless online conversations since. And we’ve produced many iterations, at least one of which I have blogged about here. Not surprising. That’s how strategic planning-y things often go, especially when they are intentionally open ended like this one.

What is surprising was how useful all of this conversation has been in aligning our everyday thinking. Words that we didn’t have before — words we invented for the theory of change — have become a part of everyday thinking and decision making in the office. And, things we’ve believed in for a long time, like transparency and open licensing, have actually become a more real part of our work. Which, in the end, was probably the point.

As I leave the Foundation (last day :( today), I promised to do one more iteration based on recent conversations. It looks like this [big version] …

The aim was to simplify as much as possible, just showing the essence. Also, there are lots of changes to some of the core language we are using.

Also, I agreed to write up a series of notes describing each element on the theory of change with a little more detail. I’ve done this as a (pretty ugly) slide deck …

In the near future, our designer Eugene Badenhorst will soon take a shot at making the above diagram real pretty and then doing a small booklet based on the slides.

In the meantime, I highly encourage you to start adding thoughts into the mix, especially if you work closely with the Shuttleworth Foundation. Are we on the right track? If we aren’t, what’s missing? If we are, how close is our theory to our practice? Where do we need to work harder? Where are we full of it?

The idea is that this snapshot of our collective brain will continue to evolve, even after the pretty design. Getting feedback — good and bad —  from people who work with us is a critical part of this. Leave comments here, or send mail to Steve Song (the new lead on this), Helen and I.

Under the Hood: Open Source @ gov.za

August 25, 2008 § 2 Comments

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

Aslam Raffee – mouseover for audio

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).

How We Work Remix

August 20, 2008 § Leave a comment

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.

Budapest + Cape Town: What’s Open?

July 18, 2008 § 1 Comment

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.

Shuttleworth open licensing policy now online

June 26, 2008 § Leave a comment

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

June 23, 2008 § Leave a comment

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.

Where Am I?

You are currently browsing the shuttleworthfoundation category at commonspace.

Follow

Get every new post delivered to your Inbox.

Join 6,480 other followers