Autonomo.us and the Franklin Street Statement on Freedom and Network Services launched today.
I’ve written about the subject of this group and statement a number of times on this blog, starting with Constitutionally Open Services two years ago. I think that post holds up pretty well. Here were my tentative recommendations:
So what can be done to make the web application dominated future open source in spirit, for lack of a better term?
First, web applications should be super easy to manage (install, upgrade, customize, secure, backup) so that running your own is a real option. Applications like WordPress and MediaWiki have made large strides, especially in the installation department, but still require a lot of work and knowledge to run effectively.
There are some applications that centralizaton makes tractable or at least easier and better, e.g., web scale search, social aggregation — which basically come down to high bandwidth, low latency data transfer. Various P2P technologies (much to learn from, field wide open) can help somewhat, but the pull of centralization is very strong.
In cases were one accepts a centralized web application, should one demand that application be somehow constitutionally open? Some possible criteria:
- All source code for the running service should be published under an open source license and developer source control available for public viewing.
- All private data available for on-demand export in standard formats.
- All collaboratively created data available under an open license (e.g., one from Creative Commons), again in standard formats.
- In some cases, I am not sure how rare, the final mission of the organization running the service should be to provide the service rather than to make a financial profit, i.e., beholden to users and volunteers, not investors and employees. Maybe. Would I be less sanguine about the long term prospects of Wikipedia if it were for-profit? I don’t know of evidence for or against this feeling.
Consider all of this ignorant speculation. Yes, I’m just angling for more freedom lunches.
I was honored to participate in a summit called by the Free Software Foundation to discuss these issues March of this year, along with far greater thinkers and doers. Autonomo.us and the Franklin Street Statement (named for the FSF’s office address) are the result of continued work among the summit participants, not yet endorsed by the FSF (nor by any other organization). Essentially everything I conjectured above made it into the statement (not due to me, they are fairly obvious points, at least as of 2008, and others made them long before) with the exception of making deployment easier, which is mundane, and service governance issues, which the group did discuss, but inconclusively.
There’s much more to say about this, but for now (and likely for some time, at the rate I write, though this activity did directly inspire me to propose speaking at an upcoming P2P industry summit, which I will early next month–I’m also speaking tomorrow at BALUG and will mention autonomo.us briefly–see info on both engagements) I wanted to address two immediate and fairly obvious critiques.
“Where it is possible, they should use Free Software equivalents that run on their own computer.” This is near Luddite talk… It is almost always possible to use an app on your own comp, but it is so inefficient. Networked online apps are not inherently evil, should you back up your work
offline, yes. Should you have alternative options and data portability, yes. You should fight to impove them. But you should not avoid them like the plauge.
The statement doesn’t advocate avoiding network services–see “Where it is possible”, and most of the statement concerns how network services can be free. However, it is easy to read the sentence Rowe quoted and see Luddism. I hope that to some it instead serves as a challenge, for:
- Applications that run on your own computer can be networked, i.e., P2P.
- Your own computer does not only include your laptop and home server, but any hardware you control, and I think that should often include virtual hardware.
I see a lot about software licensing and not much about identity and privacy. I guess when all you have is the AGPL everything looks like a licensing problem.
True enough, but lots of people are working on identity and privacy. If the FSF doesn’t work on addressing the threats to freedom as in free software posed by network services, it isn’t clear who would. And I’d suggest that any success free software has in the network services world will have beneficial effects on identity and privacy for users–unless you think these are best served by identity silos and security through obscurity.
Finally, the FSF is an explicitly ideological organization (I believe mostly for the greater good), so the statement (although not yet endorsed by the FSF, I believe all participants are probably FSF members, staff, or directors) language reflect that. However, I suspect by far the most important work to be done to maintain software freedom is technical and pragmatic, for example writing P2P applications, making sharing modified source of network applications a natural part of deployment (greatly eased by the rise of distributed version control), and convincing users and service providers that it is in their interest to expect and provide free/open network services.
I suggest going on to read Evan Prodromou (the doer above) on autonomo.us and the Franklin Street Statement and Rufus Pollock on the Open Software Service Definition, which more or less says the same thing as the FSS in the language of a definition (and using the word open), coordinated to launch at the same time.
[…] I’ve mentioned several times in passing, such practices will facilitate open web applications and other network […]
[…] Google Chrome looks really interesting. Given that the web is the interesting platform, more web client innovation is welcome, especially in open source web clients (but let’s not forget the servers). […]
[…] I’m really excited that the conference will have software freedom and network services as a major focus. This will be the first public conference on the topic, following last year’s meeting from which followed the Franklin Street Declaration and Autonomo.us. […]
[…] Michael Meeks on “Risks vs. Benefits on Copyright Assignment” made the case that assignment (and some non-assingment contributor agreements) is harmful to participation, and proprietary re-licensing has not proven a good business, so a corporate sponsored software project ought to either be free (sans assignment and potential for propreitary relicensing) or proprietary, and fully enjoy the benefits of one or the other, rather than neither. He also indicated that permissive licensing can be better than copyleft for a free software project with copyrights held by a corporation, as the former gives all effectively equal rights, while the latter abets proprietary relicensing and ridiculous claims that the corporate sponsor will protect the community. Meeks repeatedly called on the FSF to abandon assingment, as for-profits disingenuously cite FSF’s practice in support of their own (FSF ED John Sullivan responded that they are getting corrections made where FSF practice is inappropriately cited and will work on explaining their practice better). Finally, Meeks requested an “ALGPL” which would require sharing of modified sources used to provide a network service, like the AGPL, but allow modifications that only link to or the equivalent ALGPL codebase to not be shared. I don’t know whether he wants GPL or LGPL behavior if such modificaitons are distributed. I was somewhat chagrined (but understanding; just not enough time, and maybe nobody submitted a decent proposal) that this was the only1 discussion of network services! […]
[…] this feature is not cost-free. But I also want to see more projects services (preferably also free and federated, but putting that issue aside) that do take the strategy of relying on public […]
[…] cloud”, the topic of the other FSF-related committee I’ve participated in, over 6 years ago, correctly implying that effort was not very influential. I hope to post an assessment and summary […]