Introducing Between the Bars

I’ve been working with Charlie DeTar and the Center for Future Civic Media on a project called Between the Bars which is a blogging platform for prisoners. The current platform is essentially a snail-mail to web gateway: prisoners send letters which semi-automatically scanned and posted to the site; comments are printed and mailed back.

As we plan the launch of the project, we are trying to talk to as many stakeholders as possible — this includes ex-prisoners, families and friends of people who are or have been in prison, non-profits working with prisoners, victims of people in prison, people who work in prisons or in corrections, probation officers, or almost anyone else with a perspective or set of experience that might help us understand the difficult space our project is trying to negotiate and who might be able to help influence the design. At the moment, we’re not talking to current prisoners due to rules regulating research involving prisoners, but almost anyone else would be someone we’d love to connect with. We’re interested in hearing from people about their experience with prisons or prisoners, about staying connected to families and friends while behind bars, and, ultimately, about how we might design, deploy, and support technology to help folks out.

If you or someone you know are stakeholders and would be willing to talk about your experience and opinions with prisons, communication, and technology, please drop us a line at betweenthebars@mit.edu.

Meta-Microblogging

So I don’t tweet because I’m not ready to hand my data and autonomy over to Twitter. Luckily — or unluckily perhaps — that hasn’t kept me off the microblogging wagon. I "dent" semi-regularly over at freedom-friendly identi.ca.

I’ve found that microblogging is a great public outlet where one can talk about all those otherwise little meaningless things that we all do in our daily lives. High on my list of meaningless little actions, however, is microblogging itself! But can you microblog about your microblogging — i.e. can you "metamicroblog" (or "metadent", or "metatweet")? I created a new account, metamako that over the last month or so, has been proving that you sure can!

Ubuntu Books

/copyrighteous/images/ubuntu_books_2009.png

As I am attempting to focus on writing projects that are more scholarly and academic on the one hand (i.e., work for my day job at MIT) and more geared toward communicating free software principles toward wider audiences on the other (e.g., Revealing Errors), I have little choice but to back away from technical writing.

However, this last month has seen the culmination of a bunch of work that I’ve done previously: two book projects that have been ongoing for the last couple years or more have finally hit the shelves!

The first is the fourth edition (!) of the bestselling Official Ubuntu Book. Much to my happiness, the book continues to do extremely well and continues to receive solid reviews. This edition brings the book up to date for Jaunty/9.04 and adds a few pieces here and there. Although I was less active in this update than I have been in the past, Corey Burger continued his great work and Matthew Helmke of Ubuntu Forums fame stepped up to take a leading role. As I plan to retreat into a more purely advisory role for the next edition of this book, I’m thrilled to know that the project will remain in such capable hands. I’m also thrilled that this edition of the book, like all previous editions, is released as a free cultural work under CC BY-SA

For years, I have heard people say that although they like the Official Ubuntu Book, it was a little too focused on desktops and on beginners for their tastes. The newly released Official Ubuntu Server Book is designed to address those concerns by providing an expanded guide to more "advanced" topics and is targeted at system administrators trying to get to know Ubuntu. Kyle Rankin planned and produced most of this book but I was thrilled to help poke it in places, chime in during the planning process, and to contribute a few chapters. Kyle is a knowledgeable sysadmin and has done wonderful job with the book. I only wish I could take more credit. The publisher has promised me that, at the very least, my chapters will be distributed under CC BY-SA.

Many barriers to the adoption of free software are technical and a good book can, and often does, make a big difference. I enjoy being able to help address that problem. I also truly enjoy technical writing. I find it satisfying to share something I know well with others and it is great to know that I’ve helped someone with their problems. I’ll assure I’ll be able to do things here and there, I’ll miss technical writing as I attempt "cut back."

AttachCheck Revved

I finally got around to pushing out a new version of AttachCheck — a trivial little program I wrote several years ago that tries to prevent people from having to send followup emails with subjects that include phrases like, "REALLY attached this time," by asking you for confirmation when you send an email that says you’ve attached something when it looks like you haven’t.

The release fixes a single bug that affected a few users — thanks to Iain Murray who sent the patch in and apologies to him and others for taking a while to push it out.

There’s very little to AttachCheck and, if I remember correctly, it was the very first program I wrote in Python. I’m only mentioning this revision because it’s been quite a few years since I last mentioned the program and, while the script doesn’t do much, it continues to save me a little embarrassment and effort every other week or so.

Wikimedia and GFDL 1.3

I spent more time than I would like to admit massaging the process that ultimately led to the release of the the GNU Free Documentation License 1.3 (GFDL) by the Free Software Foundation (FSF). Hours counted, it was probably one of my biggest personal projects this year.

The effect is to allow wikis under the GFDL to migrate to the Creative Commons BY-SA license or, as Wikimedia’s Erik Möller has proposed, to some sort of dual-license arrangement.

There are many reasons for this change but the most important is that the move reduces very real barriers to collaboration between wikis and free culture projects due to license compatibility. BY-SA has become the GPL of the free culture world and Wikimedia wikis were basically locked out from sharing with a larger community, and vice-versa; projects will no longer have to choose between sharing with Wikipedia and sharing with essentially everyone else. The GFDL has done a wonderful job of helping get Wikimedia projects to where they are today and Möller’s proposed switch seems, in my opinion, the best option to continue that work going forward.

The FSF gets a lot of credit (and a lot of flack) for what it does. Offering to "let go" of Wikipedia — without question the crown jewel of the free culture world — represents a real relinquishing of a type of political control and power for the FSF. Doing so was not done lightly. But giving communities the choice to increase compatibility and collaboration by switching to a fundamentally similar license was and is, in my opinion, the right thing to do.

Everyone who has worked hard to make this happen deserves the free culture movement’s thanks. This list includes Richard Stallman, Brett Smith and Peter Brown of the FSF; James Vasile and Eben Moglen of the SFLC; Erik Möller, Mike Godwin and Shunling Chen of the Wikimedia Foundation.

The FSF in general, and RMS in particular, deserves a huge amount of credit for what it has decided to not do in this case and for giving up control in a way that was responsible and accountable to its principles and to GFDL authors and in the interest of free culture movement more generally. It has not been easy or quick. If you support or appreciate work like this, please support the FSF and express this while doing so. Doing so is an important way to support these essential and almost inherently underappreciated efforts.

Eric von Hippel

For those that are curious as to I’ve been up to recently, you might be interested to read this portrait of Eric von Hippel on Linux.com. The article mentions that I’m currently studying with von Hippel in my own effort to try to help build a more evidence-based understanding of how free software works and explore some of the ways I might help it work better.

Punditry

On the morning after the final US presidential debate that happened a week ago, I was invited onto the excellent new WNYC morning show The Takeaway — syndicated by Public Radio International. One of the hosts, John Hockenberry, was in Boston to tape that edition of the show.

I was on to talk about Selectricity and some of other ways that we might use election technologies. I was on and off (mostly off) air for the whole second hour (7:00-8:00 AM) of taping and had a bit of a segment just into the second half of the hour. You can check out the website or download the podcast.

Although it’s definitely not as fun to listen to as my a last gig on public radio, it’s certainly more consequential. The role of the techno-pundit was also — unfortunately? — easier for me to fill.

What I’m Up To

It’s been a year or so since I last reported what I was up to in my "day job." The last year has been a productive, if sometimes schizophrenic, period.

I’ve had a good time working with Eric von Hippel (innovation and free and open source software research guru) and have decided I’d like to do a bit more of that.

So I’m taking classes again — mostly sociological methods courses — to try to learn a bit about becoming a social scientist. To do so, I’ve enrolled in the Technology, Innovation and Entrepreneurship PhD program at the MIT Sloan School of Management and am working on putting together an interdisciplinary — probably even interdepartmental — research program. My basic research questions remain the ones that have motivated all my work: How can I get a better understanding of communities producing free stuff? How can I help those communities do so more effectively?

MIT has a large number of people who share these goals and interests. Who knows, if I can put together enough of them and an academically rigorous research proposal that will provide a real benefit to the free software and free culture communities I care about, I might even manage to get a degree out of it!

I’ll also be staying on as a fellow at the MIT Center for Future Civic Media where I’ll continue to maintain and expand Selectricity, work on Revealing Errors, and more.

Free Software Project Management HOWTO

I took a little time today to make a new release of the Free Software Project Management HOWTO. Nearly eight years after I wrote it, much of the document is out of date or has been replaced with better, more comprehensive write-ups. In particular, I think Karl Fogel’s book, Producing Open Source Software says everything insightful I say in the HOWTO, a whole lot clearly — plus adds a lot I missed.

That said, my HOWTO is short and is apparently still useful to folks. I updated it to include links to a new German translation courtesy to Robert F. Schmitt, to fix a bunch of links that time broke, and to address a few obvious mistakes that readers have pointed out.

Thinking about the documents’ future, I’m happy to release it under Creative Commons BY-SA in addition to GFDL and would love to help out on a wiki book project to merge a few of related efforts into a comprehensive wiki reference work.

Vaporizer

Nothing is more embarrassing than a website announcing that something will happen on a particular date — e.g., a product will be released, a feature will be turned on — after the date has come and gone! Even worse, putting things off repeatedly can be a lot of work!

To help such people, I just did a very quick 10 minute hack I’m calling The Vaporizer. It looks like just a date on a webpage. However, if the date originally listed has come and gone, a little bit of Javascript will change the site so that it shows tomorrow’s date instead. Vaporware providers of all types can use it to safely (and effortlessly) put things off without worrying about looking overdue!

I have seen the future, and the future is tomorrow.

Making Wiki Images More Wiki

One thing that has always annoyed me about most wiki is the way they handle images. MediaWiki, like most wikis, allows users to upload images and embed pictures. However, if you want to change an image, you need to download the file, open it up in GIMP, Inkscape, or Photoshop, edit it, save it, and re-upload it. Somewhere in this long process, the ease of editing that makes wikis so wonderful gets lost. Basically, I’m annoyed because images in wikis aren’t very "wiki."

I had a talk with Brianna Laugher at Wikimania about ways to make it easier to folks to edit pictures from within the browser — even if it is only simple stuff. Yesterday I took the afternoon to write a new MediaWiki extension which gives a working example of in-browser image editing. It provides the ability to crop images using David Spurr’s wonderful Javascript cropping user interface and uses ImageMagick to do the actual image manipulation.

It is in the form of an extension to Mediawiki I’ve called EditImage. It’s an afternoon hack from an under-qualified PHP hacker so it’s nothing special. You can read it about on its page in the Mediawiki wiki and you can try it out on my personal wiki where I have it installed.

I’m certainly not the first person to think about doing this. In fact, some old pages in the MediaWiki wiki imply that I’m not even the first person to play around with the idea of using Spurr’s code to do image cropping for MediaWiki. Hopefully though, my code can act as a nice first step and a framework for folks wanting to add additional image manipulation features. For example, I think it would be quick to add the ability to do in-browser brightness and contrast manipulation and I would love to see this in a future version of the extension.

Revealing Errors OSCON Keynote

When I gave a Revealing Errors talk at Lug Radio Live USA, I had the misfortune of being up against Robert Love’s talk on Android which many people at the conference wanted to see — myself included! One person who showed up to my talk anyway was Allison Randall. She was apparently entertained enough to invite me to give a short version of the talk as one of the keynote presentations at OSCON 2008!

In the talk, I covered the ideas behind my Revealing Errors project and quickly walked through a few examples that showcase what I’m trying to do. I’m happy with the result: a couple thousand people showed up for the talk despite the fact that it was at 8:45 AM after the biggest "party night" of the conference!

For those that missed it for whatever reason, you can watch a video recording that O’Reilly made and that I’ve embedded below.

A larger version of the Flash video as well as a QuickTime version is over on blip.tv and I’ve created an OGG Theora version for all my freedom loving readers.

Autonomo.us and the Franklin Street Statement

Recently, I’ve been doing a lot of thinking — and a bit of talking — about what software freedom means in the context of network services. I gave a talk on this subject at the most recent FSF members meeting and at Sun’s Community One. In a few days, I’ll be giving another at Wikimania in Alexandria, Egypt.

A few months ago, I worked with the FSF to organize a meeting of free software hackers and scholars to talk about the issues. Today, that group is announcing the first two concrete results of that project.

The first is a blog and a wiki called autonomo.us. The project aims to provide a space to continue, expand, and open up the work that was done at the FSF in March. Our aim is to explore the implications and responses to network services in relation to software. We’re going to do that by continuing to take notes in the wiki and by publishing articles, essays, and documents that help inform the discussion about software freedom and network policies. We will be working independently from, but closely with, the Free Software Foundation, and with others in the free and open source software communities. Our goal is not to set policy, but to explore the space and inform the discussion about autonomy and user freedom in cloud computing and software as a service.

The second announcement is the first concrete product of autonomo.us’s work: a statement we’re calling the Franklin Street Statement on Freedom and Network Services. It lays out our initial consensus on positive steps that developers, service providers, and users can take.

If you want to follow our work, please subscribe to the autonomo.us blog and check out some of our work so far. If you’ve got thoughts and things to contribute, you can mail or get to work in our wiki. You can read our about page for more information about us and our goals.

In a coordinated move, the Open Knowledge Foundation (which I help advise) is launching the 1.0 version of their Open Software Service Definition.

There is a whole lot we need to learn, think through, and do before we have reasonable answers to the problems to freedom posed by network services. Today marks the beginning of several wonderful steps toward some of these answers.

Ubuntu Book Third Edition

Another year has past and another edition of the Official Ubuntu Book has been finished and will be released soon. Over the last two years, the two previous editions of the book have grown along-side Ubuntu. The book has continued to sell very well, received almost universally favorable reviews, and been translated into more than half a dozen languages

While Jono Bacon has mostly been pulled into other projects, Corey Burger stepped up to help play the major supporting role in this version of the book’s production. The whole text was updated to reflect changes in Ubuntu over the last year including a major rewrite of the chapter on Kubuntu and important work on the Edubuntu chapter. If you use either, you’ll understand that there’s plenty of churn to report.

In a sort of experiment, Barnes and Noble will also be selling a custom edition with an extra chapter by Matthew Helmke on the Ubuntu Forums which I hope to include in the next edition of the book. It’s an excellent introduction to the best support resource Ubuntu has to offer that I hope many beginners — the group that always been the book’s audience — will find useful.

You can pre-order the custom edition from B&N or get the book from Amazon or many other sources.

Like all previous editions, the book is licensed under the Creative Commons Attribution ShareAlike license and soft-copies should be up on the publisher’s website once the book is released. Please support commercial free culture publishing by buying a copy if you find the book useful.