administrivia

Our most important statement to date is the Franklin Street Statement on Freedom and Network Services. It calls upon developers, implementors and users of network services to do a series of things to help ensure software freedom for network services.

Now we run a blog, of course, so, in that capacity, we’re one of the implementors our statement speaks to. We use Wordpress with a downloaded theme and a couple extra plugins — all of which are free and available online. We export our blog’s content using RSS and Atom under the Creative Commons Attribution ShareAlike License — a licensed approved for Free Cultural Works.

In the Franklin Street Statement, we ask implementors to choose free software for their services. We’ve done that. We ask them to release customizations under a free software license. Like most people who run blogs, we’ve not made any changes, so no action seems to be required. We don’t host any private data other than passwords. Public data on our blog is accessible via RSS and licensed freely.

So are we doing enough to comply with the statement’s guidelines? It seems so. But have we provided an ideal example? Perhaps not. We’ve argued that a free service is one that can be copied, changed and reimplemented by its users. With a little extra work from us, that could certainly be easier with regards to our service.

To work toward being a better example, I’ve put together a new page on our blog that links to local copies of source code for all the software running our blog. In building this list, I made several observations.

While I think many people running blogs would be happy to provide such information, perhaps they won’t be as motivated to take the time I did to put it together. Perhaps we need a plugin to generate such sets of links automatically. Perhaps such a plugin can go further than just RSS by providing database dumps that are automatically and appropriately cleaned of sensitive information like passwords and unpublished posts.

The process of building and auditing the list raised several important issues related to the software we use. The theme we’d been using had unclear and potentially problematic licensing status so I switched to one clearly released under the GNU GPL. It’s not clear to me what to make of the Akismet plugin which, while presumably free itself, uses a separate service and database to do spam checking. The freedom status of this system is much less clear. Now, the whole point of Akismet is build a centralized database resistant to spammers. Should we uninstall Akismet? Possibly. I’m not sure yet, but I hadn’t even considered it before I went through this process.

As more people try to implement the Franklin Street Statement, these types of questions, problems, reports, and shared solutions will help make it easier for others to comply in the future. Other’s who’ve gone through this process and have useful advice, tips, or code to share should contribute that to the Autonomo.us wiki or help write an article on this blog.