Joining the FSF Board of Directors

When I was 12 years old, I discovered free software. That discovery changed my life and I’ve never recovered.

Over what is now more than half of my life, I have looked to the Free Software Foundation for vision, guidance, and an example of a free world and I have rarely been disappointed. The list of directors of the FSF — Richard Stallman, Eben Moglen, Lawrence Lessig, Henri Poole, Gerry Sussman, Hal Abelson, and Geoffrey Knauth — doubles as a list of some of my greatest heroes and role models.

As such, I lack the words to describe how it feels that, just yesterday, I was elected to the board of directors of the Free Software Foundation. With Moglen having stepped down I have staggeringly large shoes to fill. I’m more than a little intimidated.

At 26 years old, I suspect that I’ll be the youngest person on the board by quite a bit. This means I’ll have to try and make up with hard work and passion what I lack in experience and wisdom. It’s a challenge I look forward to.

With free software becoming increasingly successful and widespread, we’ve already begun to see push back. I suspect that in the next years, we’ll see much more. We reaching the dangerous part of the, "first they ignore you, then they laugh at you, then they fight you, then you win" progression. I’ll do what I can to defend freedom until we’ve won.

In order to ensure that I have the time necessary, I’m going to be resigning from the board of Software Freedom International and will consider reducing and resigning some of my other commitments as well. If you want to support my work with the foundation, you can become an associate member.

Selectricity

/copyrighteous/images/selectricity_logo.png

More than a year ago, I published an election methods library called RubyVote. Interest in the library surpassed any of my expectations: I know of at least one startup using the library heavily in their core business and a number of fun sites, like Red Blue Smackdown, that are using it as well. The point of course, was to make complex but superior election methods accessible in all sorts of places where people were making decisions suboptimally. It its own small way, it seems to have succeeded enormously.

Over the last year, I’ve been asked by a variety of people if they could use RubyVote for their own organizational decision making — tasks like electing leadership of a student group or members of a non-profit board of directors. Since RubyVote was just a library without a UI of its own, I had to tell them "no." I caved in eventually and got to work on a quick and dirty web-based front end to the library.

That project grew into Selectricity which is a primarily web-based interface to a variety of different election methods and voting technologies. You can currently try out quickvotes which can be created in half a minute and voted on in a quarter but which bring all of the power of preferential voting technologies to bear on very simple decisions. Prompted by Aaron Swartz, I also built a mobile phone version that’s lets you send a short email or SMS to create or vote in a election.

For those that follow research in voting technologies, there’s not a lot of new stuff here. What’s new is that this project, unlike the vast majority of voting technologies, is interested in the state of the art for everyone but governments. Clearly government decisions are important but they’re one set of decisions, usually only once a year. Selectricity is voting machinery for everything and everyone else.

It was announced in a variety of news outlets today that Selectricity was selected for grant from mtvU and Cisco as part of their Digital Incubator project. As part of that, I’m going to be working with some other voting technology experts to bring tools for auditable elections, cryptographically secured anonymity, and voter verifiability to the platform (I have only rudimentary functionality today). There are a couple people who will be joining me on the project this summer and we will building out what I hope will be an extremely attractive platform for better every-day decision-making.

More than the grant though, I’m excited about the visibility that use by MTV will bring to the project. Most of all though, I’m just excited about more free software and more (and more accessible) democratic decision making. My adviser Chris Csikszentmihályi put it well:

One of the big arguments against preferential voting, or new voting technologies, is the fear that they would disenfranchise the average person who doesn’t yet understand how they work. Certainly, making all voting technologies open source is critical, but the issue of familiarity is worth considering. We’re hoping that MTV — and eventually American Idol — will move their voting over to Selectricity, allowing it to work as both a technical tool but also pedagogically, training future voters. Why not integrate democratic processes into all your software and communications tools? Why not use the best democratic processes available, so long as they’re available to everyone?

Overprice Tags

Last Thursday (February 15, 2007) was declared National Day of Action for Open Access. To help raise awareness of the movement for open access in scholarly publications at MIT, I got together with a number of other MIT students and placed price tags — we called them overprice tags — onto the 100 journals that MIT subscribes to at a cost of more than $5,000 USD per annum.

/copyrighteous/images/overpricetagged_journal.jpg

The project, inspired by a similar project called Seeing Red carried out by a Brown librarian a few years back, was a huge success. You can find information about the project, motivation and experience, see pictures, and find out how you might run a similar event at your institution on the Overprice Tags homepage.

A Definition of Free Cultural Works

Last year, I announced a project to bring together artists, content creators, and others who care about freedom to come up with a clear set of goals around which a social movement for essential freedoms around culture might be based. There has been a lot of discussion and a number of important changes to the document over the last year. A few days ago, we finally released "1.0" of our definition with this announcement:

A diverse group of writers has released the first version of the "Definition of Free Cultural Works." The authors have identified a minimum set of freedoms which they believe should be granted to all users of copyrighted materials. Created on a wiki with the feedback of Wikipedia users, open source hackers, artists, scientists, and lawyers, the definition lists the following core freedoms:

  • The freedom to use and perform the work
  • The freedom to study the work and apply the information
  • The freedom to redistribute copies
  • The freedom to distribute derivative works.

Inspired by the Free Software Definition and the ideals of the free software and open source movements, these conditions are meant to apply to any conceivable work. In reality, these freedoms must be granted explicitly by authors, through the use of licenses which confer them. On the website of the definition a list of these licenses can be found. Furthermore, authors are encouraged to identify their works as Free Cultural Works using a set of logos and buttons.

The definition was initiated by Benjamin Mako Hill, a Debian GNU/Linux developer, and Erik Möller, an author and long-time Wikipedia user. Wikipedia already follows similar principles to those established by the definition. Angela Beesley, Wikimedia Advisory Board Chair and co-founder of Wikia.com; Mia Garlick, general counsel of Creative Commons; and Elizabeth Stark of the Free Culture Student Movement acted as moderators, while Richard Stallman of the Free Software Foundation and Lawrence Lessig of Creative Commons provided helpful feedback.

As more and more people recognize that there are alternatives to traditional copyright, phrases like "open source," "open access," "open content," "free content," and "commons" are increasingly used. But many of these phrases are ambiguous when it comes to distinguishing works and licenses which grant all the above freedoms, and those which only confer limited rights. For example, a popular license restricts the commercial use of works, whereas the authors believe that such use must be permitted for a work to be considered Free. Instead of limiting commercial use, they recommend using a clever legal trick called "copyleft:" requiring all users of the work to make their combined and derivative works freely available.

Möller and Hill encourage authors to rethink copyright law and use one of the Free Culture Licenses to help build a genuine free and open culture.

If you haven’t yet, please check out the project at freedomdefined.org. If you’re still curious feel free to read about my motivation and why I think that everyone should stand up for what they feel are essential freedoms.

Wikimedia Foundation Advisory Board

A few days ago, the Wikimedia Foundation announced the creation of an advisory board of which I am thrilled to be a member. I’m honored to be on a board among many folks whose work has provided and example and inspiration for me and helped bring me, and my own work and activism, to where it is today.

But most of all, I’m thrilled to be able to help Wikimedia Foundation. I’ve been reasonably convinced that WMF’s projects, Wikipedia being most notable among them, are the single most important and exciting project in the world that I was not already involved in in some official capacity.

Digital Disobedience

/copyrighteous/images/steal_music_bubble.jpg

I am helping to organize and host an event called Digital Disobedience on cyberactivism and culture jamming this Friday with Harvard Free Culture. The event will explore the interplay between technology, activism, and cultural critique. Here are the details if you are local to Cambridge/Boston and would like to drop by:

Digital Disobedience
Cyberactivism and Culture Jamming
Friday, December 1, 18:00
Science Center 110, Harvard University

The event will feature talks by:

The format will be interactive with short presentations from the speakers and then break-out groups to discuss thoughts and questions with the presenters. A few people have voiced a desire to do some culture jamming of our own afterward. My birthday is the next day so maybe we can have that turn into a little bit of a celebration.

iRony RockBox Installer

In my blog post yesterday I described iRony, an install party I helped organize for iPods. In the post, I pointed folks to some resources for holding similar parties.

To help with mass installs at our party, I wrote a simple installer for RockBox in Python that would run on GNU/Linux. With a few modifications, the script could be relatively easily converted to also run on Mac OS X.

While an unofficial installer exists for Windows, my installer, simply called the iRony RockBox Installer, seems to be the first installer for GNU/Linux.

Of course, the installer is still largely rough and untested and is definitely unsupported by the RockBox team. If you get around to trying it, please send me feedback, advice, or and patches. You can grab it (and future version) here: http://mako.cc/projects/irony/

iPod Liberation!

About a month ago, I announced an iPod liberation party (i.e., an install-fest for free/open source software onto iPods). The summary, now several weeks after the fact, was that the party was a total success. More than fifty people attended and several dozens iPods were liberated. Pictures and information on the event are now online.

Over the past few weeks, I’ve been polishing a RockBox installer that I wrote for the event, writing up an article published on NewsForge today, and documenting the process for those that want to hold their own similar events.

If you are unconvinced on the subject of iPod liberation, read the NewsForge article written with others from my research group and Harvard Free Culture. Most of the rest of the information on our party and information on throwing your own party exists in sub-pages from the iPod Liberation page in the Free Culture wiki.

I’m looking forward to seeing a whole string of similar parties run by LUGs and other interested groups. It’s a great way to get out a message about software freedom, DRM and about freedom on devices other than computers.

Software Freedom Curriculum

About a year ago, I was working on OLPC during most of the time and thinking a lot about software freedom in the context of the project. My blog post on OLPC and Charges of Technological and Cultural Imperialism from last December is a great example of my thinking out loud about some of the issues.

The attractive thing to me about OLPC was the idea of students getting a real, free software, free hardware, truly open platform unlike phones, calculators, and eBooks: closed paternalist platforms that seem to be the only real alternatives. This is a goal that OLPC has not achieved yet but has already come quite close to.

People say that because modifying technology is often difficult, only a small percentage of users — especially young users — will take advantage of the malleability or "hackability" of a product. They are probably right. But part of why this happens is because when computers are employed in education, we use them as tools to accomplish predefined and preprogrammed tasks. Even when students learn to program, it’s in a window (quite literally in a box) separate from the rest of the things that the computer does.

And for someone working on a project in part so that they can spread technological freedom, this is a problem. Consider the fact that with only a small number of exceptions, the only advocates of software freedom I know are programmers or hackers. I don’t think that this is because of some "programmer’s sensibility" but rather because programmers understand a set of things about the malleability of software and the nature, effect, and context of computation that gives them perspective to understand how a concept like freedom might apply to something like software. In other words, to understand software freedom, you must first understand — really understand — what software is and what it is not, how it makes things possible and impossible, and how changing it can have important effects.

The mentality I’ve described is currently a "hacker’s sensibility" but I don’t believe that you need to be a hacker to understand why software freedom is important. Proof, I think, is the fact that people think that a free press is important even if they don’t publish or write very well.

As an exercise, I took it on myself to write the beginning of a curriculum that teachers could use to teach students about software freedom and the concepts that I think are key to understanding it. It tries to come up with models for framing discussions and a series of activities to help teachers teach relatively young (i.e., middle school students) about issues of computation, information goods, and ultimately about software freedom.

I wrote the curriculum about a year ago, showed it to a few teachers and colleagues, and then sat on it because I wasn’t sure what to do with it and because I was concerned by my own lack of experience teaching outside of Universities. I’m still not entirely sure about incredibly basic things like what form a curriculum should take for this age group.

I noticed recently that Wikiversity launched in August and it seems like the perfect place to put my curriculum for consumption by the world and for collaboration, discussion, and further development. You can see what I’ve got from this page and the pages linked from it:

http://en.wikiversity.org/wiki/Software_Freedom

The project still needs lots of work. It needs to be threshed out on its own terms and it needs to be broken down and integrated into Wikiversity as a series of learning projects, learning activities, etc. I’ve looked at the documentation around Wikiversity and I can neither understand how to do this nor find examples of large curricula in Wikiversity to which this has already been done. If you have experience on Wikiversity, your help would be welcome.

If you are interested in using part of the curriculum, I would love to hear from you and to see your edits on the wiki.

The Official Ubuntu Book

Any Day Now, The Official Ubuntu Book will show up in stores. I have a rubber-banded-together copy of the folded and gathered sheets and the the first batch of books should be bound (or being bound) right now. Those who have pre-ordered it from Amazon or elsewhere should have it in their hands quickly.

In addition to my own name on the author page is (future Ubuntu Community Manager) Jono Bacon, Corey Burger, Jonathan Jesse, and Ivan Krstić. Many more members of the Ubuntu community and many editors at Prentice Hall deserve credit as well.

I’m proud of the book. I sense that it’s more consistent, better organized, and of a higher overall quality than my last book. Even better though, is the fact that the book is released under a Creative Commons Attribution-ShareAlike license. Several chapters are already being shipped by default on the Ubuntu desktop and several translations are underway.

You can read more about the book on the publishers site and order it from any number of places online. Books under such licenses are economically risky for publishers so please support the project by buying it if you end up finding the text useful!

System.hack()

My friends Marcell and Tomislav organized a show called System.hack() that aimed to highlight many of the last half-centuries greatest "hacks" as a means of celebrating the hacks themselves while exposing them, and the idea of hacking and hackers, to a larger audience.

As part of their show, I procured an original circa-1960’s Cap’n Crunch whistle (the one that emits 2600 Hz when one hole is covered) and wrote a short essay for a book published along with the show. You’ll have to track down Tomi and Marcell in Zagreb if you want to find my whistle but you can read about the hack in either English or Croatian on the exhibit’s wiki. You should also check out the whole System.hack() wiki because there’s some other good stuff up there from other contributors.

Defining Free Content and Expression

(This is mostly reposted from an Advogato article I just submitted).

About a year ago, I posted an article on Advogato entitled, Towards a Standard of Freedom: Creative Commons and the Free Software Movement. In it, I argued that Creative Commons and the free culture movement were struggling to build a cohesive freedom movement in the way that free and open source software had succeeded in doing by never stopping to define the ground rules of the commons movement.

I argued that Free Software built a movement around calls for essential freedoms and against the actions of software producers who failed to live up to this standard. On the other hand, Creative Commons has argued for "some rights reserved" but never explained which rights were unreservable. In the process, they’ve done the invaluable service of creating a stable of powerful, internationalized licenses. But they failed to build the type social movement that some of us wanted. While this was never their goal, it left some people unsatisfied.

In a later version of the essay published in Mute Magazine, I concluded by stating:

Whether in unison or cooperating in separate groups, it is time for those those of us that feel strongly about freedom to discuss, decide, and move forward with our own free information movement built upon a standard of freedom. When we have defined free information in terms of essential freedoms, a subset of Creative Commons works and a subset of Creative Commons licenses will provide tools and texts through which a social movement can be built.

I’m thrilled to say that that day is now within sight.

A few weeks ago, Larry Lessig introduced me to Erik Möller, a Wikipedian who had read my article and was planning on launching the same project that I had been planning. It only seemed sensible to collaborate.

Today, we have launched a draft of a Free Content and Expression Definition online at freedomdefined.org. The website is a wiki and we welcome feedback, suggestions, and alternative versions of the document.

So far, we’ve have decided to stick closely to the freedoms of free software but are actively interested in updating these to be more relevant for other types of creative works. Of course, anything, even the name, can be changed at this point.

To guide us through the project of debating and further refining a definition are four moderators who will ultimately be called upon to resolve disputes and disagreements about what the definition should and will say. These moderators are myself, Erik Möller, Creative Commons General Counsel Mia Garlick, and Wikimedia Foundation Trustee Angela Beesley.

You can view the announcement of the definition, please take a look at:

To view the definition itself, please visit:

RubyVote

Authors who name their software using a one-word combination of the language the software is written in followed by a word that describes functionality are advertising their own unoriginality. Such names are slightly more acceptable when describing libraries where the language might actually matter.

Then again, I might just be trying to rationalize RubyVote. RubyVote, of course, is the very descriptive, accurate, and uninspired name of a new election methods library I’ve just written and released in on RubyForge. Here’s the short description:

An election methods and voting systems library written in Ruby. It provides a simple, consistent and well documented interface to a number of preferential, positional, and traditional election and voting methods.

Yes. Condorcet and Cloneproof-SSD are supported.

The homepage and project pages, both of which are also descriptive, accurate, and uninspired, can be found here:

The software is distributed under the GNU GPL.

No Price Is Too Much

This article from Access North Georgia’s Newsroom describes how there is a investigation in Cobb County into allegations that, "the bidding process for the 100 million dollar laptop program was slanted in favor of apple."

Making a laptop for 100 million dollar hardly seems that difficult. Some of us are more ambitious.

If you haven’t seen it, the first demo of the laptop was unveiled in Tunis and is totally green. Congratulations to everyone else who put in long days (and nights) on making this demo shine.