Recording of Stallman on copyright
For anyone interested in Richard Stallman’s talk about copyright (in general, not just for software), here’s a recording from yesterday:
For anyone interested in Richard Stallman’s talk about copyright (in general, not just for software), here’s a recording from yesterday:
Possibly interesting links I saw yesterday.
See also: the archive of Yesterday’s links.
—
Ciarán O’Riordan,
Support free software: Join FSFE’s Fellowship
Possibly interesting links I saw yesterday.
See also: the archive of Yesterday’s Links.
—
Ciarán O’Riordan,
Support free software: Join FSFE’s Fellowship
Possibly interesting links I saw yesterday.
See also: the archive of Yesterday’s Links.
—
Ciarán O’Riordan,
Support free software: Join FSFE’s Fellowship
I recently read the discussion on the GCC development mailing list related to GCC’s transition to GPLv3. Despite generating 172 emails, the transition was quite smooth actually.
I decided to read about GCC’s transition because I wanted to investigate a (false) claim which Slashdot featured on their front page. Slashdot’s story, which I now know to be complete rubbish, claimed that key GCC developers were talking about forking GCC.
Actually, they mostly discussed version numbers, as well as the copyright status of code written by scripts, and of World War II photographs, etc.
About the version number, DJ Delorie argued against bumping the version number up to 4.3.0 for the new licence because Slashdot might print a negative story about GCC 4.3.0 not having the features previously scheduled for that version number. Which is pretty funny in hindsight because the developers finally agreed not to bump the number up to 4.3.0, and Slashdot still printed a negative story. It seems there’s no getting around the fact that Slashdot just loves controversy, even when it means creating anti-free-software FUD.
So, in review, Samba’s GPLv3 transition went well. Then SugarCRM ditched their custom licence and moved to GPLv3, which, as I said, is one way in which GPLv3 tackles licence proliferation. And now GCC and 286 other projects have made the transition, according to Palamida’s GPLv3 counter. It seems that GPLv3 transitions are going quite smoothly.
In fact, it seems that many commentators have been surprised (and some have surely been disappointed) by the lack of major problems. There is a vacuum of bad press, which is why Slashdot has resorted to printing hallucinations, and InformationWeek can only publish bad news by inventing it. All in all, I’d chalk that down as a success for the eighteen months of hard work that was the GPLv3 consultation process.
—
Ciarán O’Riordan,
Support free software: Join FSFE’s Fellowship
I have three efficiency tips. One is to tell people what your goals are, another is to maintian a todo list, and the third is to remember to eat breakfast. Obviously, I still have a lot of room for improvement, so I’m going to read Getting Things Done and see what other good tips I can find there.
It was hard to resist using the title "Getting Getting Things Done read" for this entry, but I wouldn’t want to give too much prominence to a book that can’t be freely copied. At the same time, I do what to say what my goal is – that way I have to do it. That tip got me started in the campaign against software patents. I knew nothing about the subject, so I told people I would give a talk about it at an event – then I couldn’t avoid getting that work done.
When I’ve read the book, I’ll blog about what I’ve learned. Hopefully I’ll have found some useful free software for implementing the methods in the book. Many free software packages for the book can be found on Wikipedia’s Comparison of GTD software article.
The tip about lists works for three reasons. One is they stop you from forgetting things, a second is that they remind you of more options so there will usually be something you feel like doing, and the third is that they free up your brain from trying to remember these things. Human brains stopped being for that as soon as writing became easy. So I start each day by reading yesterday’s list and making a new list with whatever I haven’t finished.
Oh, and breakfast. Without a proper breakfast, after an hour or two my concentration has deteriorated noticeably.
In the mean time, by coicidence, I got this link passed to me recently:
—
Ciarán O’Riordan,
Support free software: Join FSFE’s Fellowship
Possibly interesting links I saw yesterday.
See also: the archive of Yesterday’s Links.
—
Ciarán O’Riordan,
Support free software: Join FSFE’s Fellowship
It’s proven harder than I thought to find 4 or 5 good links per day. I’m going to keep trying, but I’ll probably expand this to include some musings too – and then find a new name for the series.
See also: the archive of Yesterday’s Links.
—
Ciarán O’Riordan,
Support free software: Join FSFE’s Fellowship
Possibly interesting links I saw yesterday (July 16th 2007).
See also: the archive of Yesterday’s Links.
—
Ciarán O’Riordan,
Support free software: Join FSFE’s Fellowship
InformationWeek have posted a follow-up article. In trying to respond to recent criticism about misrepresenting facts regarding Linus Torvalds and GPLv3, InformationWeek has managed to show exactly how incorrect their first article was.
Their misleading GPLv3 article from last week drew criticism for using false evidence to suggest that Linus is on a new anti-GPLv3 and that Linus’s insults are "the latest sign of a growing schism".
Now they’ve done something very strange. In their new article "The Linus Files, Part Two", they’ve dug up further, slightly older, insults which Linus has levelled at FSF, and they’re presenting these as some kind of proof that their first article was accurate. An attempt at a classic straw man tactic, albeit executed so poorly that it’s backfired.
By digging up older criticism, and being unable to find or provoke anything new, they’ve just shown that there is no news to report. No new phenomenon, no widening of an old rift. You could even conclude that things are calming down.
UPDATE: I added the first sentence just now because previously there was no way to find the InformationWeek article I’m debunking.
—
Ciarán O’Riordan,
Support free software: Join FSFE’s Fellowship