[wp-hackers] WordPress and GPLv3
computerguru at neosmart.net
Wed Dec 26 18:35:54 GMT 2007
You know, I started to reply earlier, and my sentence (and I quote) is
almost the same as your opening statement :)
"The problem with GPL v3 is that it gives extra rights to users, but in
exchange puts additional burdens on developers."
Like you said - that's all the problem now. When I write open source code,
I'm choosing more and more to steer away from GPL because I find it makes
life harder for me as a developer rather than easier.
Look at most linux distros - in an attempt to protect the "integrity" of
open source, you can't distribute open source with free source (in FSF's
*INTERPRETATION* of the GPL and not the word of the GPL) so Linux distros
force users to manually "unlock" drivers and codecs which is one of the
biggest things that newbies don't understand: "Why doesn't it work out of
Sure, it preserves the code - but in doing so, it places additional burdens
and restrictions on the _developer_ instead, which is just bull.
GPLv2 had the huge distinction between "the letter of" and "the spirit of"
the GPL - but for those of us developers disinclined to follow the FSF's
developer-limiting spirit, we could still take advantage of the GPLv2 as a
license that protects both our rights as developers AND our user's freedoms.
With the GPLv3, the FSF tried to do away with the separation between letter
and spirit - which was a wholly unnecessary and totalitarian move.
Basically: GPLv2 gives developers more freedom _and doesn't start off with
the assumption that all developers are evil, greedy bastards who just want
to take GPL'd code and make money off of it_ whereas the GPLv3 limits
developer's rights and makes that ridiculous assumption.
There is nothing to be gained by moving from GPLv2 to GPLv3 except trading
the right to interpret open source in the way that best suites the community
in exchange for the FSF's interpretation of those rights.
I have yet to see a compelling argument to get developers to switch TO the
GPLv3 - and when you say it'll make your code fully compatible with people
already using the GPLv3; well, perhaps they should consider switching back
to v2 and saving face.
From: wp-hackers-bounces at lists.automattic.com
[mailto:wp-hackers-bounces at lists.automattic.com] On Behalf Of Otto
Sent: Wednesday, December 26, 2007 6:36 PM
To: wp-hackers at lists.automattic.com
Subject: Re: [wp-hackers] WordPress and GPLv3
On 12/25/07, Andy Skelton <skeltoac at gmail.com> wrote:
> Could you substantiate this for the benefit of those of us who have
> not the same knowledge that you possess? I'm trying to form an opinion
> and I want to understand your disdain for GPLv3.
My disdain for the GPLv3 is that it attempts to solve problems which
do not exist, and in so doing, it puts the freedoms of the users above
the freedoms of the developers, who are also users, but ones that they
Consider the so-called problem of so-called "Tivoization". If you
don't know the background here, I'll explain it. Tivo boxes use a
modified copy of the Linux kernel. Tivo followed the GPL to the letter
and released all their code changes ( http://www.tivo.com/linux/ ).
However, after the Tivo hacking started, they modified the code in
their actual hardware to check for a signature on the copy of the
kernel before booting it. This was to protect them and their service,
they didn't want people hacking the boxes in ways such that they did
not require the Tivo service. In other words, Tivo boxes can only run
kernels actually signed by Tivo.
Somehow this offended Stallman and the FSF. They think that the user
should be free to modify the code on the purchased hardware, despite
the fact that the hardware is not actually end-user modifiable by
normal people (just hackers) and also despite the fact that Tivo was
selling the boxes at a loss.
And that is Tivoization. Wrapping the code into a black box that can't
What Stallman and crew are failing to see is that there's nothing
wrong with this. Tivo isn't selling hardware. Tivo is selling a
service. They leveraged open source code to create this service, and
they created an unopenable black box using that code. They released
their changes to that code back to the public, and anybody else who
wants to do so can create their own hardware and run Tivo's changes.
In other words, the GPL fulfilled its function, the changes were given
back. Tivo's only "crime" was in doing the razor blade service idea
and then trying to protect themselves from unscrupulous people.
> Some guy called Stallman seems to think you disagree with the goal of the
Yes, I absolutely disagree with Stallman and virtually everything he
says nowadays. He's gone from genius to socialist zealot.
The goal of the GPL, in my opinion, was to preserve freedom by keeping
what was released under it free for all to see and use. When the code
is free, everybody benefits. You can all use the code. You can all
modify the code. If you modify it and sell it, you have to give those
modifications back. Tivo did this. Hell, I've done this.
However, this freedom does NOT give you the freedom to take advantage
of other people's schemes. This does NOT give you the freedom to steal
service. This absolutely does not give you the freedom to set terms on
USE of that code. The GPLv2 focused entirely on redistribution. If I
redistribute the code, then I have to give away my changes. The GPLv3
adds a new one. Now, if I redistribute that code in a product, I have
to not only make the changes available, but I have to let the end-user
modify the product. I cannot protect my product and my business plan
through technical measures. I cannot give away razors while trying to
sell razor blades.
In other words, I cannot use GPLv3 code in any sort of actual
non-end-user-modifiable product that I sell. If I use GPLv3 code, I
must take extra steps to make the product modifiable by end-users.
And why? Because Stallman and the FSF think that's a good idea? Yes, I
disagree with them. I do not think that it is a good idea. I think
it's restrictive of freedoms for the developer. I want to use the open
source code to create new cool products, but this sort of ridiculous
restriction only limits the use. It takes away the freedoms of the
developer. It is far, far less free than the GPLv2 was.
> Is he wrong?
Yes. Richard Stallman is absolutely, 100% wrong in everything he has
said for at least the last 3 years. He can no longer be trusted on any
subject of any kind.
wp-hackers mailing list
wp-hackers at lists.automattic.com
More information about the wp-hackers