Will Stallman Kill the "Linux Revolution?"
frdmfghtr writes "The October 30 issue of Forbes Magazine has an article speculating that Richard Stallman's efforts to rewrite the GPL could threaten to 'tear it apart.' The article describes how the GPLv3 is expected to be incompatible with the GPLv2, causing trouble for Linux vendors such as Novell and Red Hat. The article wraps it up: 'And a big loser, eventually, could be Stallman himself. If he relents now, he likely would be branded a sellout by his hard-core followers, who might abandon him. If he stands his ground, customers and tech firms may suffer for a few years but ultimately could find a way to work around him. Either way, Stallman risks becoming irrelevant, a strange footnote in the history of computing: a radical hacker who went on a kamikaze mission against his own program and went down in flames, albeit after causing great turmoil for the people around him.'"
Exactly. Personally I think that Stallman is a visionary and Linus is too pragmatist in a sense, as Stallman clearly wants to avoid the DRM/"Trusted computing" trap with GPLv3 and Linus can't see medium/longterm about this. Also, he doesn't seem to be really understanding the v3, since he claimed things like digitally signed repositories like apt-get would be not allowed with v3, while Stallman clearly established that it's not the case.
I think Linus is a good coder and project manager, but we shouldn't expect him to "show the way" in issues of principle/vision. He's an engineer, not a "freedom fighter".
It takes a man to suffer ignorance and smile
Be yourself no matter what they say
And as far as any possible splinter goes, this will separate the wheat from the chaff in both directions. It may be painful, but good will come of it.
Luck favors the prepared, darling.
Here's part of the problem:
Stallman doesn't believe in compromising his ideals. His life's work is Free Software.
We can call him a weirdo, mad, an ass, but without his conviction we would all be locked into proprietary products. Unlike some things that happened because the world was ready for it (cell phones, computers), I don't believe that Free Software would exist if not for Stallman. That is, without him, I don't think another person would have dedicated his/her life to the cause.
Corporations don't compromise. Look at Microsoft's business tactics that were either outright illegal or bordering on the illegal. If they had their way we would not be allowed to write our own software, not be allowed to trade software with the original authors, not be allowed to listen to our own music. And this nightmare world is happening.
Sure, there has to be regulations, but not those imposed by corporations. Look at the radio broadcast spectrum, the automobile industry, etc.. for parallels.
So here is Richard Stallman. He's probably closer to the end of his years than to the beginning. His life's work is almost happening but Linux, for good or bad, is not at all what he envisioned. He's trying to fix it while he can. If I were in his position, I'd probably do the same thing (if only to be an ornery bastard).
Stallman is not compromising, but neither is Microsoft.
This is Forbes magazine.
The consequence of Richards vision is plenty for everyone and no capacity for hoarding, depriving, controlling and trading.
You think global warming holds a candle to something like this? He's a dangerous athiest among the flock.
-1 Uncomfortable Truth
I don't think "expand" is the right term here. "Preserve" would be much better.
Keep in mind that when GPL-2 was created there was no such thing as DMCA and software patents were a rather exotic idea. GPL-3 is the answer to new laws and aggressive interpretations of old ones.
"Global" and "Internet" are not just empty words. Combine a potential loophole (as one can use GPL source and lock down binaries with crypto key and DMCA) and millions of people and there *will* be a few unscrupulous ones that will spoil it for everybody (example: e-mail).
So, yes, we do need GPL-3, but the issue of how to deal with existing GPL-2 software is truly a hairy one.
GPLv2 contains the following language in paragraph 9:
If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation.
This provision gives the option of deciding whether to follow V2 or V3 to the person making a copy of V2 code, not to the author.
There is a serious ambiguity - if that person adds or changes some of the code, can that person convert the entire module to V3 or is the module now fragmented? And if the latter, how is anyone supposed to keep track of what statement of code is under what license?
Personally I have abandoned publishing code under the GPL - I now use the less restrictive, non-viral MIT/BSD style licenses.
There is another situation that few have discussed - The rules of copyright in the US are defined by statutes enacted by, and changable by, Congress.
There is a chance that Congress could amend the US copyright law to deny the right of enforcement to anyone who has made only a partial or small contribution to the totality of the work or if that contribution has been subject to several intervening layers of further contributions. (It would be a bear to define these things, but the Congress critters would be getting a lot of help from the IP and non GPL software industry.)
Let's see:
Ten commandments?
I'm not religious, but...
"Thou shalt not murder"
Is pretty clear to me. Although apparently it wasn't to Christianity. Then again this wasn't an issue of not being clear rather than the people this is and was addressed to, putting their fingers in their ears and singing "LA LA LA LA LA LA I can't hear you LA LA LA!!"...
There are two rules for success:
1. Never tell everything you know.
So you have a law phrased in several different ways so that everyone understands... what do you do if there is ambiguity between phrasings?
a ctions.html ), since language is just an abstract way of communicating our thoughts.
Nothing's ever going to be perfect and eternal. Things and language are changing all the time, and there's always going to be something that somebody never thought of. You can keep adding words and sentences and specifics until your face turns blue, but the law will still have uncharted territory - maybe not today, but eventually.
The nature of this conversation reminds me of The Law of Leaky Abstractions ( http://www.joelonsoftware.com/articles/LeakyAbstr
Think of it this way: Was the Windows API perfect when Windows 3.1 hit the shelves? No. They've added functions and parameters, which most likely were not needed at the time of its original creation.
Buckle your ROFL belt, we're in for some LOLs.