Archive for the ‘freeculture’ Category

Healthy Competition

Thursday, September 7th, 2006
This week’s column for the New Statesman focuses on botched government IT projects, and suggests that code commissioned by the government should be open.
“The recent announcement that the Financial Services Authority is investigating iSoft, the troubled computer software company charged with delivering a large part of the new, centralised patient records system for the National Health Service, is just another sorry episode in the government’s Connecting for Health initiative.

”In June 2005, Fujitsu, winner of the contract for southern England, changed horses midstream and dumped its software supplier…”

Read the rest here.

Revolution at our fingertips

Wednesday, September 6th, 2006
This fortnight’s column for openDemocracy centres on a book I discovered while researching a paper I am currently writing for the Ford Foundation on freedom of expression in the networked information age. The book is written by Ithiel De Sola Pool, a prolific scholar of political science and sociology. Although it was written in 1983, it is eerily prescient, and thus rather humbling. I believe it is out of print - a great shame:
When we are caught in the centre of an emerging phenomenon, in the eye of the networked information age’s storm, only the clearest thinkers can lead us to safe harbour. Historians have the benefit of hindsight, while those writers who have predicted everything from the demise of the English language through SMS messaging to the disappearance of musical innovation thanks to peer-to-peer filesharing will no doubt be silenced in the passing of time.
“A half dozen books have informed my thinking about the effects of the internet…”

Read the rest here.

Child star flash mobs BPI

Thursday, August 17th, 2006
When I was a kid, I used to think working in the music industry would be, like, the coolest thing ever. In my early twenties, I started doing music writing, and started having my doubts. Then, as a tech journalist, I started meeting people from the BPI and I knew the mirror had cracked.

At twelve, this kid is never going to have that experience. She already knows the industry sucks. That’s why she flash-mobbed BPI headquarters on Tuesday, after they took her single off the fledgling “kiddie-chart”. The BPI’s logic? Her single was released on Flowerburger records, a label currently petitioning the BPI to stop suing filesharers. From The Inquirer:
“12 year-old singer-songwriter Amy Thomas staged a protest outside the headquarters of the British music industry yesterday, following a decision to ban her from a new school kids’ music chart because of her views on downloading.”
Read the rest here. (via Techdirt)

Happy Birthday FLOSS

Friday, August 11th, 2006
This week’s column in the New Statesman celebrates 15 years of open source:
“Fifteen years ago this month, when the internet was the domain of the geeky and the good, a young computer science student from Finland sent an e-mail to a message list of programmers. ‘Hello everybody out there using Minix,’ began the message, ‘I’m doing a (free) operating system (just a hobby, won’t be big and professional like GNU) . . .’. Linus Torvalds couldn’t have been more wrong…”
Read the rest here.

Property market

Thursday, July 20th, 2006
This week’s column in the New Statesman is on the Gowers Review of Intellectual property and a report from Rufus Pollock for the ippr:
“As the British Phonographic Industry, the body that represents the UK music business, begins a fresh assault on those who use peer-to-peer file-sharing networks to download music illegally off the internet, it’s worth asking if there might be a better way to protect the creative industries than by punishing potential customers.

This autumn, the government will wind up a nine-month review tasked with examining intellectual property (IP) law…”

Read the rest here:

Useful links:

Recommended listening: Innovation and IP

Monday, July 17th, 2006

The ippr have just posted audio from an event I attended on Friday last week, the last in their series to accompany the UK Gowers Review of Intellectual property. Hear Lord Sainsbury (DTI), Chris Parker (Microsoft), Rufus Pollock (Open Knowledge Foundation) and Dr Richard Jennings (Cambridge Enterprise) on Innovation in the Information Age, then listen to the assembled audience of IP lawyers, rightsholder lobbyists, free culture folk and journalists give them a grilling. My favourite part is when Bobbie Johnson of the Guardian asked Sainsbury if the Tories had patented sleaze, and if so, were Labour licensing it off them

Open source nation

Monday, September 19th, 2005
(originally published on openDemocracy)

Geoff Mulgan sees two ways in which organisational principles borrowed from the world of open source can make the political process more accountable. One is in turning democracy back into a conversation, the other in allowing the people to scrutinise public services. But, he warns, there still needs to be a recognisable place where the buck stops. Becky Hogge spoke to him.

Earlier this year, Geoff Mulgan and Tom Steinberg, with Omar Salem, published a paper for the UK think tank Demos which is widely becoming seen as the seminal work on open source methodology.

The paper, Wide Open, described the methods developed in the production of the open source operating system Linux and the free, collaborative encyclopedia Wikipedia as embodying:
“a new way of creating knowledge that combines an open and democratic ethos with the extraordinary ability to produce work of high quality and on a huge scale”
Wide Open investigated possible applications of these methods in fields as diverse as bioscience, politics and journalism. openDemocracy’s Becky Hogge went along to Geoff Mulgan’s offices at the Young Foundation in east London to find out what open source methods can do for 21st century politics, and where this leaves traditional ideas of accountability.

***

Becky Hogge: Can open source methodology, or, as the paper preferred to call them, open methods, really be called democratic?

Geoff Mulgan: When we wrote that, we meant democratic in spirit. With open methods, anyone can take part without prior qualifications or having been asked to do so or being part of an established hierarchy.

Democracy is conversation and there are deep roots for ideas about a society being able to talk about itself, going back to the Buddhists and the ancient Greeks.

Every civilisation has traditions of people arguing – this is not a western idea at all. Of course when democracy came into being in the late 18th and 19th centuries, because of the scale of the organisation of the state, because of the lack of technology, those conversations had to essentially take place within parliament – speaking parliaments with speakers overseeing them and so on. The rest of the conversation was somewhat of a monologue either by parties or newspapers.

In a 21st century democracy, many more people should be involved in the conversation that precedes a decision. It’s really only in the last twenty or thirty years that technology has made it possible to rethink how to organise much wider conversations that involve sixty million people in a country like the UK or several hundred million in a country like the United States.

But for those conversations to be meaningful there have to be organising principles, there can’t just be a free-for-all cacophony because not everyone can be heard in the permitted bandwidth.

Becky Hogge: And that’s where open methods come in?

Geoff Mulgan: Yes. Essentially, where the object is producing the best and the most usable thing, which may be a Wikipedia or a software programme, the argument is that most existing organisational principles we have don’t work very well. Therefore, organisational principles which reward or give most weight to the best, the most respected, very much like the vetting procedures of Linus Torvalds and his deputies or the collective scrutiny of Wikipedians, should be superior.

Tom and I spent a lot of time trying to find the appropriate word for this kind of organisational structure, going through our ancient Greek dictionaries. The irony is that “aristocracy” technically means rewarding the best input but, of course, every aristocracy that we’ve ever come across is full of the worst rather than the best so the word has completely lost that meaning.

Becky Hogge: So reputational systems, like the ones used in creating Wikipedia or Linux, can help structure wider conversations that lead to better democracy?

Geoff Mulgan: That’s right. At the moment reputational systems look like the best ones to run with. My expectation is that within the next twenty or thirty years you will see lots of experimentation with direct participative models. Deliberative polls, citizens’ juries and reputational systems – and each of these uses a different principle of how to involve a much larger number of people and the ultimate test will be which delivers more legitimate, better decisions in the long run.

Becky Hogge: But this sounds an awful lot like “consultation” – isn’t that a dirty word in politics?

Geoff Mulgan: Sure, sometimes. Take, for example, the British Labour party’s “Big Conversation” of a year and a half ago, which I was heavily involved in trying to design. That was attempting to get a more genuinely reciprocal conversation between the ruling party and the public, holding hundreds of meetings in constituencies with MPs, stakeholder groups, NGOs and so on, in a fairly public way.

One of the very predictable problems that exercise ran into was that it went alongside some classic internal decision-making, strategy-making processes which in some ways were superior to an open conversation. If you are trying to plan exactly what the National Health Service should do in the next five or ten years you get involved in huge complexities of money, organisation and so on which you can’t really get to in a general discussion. But you can have regular discussions on something like smoking bans, about what to do with alcohol, or chronic disease management.

Secondly, a lot of the bits of the party really had no training in how to do open conversation, including MPs. Some MPs were brilliant at it, but some were simply not culturally at ease with a genuinely open conversation about politics and policy. They were used to being a transmission belt from the centre and I think to a degree the media and the public didn’t know what to think. They weren’t sure whether it was a completely manipulative ruse to give the appearance of openness or if there was anything serious in there. In a way this was probably a transitional example.

But my guess is that in the future all parties will feel the need to have some kind of conversation with an electorate ahead of their manifestos and policies and it will always be somewhat ambiguous. In some ways what comes out will not reflect what happened in those conversations but instead will reflect the beliefs of the leaders and the core party.

If it doesn’t then, to some extent, what’s the point of having them there to make sometimes difficult judgements which may go against what the public wants? But I think the era of simply top-down monologue organisation is over and I think the Labour party should at least be commended for having made the attempt to do things in a different way.

Becky Hogge: So open methods aren’t there for the difficult decisions?

Geoff Mulgan: For institutions spending large sums of money, going to war, things like that, I would be pretty worried about any organisation or innovations which made it less clear where the buck stops. There are lots of other activities ranging from the organisation of science to culture where you can have much more efficient ways of doing things without very strict hierarchies. But, crudely, you need the most accountability the closer you get to the core power activities of the state which are essentially spending money and using force.

Becky Hogge: So, if open source isn’t for decision making, what is it for? And does it always compromise accountability?

Geoff Mulgan: Not at all. Right now, the UK is spending several billion on auditors and inspectors for its public services – often on people who should be actually teaching in schools and working in hospitals. In my ideal future, much more of that work is performed by the public using open methods supplemented with templates to make sense of what they should be looking for in their local schools, their hospitals and their police force.

These volunteer scrutineers would use open methods to aggregate deliberation and to get the messages to the right managers, as it were, in close to real time. It will still be up to each of those agencies whether they take any notice of it or not – that’s the pinch, the weakness of open methods. But once you have that in place it would greatly change the operating climate for public services.

So if you were a police chief and you had hundreds of thousands of people in your area commenting on whether you were making the right decisions on – it could be stop-and-search policy for example – then that’s one of the things the media would look to, that’s one of the things elected politicians would look to and the whole climate of behaviour would shift. That’s where I think these open methods are most appropriate.

Becky Hogge: But with so much disenchantment surrounding the political process and public services, in Britain and elsewhere, is that scenario really plausible?

Geoff Mulgan: A huge amount of our society works on this kind of gift economy. The National Health Service has at least half a million volunteers without whom it would collapse tomorrow. The schooling system has, I think its four hundred thousand governors at the moment, none of whom is paid a penny to help their local schools to operate. Despite what is happening to democracy in terms of disenchantment, we still have twenty thousand councillors and hundreds of thousands of political activists working on a voluntary basis.

Most people aren’t doing it for any particular reward. You could also say that much of art and culture is essentially a gift model. People are motivated by the quality of what they do and what they are involved in, and not always by monetary reward. I don’t see any sign of that diminishing.

I think the challenge for any of the new ideas in the open methods field is whether people in practice will be motivated enough to get involved. This will hinge on whether they see a direct enough link between what they have put in and something happening. Precisely the appeal of something like Wikipedia is that you can see a relationship between what you put in and what you get out. I would like to see many other domains in which there was a clearer link between input and output.

Becky Hogge: To sum up, do you think open methods offer significant innovation to accountability practice?

Geoff Mulgan: There’s a tradition of how you make people accountable to you before they act, ex ante, for example by giving them a mandate. Then there’s a whole tradition of being accountable after the act, post hoc, like general elections to decide if the government is any good, or AGMs where a company is judged on the totality of what it’s done.

I think what’s very interesting about open methods is that they are introducing something more like real time accountability and feedback. Even if that won’t have quite the same sort of constitutional strength as the ex ante or post hoc accountabilities, open methods will probably do more to change the spirit, the climate of decision-making than almost anything which can be done from either end.

Mozilla’s ‘magic pixie dust’

Monday, September 5th, 2005
(originally published on openDemocracy)

Open standards are just as important as open debate: Becky Hogge explains why openDemocracy recommends the Mozilla Firefox web browser.

It’s funny the little things you judge people by. A couple of weeks ago one of openDemocracy’s new interns shocked me when he exclaimed “I really can’t stand this Firefox thing”. He was referring to the web browser Mozilla Firefox, used as standard in the openDemocracy offices, yet new to him, a lifetime user of Microsoft’s Internet Explorer. But Firefox is more than just a browser: it is a symbol of the democratic use of the internet.

When Firefox 1.0 launched in the UK back in November 2004, it made the headlines. It was the first time the release of a piece of computer software merited its own leader in a national newspaper (Britain’s The Guardian). Online hipsters downloaded the web browser in droves, and the adoption of the open source technology snowballed. Mozilla Firefox now enjoys just over 8% of the browser market share – not bad in a market that has seen some of the most high profile monopoly actions in legal history.

The antitrust cases brought against Microsoft in the late nineties now seem like a distant memory. But in 1998, having been pushed out of the market by their Redmond competitor, a (comparatively) little company did a big thing. On 22 January, Netscape Communications Corporation, bruised and battered by the “browser wars” that for Microsoft were to end in court, gave away the source code for their Communicator 4.0 web browser.

For most of us, a whole pile of programming source code (the interface language between human and machine), is hardly an ideal gift. But to a growing community of programmers, it was as if all their overdue Christmas presents had come at once. These programmers, scattered all over the world but united by a collective enthusiasm for the opportunities for massive colaboration on software code that the internet offers, came to be known as the ‘open source’ community.

Netscape had timed their release well. Just seven months previously, a collection of essays by the technologist Eric S Raymond had been published under the beguiling title The Cathedral and the Bazaar. In the book, Raymond sung the praises of a new way of working on computer code, facilitated by the internet and pioneered by a young Finnish programmer, Linus Torvalds. Raymond defined the style of open source as against the hierarchical structures of commercial software companies, calling on Brook’s Law (“Adding more programmers to a late project makes it later”) to back up his case.

Instead of this “cathedral-building” style of working, with authority over code limited to a closely controlled set of employees working in a top-down structure, Raymond showed how working within a “bazaar” model – anarchic, open and ad hoc – produced faster, better results.

He had a big example to back him up. From the late eighties, the maverick MIT programmer Richard Stallman had been working on a Unix-based operating system cheekily called GNU (Gnu’s Not Unix). Programming had stalled on the design of one of the components, a kernel. Then in stepped Linus Torvalds and his band of merry programmers on the comp.os.minix USENET message board.

Together, in under six months, these programmers worked collaboratively to produce the Linux kernel, the final piece in Stallman’s puzzle. The coding was exuberant, fuelled by the programmers’ enthusiasm for the project. There was no financial gain for any of them, and Raymond surmised that they had been motivated by the appeal of reputation – the better the code they produced, the more their peers would respect them as coders.

The promise of respect encouraged many programmers to submit patches to Linux (Torvalds maxim “release early, release often” meant code was raw and riddled with “bugs”) and the schema worked – a reliable kernel emerged in less than a tenth of the time one would expect from a commercial software company. From this Raymond made his first, charming, deduction: “given enough eyeballs, all bugs are shallow”.

So, when Netscape released the source code of their browser, it was eyeballs they were after. They set up the Mozilla Organisation (later the Mozilla Foundation) to manage the further, open source development of the software into a second generation browser, capable of taking advantage of all that the world wide web had to offer. Initially the eyeballs were slow to come. Netscape had got open source a bit wrong, and hadn’t given the programmers the tools they needed. For their part, the open source community was slow to trust a commercial company bearing gifts. In 1999 one of the officers on the project resigned, with the famous parting line “open source isn’t magic pixie dust”.

Nevertheless, in September 2002 Mozilla made its first, tentative, release – the Phoenix browser. The browser would be almost unrecognisable to Firefox fans today. A slew of “beta” (test) versions followed, until, little by little, Firefox emerged.

It is no wonder then that the world was on tenterhooks when the first non-beta release emerged last year. But is the Firefox browser’s history in itself a reason to use the technology?

Yes. Simply put, Firefox is better because thousands of man hours have been invested by people all over the world in making it a stable, usable and enjoyable piece of software. It boasts superior functionality to Explorer – tabbed browsing, inbuilt RSS feeds, and pop-up control. Further, because the code is an open standard, that is, available for scrutiny by every coder from hobby hacker to six-figure silicon-valley geek, an army of ‘plugins’ – additional services – have been developed by dedicated Firefox fans. These range from ad blockers to chat software to scripts that can change the way a website looks.

Internet explorer, by contrast, has enjoyed massive market share for so long that there has been no impetus to develop new features and services for its captive audience of users. And with no access to the code, only Microsoft can provide these services. Further, partly because the browser is so integrated with the Microsoft desktop and partly because Microsoft has a bad track record at fixing security bugs, Internet Explorer has been gaining a reputation for poor security.

This is set to change. A new version of Internet Explorer, IE7, has been released in beta, with rumours of a 1.0 (non-beta) release at the end of this year. The new IE7 mirrors many of the features of Mozilla. But even sworn Microsoft camp-followers are sceptical about the new release, mainly because the browser refuses to conform to open standards of the web.

For openDemocracy’s part, we’ll be sticking with Firefox, and this week we urge our readers to do the same. After all, in terms of development, open standards on the web are just as important as open debate – as our intern now understands. What could be more democratic than that?