2013-09-17
City of Munich throws Ubuntu lifeline to Windows XP holdouts • The Register
City of Munich throws Ubuntu lifeline to Windows XP holdouts • The Register
I assume that the lucky City of Munich workers will also get LibreOffice as part of the deal?
I assume that the lucky City of Munich workers will also get LibreOffice as part of the deal?
2013-09-11
SUSE Partners with Collabora to Deliver Commercial LibreOffice Support | SUSE
SUSE Partners with Collabora to Deliver Commercial LibreOffice Support | SUSE
Basically, SUSE has ceded development to others, if any, on LibreOffice. And also calling it a "community" effort--often, if not necessarily in this case--a code term for something thrown under the bus does not inspire confidence in LibreOffice.
Of course, as a champion of AOO, I *would* see it this way. But I also feel that though the desktop will be with us for at least the next generation, that at the same time we are moving to mobile alternatives, and, as far as I know, that means a more agile, lightfooted alternative than AOO or LibreOffice can offer. For it has to work well on the tablet.
Basically, SUSE has ceded development to others, if any, on LibreOffice. And also calling it a "community" effort--often, if not necessarily in this case--a code term for something thrown under the bus does not inspire confidence in LibreOffice.
Of course, as a champion of AOO, I *would* see it this way. But I also feel that though the desktop will be with us for at least the next generation, that at the same time we are moving to mobile alternatives, and, as far as I know, that means a more agile, lightfooted alternative than AOO or LibreOffice can offer. For it has to work well on the tablet.
2013-08-24
Daily Kos: New community guidelines, final draft
Daily Kos: New community guidelines, final draft
Those of us who've been involved and even led communities, online or not, end up devising simple guidelines to guide behaviour. Most of us try to keep it simple and trust that if the community "needs" a bureaucratic codification that goes on and on then it probably needs a reassessment. What we have in mind by having any guideline is to ensure that the environment of communication stays friendly and, ideally, productive; that it is not a space where hostility is at all countenanced or tolerated and that people contribute because they like the whole process and also trust it as an institution. Certainly that idea, of insisting that discourse be friendly and open to all, and inclusive and stay civil and not veer into misogyny or racism or other forms of obnoxious rudeness determined the guidelines and policies I had a part in writing for OpenOffice.org.
These guidelines I link to by Daily Kos are of interest if only because Daily Kos is such a public site and not an open source site. But as with open source environments, where harshness and (misinterpreted or not) irony is always a possibility, maintaining productive civility is hard. Hence these guidelines.
Speculatively, it would be interesting to look at the other big, public sites, like Reddit, or even Twitter, to track the elements that are permitted or not and how they may differ around the world.
Those of us who've been involved and even led communities, online or not, end up devising simple guidelines to guide behaviour. Most of us try to keep it simple and trust that if the community "needs" a bureaucratic codification that goes on and on then it probably needs a reassessment. What we have in mind by having any guideline is to ensure that the environment of communication stays friendly and, ideally, productive; that it is not a space where hostility is at all countenanced or tolerated and that people contribute because they like the whole process and also trust it as an institution. Certainly that idea, of insisting that discourse be friendly and open to all, and inclusive and stay civil and not veer into misogyny or racism or other forms of obnoxious rudeness determined the guidelines and policies I had a part in writing for OpenOffice.org.
These guidelines I link to by Daily Kos are of interest if only because Daily Kos is such a public site and not an open source site. But as with open source environments, where harshness and (misinterpreted or not) irony is always a possibility, maintaining productive civility is hard. Hence these guidelines.
Speculatively, it would be interesting to look at the other big, public sites, like Reddit, or even Twitter, to track the elements that are permitted or not and how they may differ around the world.
2013-08-20
LibreOffice Development Howto | Lanedo GmbH
LibreOffice Development Howto | Lanedo GmbH
This is interesting and useful. Of course, I follow and help out--though much less now--Apache OpenOffice development, for any number of reasons; and I advocate the finished code, too, over all others. But it's always worthwhile to learn about forks and similars, and to remind not just oneself but others that there is usually more that binds than severs.
This is interesting and useful. Of course, I follow and help out--though much less now--Apache OpenOffice development, for any number of reasons; and I advocate the finished code, too, over all others. But it's always worthwhile to learn about forks and similars, and to remind not just oneself but others that there is usually more that binds than severs.
Subscribe to:
Posts (Atom)