2009-02-26

Notes, Links, 2009-02-2

The action by the UK to promote open source published 24 February is of course terrific news and should be hailed as such. I hope it will, along with similar other European acts, stimulate the North American governments to also promote open source, open standards, and thus directly and indirectly innovation and economic growth here. Certainly, we need it. Note--the policy directive issued by the government is not a dismissal of proprietary software, and it is not a celebration of the freedoms granted by Foss. It is rather a statement about giving taxpayers the best value for their taxes:

“While we have always respected the long-held beliefs of those who think that governments should favour Open Source on principle, we have always taken the view that the main test should be what is best value for the taxpayer.

“Over the past five years many government departments have shown that Open Source can be best for the taxpayer – in our web services, in the NHS and in other vital public services.”

Why then the directive now? Because “we need to increase the pace,” as the innovation, the dialog between government users and the IT industry, needs to be allowed free rein, and not the essentially furtive and sporadic efforts that have preceded this directive--and which characterize government procurement practices elsewhere.

Yet there is good news emerging: Canada put out a Request For Information to which numerous companies replied, including Sun. (I helped draft the response, along with Bruno S.; Simon P. provided the logical frame.) And late last month, I gave a two-hour discussion on Foss and policy to the Ontario government. All of which is to say that in Canada there is movement in the right direction--a movement I fully expect to see grow. Why? proprietary software costs taxpayers money--upfront, down the road, in the end.

Of course, we all expect the usual arguments, and I’ve already noted harbingers of them: that there are hidden costs to Foss, and that these include such things as migration of documents, files, people; and also training and certification costs, and then the biggest fear of all, the by and large bogus problem of using software that may have license issues. In the case of OpenOffice.org (and probably most other significant software the government is likely to consider) that’s a false fear.

But that won’t stop some. In Microsoft’s suit against the in-car navigation device maker TomTom for patent infringement, even though the suit is ostensibly and ostentatiously not against Foss, (“Open source software is not the focal point of this action.”), the environment Foss is clearly affected. For whatever the merits of this suit (and TomTom is hardly quiescent here) this is very close to the sort of fear frightens governments and corporations away from Foss: That there is a tiger lurking in the open source commons.

It shouldn’t. But it should provoke us to ensure that our code is clean and that any code that we expect others to build on and distribute must be have an unimpeachable pedigree. And that goes for proprietary software, too. Or does anyone really think that the mélange of doubt can only apply to works licensed under Foss copyrights? So let’s speculate that the end result of this sabre rattling is ultimately to endorse a copyright regime that is characterized not by FUD but by transparency, of license and code, and backed not by market-driven entities but by responsible community organizations and companies--those that understand where innovation lies and how to promote it, so as to foster a sustainable present and future. We certainly need it.


2009-02-25

Notes 25 Feb. 2009

With some alarm I note I have not made an entry since prior to OOoCon, and that was back in November. (A brief entry on that is coming.) No excuse but work and other, distracting things. Coming at the end of the year--or close to it--and then that end of year being such a series of economic crises and political triumphs, it was easy to lose sight of the obligation to engage in conversation with the communities of which I’m a member. (I have to thank my friend Sophie G., for prompting me to write, to reveal what I’ve been doing. It’s so easy to ensconce oneself in other work, and then to persuade oneself that public relation is not necessary, as Isn’t what you are doing on the community’s behalf?)

But I have not been idle. My focus of late has been on regional efforts, in particular, Canada and the province where I live, Ontario. As well, I’ve been trying to get OpenOffice.org in more colleges and universities and--this is the more interesting point--developed more by students at those places. The key, as I’ve long believed and written on before, is to have Foss and not just OOo, become part of the curriculum, the way, say, any other (computer) language is taught, as a model, as the frame for a workspace, as a vehicle for engaging in real open source communities. But this clarifies the issue: teaching Foss, and OOo, is at least a dual effort: on the one hand, one must teach the code, and on the other, the process of open-source collaboration. For a student, the latter part is arguably the more problematic part, as school shields her from harsh scrutiny. Consider it a kind of gestational space, where all sorts of vulnerabilities can be revealed and worked on, and to expose the student then to the outside world is to betray the implied premise and promise of college.

But, as I’ve equally argued, the options are really not so Manichean: one can structure classwork to retain that membrane while also working with Foss groups. Indeed, students do this all the time, when they work in science labs and engage in actual, serious and publishable work. And in colleges such as Seneca, we see the success of a method like this applied to Foss instruction, including OOo.

I spoke on education and also another key issue, regional groups, at OOoCon, and I’ll discuss that shortly. But for now, at the end of last month I delivered a guest lecture at the newly inaugurated Digital Humanities Initiative at the University of Buffalo. The lecture was on “open source” but it was for me really an examination of the cultural and political, not to mention technological, change that has taken place more or less globally in the last year, and can be summarized as the end of the Reagan Era and the Dawn of the Obama Era, though I hesitate to credit Obama, at this point, with his weak economic policies, as branding an era. But I’ll give him benefit of a doubt. Regardless, the shift has been from an exit from neo-conservative and neo-liberal ideologies to something that is still taking shape but which, I should hope, and will certainly try to achieve, a political frame that is more just and sustainable and attends to what people are doing where they live every day. Foss is crucial here, as it diverges from neo-liberal imposition of products and the means of creating them and opens the market to those things made at home, for the home market.

It goes beyond that, however. Foss, to me, also implies a weakening of the consumer/producer dyad that over the last century has configured the way people think of themselves, their communities, their possibilities. (And the dyad has only been around for about a century, I’d guess, or since the rise of the department store and urban consumerism--in the city, you are generally if not axiomatically a consumer of goods produced elsewhere; less so on the farm--and the department store comes into being in the latter half of the 19th century, towards the end.) I went to college at Berkeley, and lived in the student co-ops, where we all had to do 5 hours of work a week to keep the system running. (Boast: I was the youngest elected USCA Board Member, at 18, and for year the worshift manager--I organized the work schedule and then told people how to do the jobs I’d assigned them: sort of like what I do now....) The Co-Op was “ours”; we were responsible for its upkeep, its clealiness, its food: no one else. This bred responsibility. It fostered ambition; it developed community skills; and it made, I honestly believe, for better citizens. (Or, at least, that was the idea; there were, as with all other Rochdale-inspired cooperatives, problems with drugs, and disruptive anarchic types. But I tend to think that had more to do with the times (late 70s) and the inexperience of framing governance, than with the idea of the cooperative itself, which I still believe in. (Incidentally, turns out that Toronto had, around the same time, the largest and most successful coop, not far from where I live now, on Bloor Street. Drugs, some violence, dissolution hit it, and it ended. Delany, in Dhalgren, got it right, when he imagined the beautifully violent apotheosis and also the end, of the 60s in Bellona, and of the 70s in Triton: isolated from the world, the centre cannot hold and things fall apart, in violence and narcissism.)

But back to the point: Foss weakens the impermeability of the membrane separating producers from consumers by giving the tools of production to every user and by making production itself not simply an obligation, a job, but an act of community building: an act of being yourself. This theme ended up being the dominant one in my lecture, and I characterized it by asserting that the era of Paris Hilton, of Bling, was dead, over with. The new era, the one figured by Obama, has yet to earn its name. But it is roughly one of sustainability and social responsibility, but equally of community. Being yourself no longer implies the market; it implies now or will, community. The difference lies in effects: as a consumer the consequences of what I do when I buy something are obscure; as a member of a community, that obscurantism is impossible, and what I do affects me, too.