POSS 2016, from Open Hardware to “Open divorce” (*) and formats

I enjoyed OSSPARIS 16

Last week, I presented the current status of the EU-funded research I am working on these days, that is DiDIY (Digital DIY), at the Paris Open Source Summit. I have already reported about that side of the conference on the DiDIY blog, but I found many more interesting things at POSS 2016. Continue reading POSS 2016, from Open Hardware to “Open divorce” (*) and formats

The future of ODF, XML and office suites in Public Administrations

Last week I attended the Paris Open Source Summit, were I saw things as interesting and diverse as autonomous tractors, Open Source legal support and “degooglized Internet” visions. Please read that other post to know more. Here, I am only going to describe one other moment of POSS 2016, about two other arguments I care a lot about, and on which I wouldn’t mind working again, even if these days I am mostly busy with Digital DIY. Continue reading The future of ODF, XML and office suites in Public Administrations

Pesaro, Microsoft and OpenOffice: the consequences

A few days ago I summarized the most questionable or uncertain points of the software odissey of the City of Pesaro, saying that I’d also post questions and consequences, both for the City and Open Source advocates, not mentioned yet in this story. For Pesaro, the road forward has little or nothing to do with the initial topic, that is Open Source Software in Public Administration. The advocates, instead, should rethink some of their strategies. Let’s start from Pesaro, but what follows applies to practically every city. Continue reading Pesaro, Microsoft and OpenOffice: the consequences

The correct way to use and advocate OO.o and the real reason to do it

(this is something I wrote in 2007. Everywhere you read “OO.o” you can (and should) replace it with “Apache OpenOffice or Libre Office”. See the bottom of the page for the origin and history of the text)

Many people, schools and small businesses use OO.o only because Continue reading The correct way to use and advocate OO.o and the real reason to do it