“Lance!”

On probably a dozen occasions, I’ve had people in cars taunt me by yelling some version of "Lance!", "Hey Lance!" or "Go Lance!" at me while I am riding my bike. It seems to be particularly likely if I’m wearing spandex.

Indeed, the "verb" to Lance has an Urban Dictionary entry and there is a Facebook group for Yelling "Hey Lance!" when you see someone riding their bike.

My friend Seth pointed out — after we were (collectively?) called "Lance" in California — that it’s pretty strange to insult somebody by comparing them to a man who is nearly guaranteed to be on any list of greatest living athletes, in any sport.

Center for Future Names of Media Lab Centers

A few years ago, the MIT Media Lab, working with the Comparative Media Studies program at MIT, created the Center for Future Civic Media. It’s a great project and one I’ve been involved in since the beginning.

Not too long after, the lab announced the Center for Future Banking through a partnership with Bank of America. One couldn’t help but notice the similarity between the names. The meme became further entrenched when, not too long after, the lab announced the Center for Future Storytelling in collaboration with Plymouth Rock Studios.

But perhaps the very first in the pattern is the the Okawa Center for Future Children announced in 1998 as a way of bringing together and supporting the labs work with kids. And no, it has nothing to do with zygotes.

Upcoming Travel

As is becoming my custom, I’m planning to spend much of December and January on the road. This time I’ll be in Seattle, Japan and Wellington, New Zealand. Here’s the rough schedule:

  • December 18-28: Seattle
  • December 28-January 2: Tokyo
  • January 2-14: Traveling in Japan
  • January 15-17: Boston to compete in the MIT Mystery Hunt
  • January 19-24: Wellington, New Zealand to give a talk at LCA

Mika will also be around for everything but the NZ leg and SJ seems likely to make an appearance in Japan during the first week of January.

Feel free to get in contact if you’d like to meet up in any of the places above for a coffee or beer. I’m also open to hanging out with giving talks at LUGs, GLUGs, Wikipedia groups, free culture groups, colleges or Universities along the way. Most of my time in Japan is still basically unstructured so I’m quite open to suggestions during the first couple weeks of January.

Zimmermanhosen Confessions

Between second and seventh grade, I went to a school that required that I wear grey corduroys. Every day. I loathed them. When I left that school, at twelve years old, I swore to myself that I would never wear a pair of corduroys again.

And I kept that vow until earlier this year when, in Germany, I came across a couple carpenters in Germany on their one-year traveling post-apprenticeship waltz. As it turns out, journeyman German carpenters wear some pretty wild bellbottom corduroys — zimmermanhosen. Although I tried, I couldn’t resist acquiring a pair at a local work clothing store.

http://farm4.static.flickr.com/3306/3519720780_bb9ca7f3c5.jpg

A year and a couple more trips to Germany later, I now own several pair of zimmermanhosen and wear them nearly every day. They are tough, distinctive, and have pretty awesome double-zipper flies. And although I love them, I still feel a little conflicted every time I put them on.

A. Dehqan, man of inquiry

Due entirely to the efforts of one inquisitive and indefatigable A. Dehqan, a web search for the phrase "In The Name Of God The compassionate merciful" now almost exclusively turns up hits to a wide variety of free software mailing lists, forums, and IRC channels with questions on everything from what is a kernel (in a minimum of half a line, no less), to how to send a FAX, to the intersection between Islam and copyright and much more! I’ve now run across him in five distinct projects. Maybe you have too!

Wikireaders

My friend Sean from OpenMoko recently gave me one of OM’s new WikiReaders. It’s essentially a touchscreen-based device dedicated to displaying Wikipedia articles offline.

And while I’ll never forgive the thing for not having an Edit button, I’ve got to admit the device is pretty cool. Not only does it make it possible to bring WP to a bunch of places that are otherwise impossible or impractical, the thing is built entirely with free software. One of my colleagues at the Center for Future Civic Media suggested we should put one in every bar to help settle drunken arguments. Think of the lives we might save!

I hope the device becomes successful but I’m worried about what success will mean for the already indefensibly large gap between the number of readers and editors on Wikipedia. After all, the ability to change and contribute is the thing that makes Wikipedia interesting, empowering, and successful; cutting this functionality out kind of misses much of the point.

I think it is important to start implementing a simple method to allow users of these types of devices to contribute back. Over the last few years, Sj and I have talked repeatedly about a simple method for contributing back from offline devices that would even be possible from devices like the Om Wikireader where editing the articles is probably impractical. Perhaps the device could be extended so that people could write short comments about articles from their reader — there’s an on screen keyboard after all — which could be saved to a log on the SD card. When the data on the card is updated, messages from this log could be uploaded somewhere — perhaps the talk pages of the articles in question or some dedicated page or ticketing queue. Editors could help merge these changes back into the articles.

Mr. Postman

The mailbox in my building is broken. Nobody can remember it being any other way. The lock is busted so anyone in the building can get access to every apartment’s individual boxes in the same way that the mailman does. It’s not a huge problem since there are only four apartments in the building and the box is behind a locked door to the street.

I saw the mailman come one day to deliver mail. He used a key to unlock a box on the outside of the building from which he retrieved a key to first unlock the outside door and then another to "unlock" the mailbox.

Every day, my mailman unlocks a mailbox that is always unlocked and, in fact, unlockable. As far as I can tell, he’s been doing it for years. I don’t have the heart to tell him the truth.

Updating the Ubuntu Code of Conduct

The Ubuntu Code of Conduct is one of the most surprisingly successful projects I’ve ever had the privilege of working on. On my first day working for the company that would become Canonical, I talked with Mark Shuttleworth about some ideas for community governance. Partially in reaction to some harsh behavior in other free software projects we’d worked on, Mark and I agreed that some sort of explicit standard for behavior in Ubuntu would be a good thing. Over lunch of what was my literally first day working on Ubuntu, I wrote a draft of code of conduct that was essentially the version that Ubuntu has used until today. Shuttleworth made a series of modification to my draft but I don’t think either of us took it too seriously. We figured it would be easy to update it later.

Over time, that code has become a central piece of the Ubuntu community. Every new Ubuntu member cryptographically signs the code. When conversation in any Ubuntu forums, channels, or lists becomes disrespectful, users almost instinctively remind each other of the code. Through this process, the code has become a sort of constitution of our community and a widely enforced standard. People treat the code as a reflection of what "ubuntu" — both the concept and our project — stands for.

Over time, the original code has spawned a Leadership Code of Conduct (which I also worked to draft), and has been modified and employed by scores of free software projects and by many projects that have nothing to do with free software at all. This is all wonderful, but a side effect has been that updating the code has become a more a difficult process that we originally imagined.

Despite it success, the code remains a text written in an afternoon in Mark’s flat. At times, this fact shows. For example, the code contains some off-hand humor that now seems a little akward and the text was a bit too developer centric at points. And there was a lot that, quite simply, we would have done better if we had realized that the code would be so important. So this summer, Daniel Holbach and I spent another afternoon in Berlin discussing and crafting a new version of the code along with a detailed rationale document that describes all the things we’d changed and why.

We believe that what we’ve created is fully in the spirit of the original code. We’ve made efforts to minimize the delta in terms of text as possible. Daniel and I realize that changing the code out from under our community is a dangerous game, and we’ve make exceptional efforts to make sure that the new code doesn’t say anything substantively different than the old code — but that it does say it better.

So I’m thrilled that, after being posted since early June and after incorporating a series of revisions with members of the Ubuntu Community Council, the new draft was approved at a council meeting earlier today.

Of course, we are continuing to think about how we might improve the text going forward. One important goal we’ve thrown around, for example, is the creation of a code that is no longer Ubuntu specific and that can be employed by a wide range of different groups and different free and open source software projects.

The Computer in My Pocket

An updated version of this article was published in the FSF‘s Fall 2009 members’ bulletin. Additionally, the article was translated into Spanish by Carolina Flores Hine.

If we’ve kept up with projections, by the end of this year, the world will be home to 3 billion mobile phones. That’s nearly one phone for every other living human being. Although these phones open up a world of important new opportunities in communication, creativity, and cooperation — and it’s important not to understate this fact — they also represent a step toward a sort of technological dystopia not unlike Stallman’s Right To Read. Phones represent one of the most locked-down, proprietary, and generally unfree technologies in wide distribution. The implications for software freedom and technological empowerment are dire.

But despite the fact that mobile phones represent what may be the greatest threat to software freedom today, the free software community has — with a number of notable exceptions that I want to both thank and draw increased attention to — been mostly silent on the issue.

I know passionate advocates of software freedom who work tirelessly to rid themselves and the world of a handful of binary blobs in the Linux kernel — important work that we all benefit from. And yet, even some of these "hardliners" don’t seem to hold their phones to their same standards as their laptops. Ubuntu’s decision to ship a new binary driver remains more controversial than the fact that the vast majority of the world’s computer using population knows nothing other than phone-based computers that remain almost unthinkably unfree and which remain almost entirely unfreeable when compared to personal computers. For most of the world’s computer users’, there is no option of, and essentially no hope for, freedom on their current devices.

It shocks me that anyone, especially free software advocates, would happily put up with such non-free computers.[1] I think part of the reason lies in the fact that most users of mobile phones, and even most phone users that care about software freedom and technological autonomy, don’t think of their phones as computers. Thinking that our phones as computers will not solve any of the problems I’ve alluded to. But doing so remains an essential first step toward any solution. Although we must still work to build viable, widely accessible, and compelling free phones, we must first convince both users and developers that this is an important goal. Reminding people that our phones, both free and non-free, are powerful general-purpose computers remains an important and still largely unfufilled part of this process.

We must find ways to remind ourselves and others of the fact that modern phones are powerful computers with powerful interfaces that are useful for a unimaginable variety of arbitrary applications. We must focus on the fact that these computers have microphones, sensors, and other sensors and that we trust them with our closest secrets and most sensitive data. We must not forget that, in almost all cases, these computers remain controlled, completely and ultimately, by companies that very few of us trust at all.

I’m not sure how we will accomplish this task. But more of us need to think long, hard, and creatively about this problem. I’ll be calling my phone "my computer" as a first, very personal, step. I have done this over the last week and it has led to some conversations with slightly confused acquaintances. Of course, this doesn’t make my phone any less free. But it does mean I’m talking more about the non-freeness most of us have put up with too silently. At this stage, that seems like progress.

[1] Like many free software advocates, my phone is also a computer running a combination of free and non-free software. I use it unhappily and am doing what I can to change this.

Long Bike Rides

On recent weekends, I’ve been going on long bike rides.

I like to keep going until the people I meet no longer know exactly where the place I left from is. The fact that one place is outside another place’s inhabitant’s mental map seems like a good sign that two places are far enough away from each other.

San Francisco

This last week, I gave a couple talks at OSCON including a fun talk on Antifeatures I hope to give a few in some form a more times in the next year.

After a weekend bike tour, the plan is to stick around San Francisco for another week. If you are around and want to get together to talk wikis, free software, or free culture, to have a keysigning, or to share a drink, please don’t hesitate to get in contact.