beg to differ [LWN.net]

beg to differ

Posted Sep 26, 2006 16:42 UTC (Tue) by ccyoung (subscriber, #16340)
In reply to: Just a question about the GPLv3 by Jel
Parent article: Some GPLv3 clarifications from the FSF

While I

offer my custom libraries to anyone who wishes them
I ask consultants who do generic work for me, such as mail configurations, to post the work on the web for others' benefit
contribute work and modest resources to various projects

My main business is a vertical web-based service. If I were to give away my code I would literally be giving away my business. No one paid me to write the code. I wrote it to perform execute this business. I am sure I am not alone.

(Log in to post comments)

beg to differ

Posted Sep 26, 2006 17:41 UTC (Tue) by Jel (guest, #22988) [Link]

Oh, well, if you're talking about your own code, then you can choose any
license you want, including "GPLv3, except for section X". I'm talking
about the many websites that are based on OTHER people's GPL'd code, but
don't let other people enhance those sites.

beg to differ

Posted Sep 26, 2006 19:54 UTC (Tue) by JoeF (subscriber, #4486) [Link]

And that's a use scenario. GPLv2 is concerned about distribution.
So, GPLv3 seems to restrict use, and that's exactly what the Linux kernel people are concerned about.
Restricting use is a very slippery slope.

beg to differ

Posted Sep 26, 2006 21:11 UTC (Tue) by Jel (guest, #22988) [Link]

GPLv2 AND v3 are both about ensuring freedoms, not restricting use. They
limit the freedom to limit use. It's a core reason for the existence of
the GPL, and that's precisely why GPLv3 is just a natural follow-up to
v2.

beg to differ

Posted Sep 26, 2006 22:45 UTC (Tue) by JoeF (subscriber, #4486) [Link]

If you can't use a GPL3-version of a program on a website without giving people the source, then it is a use restriction.
With GPLv2, you can modify sources as much as you want without giving out the source, as long as you don't distribute the code. That's a big difference. GPLv2 does not put restrictions on the use, it puts restrictions on the distribution only.

beg to differ

Posted Sep 26, 2006 23:28 UTC (Tue) by Jel (guest, #22988) [Link]

The intention with GPLv2 is that you can use the code INTERNALLY, in your
own organisation, without giving out the code. Again, the "restrictions"
of the GPL are restrictions AGAINST restricting freedom. The freedom to
enslave people is not a freedom that most ethical people miss. The GPL
simply stands up for such ethics, and makes sure that people are not
enslaved, by guaranteeing technological freedom via restrictions in line
with those ethics. You can argue that you'd like the restrictions
removed, but I'm afraid you will then be taking an unethical stance that
I have no interest in.

beg to differ

Posted Sep 27, 2006 0:25 UTC (Wed) by JoeF (subscriber, #4486) [Link]

Nope. That is what you may think.
The fact is that the GPLv2 restricts distribution. Use, be it internal or external, is not restricted.
Again, the GPLv3 restricts the use, and therefore goes against the freedom you so stress. The GPLv3 restricts the freedom to use an application. Plain and simple. And that is bad.
And I would appreciate if you stopped accusing me of being unethical. It is you who is completely out of line with your slavery comparison. If I would use your line of "argument", I would have to argue that the GPLv3 enslaves people, by restricting the use of software.
What is next, restricting the use of GPLed software in stem-cell research, because that goes against the ethics of some people? Keep your political stand out of software licenses.

beg to differ

Posted Sep 27, 2006 9:07 UTC (Wed) by Jel (guest, #22988) [Link]

Well then I guess we'll have to agree to disagree.

affero clause

Posted Sep 27, 2006 4:55 UTC (Wed) by sanjoy (subscriber, #5026) [Link]

If you can't use a GPL3-version of a program on a website without giving people the source, then it is a use restriction.

The so-called Affero restriction is a modification restriction. If you get a program subject to the Affero restrction, you are free to run the program as you received it. If the program is a web service and makes its source available to users, then when you run it, it would do the same. You cannot remove those facilities, so your right of modification is restricted.

If the program is not a web service, but you turn it into one, then you have to make sure that you include "get the source" facilities. That's also a modification restriction: "You are free to modify it so long as you...".

--Sanjoy Mahajan

affero clause

Posted Sep 27, 2006 6:27 UTC (Wed) by JoeF (subscriber, #4486) [Link]

Even as a modification restriction, it restricts the freedom more than the GPLv2.
And modification is a case of use. I can use a GPLv2 program any way I want, including modifying it in any way I want.

modification restrictions in GPLv2

Posted Sep 27, 2006 9:07 UTC (Wed) by xoddam (subscriber, #2322) [Link]

> I can use a GPLv2 program any way I want, including
> modifying it in any way I want.

No, you can't. Reread section 2.

http://www.gnu.org/copyleft/gpl.html#SEC3

modification restrictions in GPLv2

Posted Sep 27, 2006 14:36 UTC (Wed) by JoeF (subscriber, #4486) [Link]

That section talks about "copy and distribute" modifications. Thanks for making my point.

modification restrictions in GPLv2 and the Affero clause

Posted Sep 28, 2006 1:01 UTC (Thu) by xoddam (subscriber, #2322) [Link]

You are correct; section 2 of the GPLv2 doesn't emphasise the fact that
modification is also covered by the licence. Basically for most classes
of software if your modification is kept private no-one is going to know
or care. But in most countries you simply don't have the right to modify
the code except as the licence permits (and except, in a few countries,
for fair use rights, as Dan J "you don't need a licence" Bernstein of
qmail fame insists: http://cr.yp.to/softwarelaw.html).

It was the original choice of the FSF not to make too big a beef about
restricting modification. But you are nevertheless prohibited by clause
2c from removing copyright, warranty and licence announcements or menu
options from an interactive program (that's not how it's worded, because
furthermore they want you to *add* those things if you turn a
non-interactive program into an interactive one). That's true even with
GPLv2 and even for modifications you only make in private.

The Affero clause is an equivalent restriction, prohibiting removal of a
feature. The difference is, that in the case of a web application
available to the public, your modifications are on show to the world, so
a 'private modification' infringement is not private at all. It is
visible and meaningful in a way that it isn't for something you only use
within your own organisation.

The fundamental difference is not in the way the licence or copyright law
works, but in the nature of the application and in the fact that this
kind of breach is actually visible. The language of the Affero clause
therefore chooses to emphasise a different point of law.

An attempt to enforce clause 2c of the GPLv2 against modifications to
your own copy of emacs would be frivolous. But the legally-equivalent
Affero clause has teeth.

> Thanks for making my point.

The point I have made is that modification restrictions in the GPL have
no effect on your right to use the copyrighted software you received
under the GPL. Nor do they have any effect on your right to *use* your
own modified versions -- but you have no right to make a modified version
except as the licence permits.

Somehow I don't think this is the same as the point that you think I've
made for you. People seem to think that because they are granted certain
permissions in respect of a particular version of a program, all possible
versions should carry the same permissions. That is not the case. The
licence actively prohibits some of those possible versions.

It has long been argued and agreed that BSD- and MIT-style licences
are "more free" than the GPLv2. The Affero General Public Licence and
the GPLv3 are, in different ways, each slightly "less free" than the
GPLv2, but in exactly the same way as the GPLv2 is "less free" than BSD:
they are copyleft licences which relax but do not overstep the bounds of
copyright.

If you wish, now that you understand that the monopoly granted by
copyright includes the exclusive right to prepare derivative works, to
join the good old BSD crew and bash the GPL for being un-free, go ahead.
The GPL camp won't miss you.

modification restrictions in GPLv2 and the Affero clause

Posted Sep 28, 2006 1:33 UTC (Thu) by JoeF (subscriber, #4486) [Link]

Your last sentence is of course one of the things that I have come to expect from zealots.
It is the GPL way or the highway...
Guess what, this elitist attitude is what will be the GPLs downfall.
Sad to see that GPL "defenders" are indeed on the same level as the average religious nut case.

No restrictions on use.

Posted Sep 27, 2006 4:46 UTC (Wed) by xoddam (subscriber, #2322) [Link]

> So, GPLv3 seems to restrict use

Read the (draft) licence, JoeF.

The GPLv3 draft *permits* a distributor to redistribute GPLv3 code with a
slightly different licence, namely 'GPLv3 plus extra conditions'. Such
extra conditions are of a very limited type. The one you've been
discussing is a requirement that downstream redistributors not remove a
feature of the code.

The scenario is this:

Party A, say lwn.net, decides to publish the source code for a web
application under the GPLv3.

Party B, say xoddam.com, modifies the code, makes certain enhancements,
including a feature which adds a little link in the corner of each page
saying 'download the source code for the running version of this website'
which works as advertised. xoddam.com redistributes this version of the
software (say it's a fork as lwn.net didn't like some or all of xoddam's
changes) but also adds a restriction to the licence, saying that
downstream redistributors must continue to provide the download feature.

Party C, say JoeF.com, downloads the source from xoddam.com and builds a
new website using the source code. JoeF is permitted to modify the
source code without redistributing its own changes -- but it implicitly
*does* redistribute, by virtue of providing the 'download the running
source code' link. If JoeF wishes to remove this link, it may -- but
then it simultaneously ceases to have any right to redistribute the
program it received from xoddam.com.

It would appear that the limitation shoots itself in the foot, because
the only right that the licence is able to take away is the one whose
exercise the extra restriction is trying to *encourage*.

This is precisely because it cannot impose restrictions on use. Some
developers might like to have a licence imposing a restriction that
actually prevents people from publishing websites based on such closed
modifications, but the GPLv3 is not that licence. Such a licence wold
necessarily overstep the clear boundaries of copyright law, into dubious
click-wrap contract territory: "By downloading this code you agree..."

I suppose there may be some who would argue that some of the content you
see when using a web application is part of the software and that the act
of responding to the HTTP request is therefore a partial act of
distribution of the software in 'binary' form (which is by the definition
in the GPL any form other than source code). My non-lawyerish opinion on
the matter is that this is the kind of discussion that could result in a
lot of wasted lawyers' fees, if it were not that any such content could
easily be replaced so that it is recognisably no longer subject to the
copyright of the upstream author.

No restrictions on use.

Posted Sep 27, 2006 6:45 UTC (Wed) by JoeF (subscriber, #4486) [Link]

Well, my position is that if I put a program, e.g., a Web service, up, I am not distributing it. I provide the output of the program, which is probably not under the GPL. Otherwise, the output of gcc, regardless of if it is used to compile a proprietary program or another GPL-ed program, would be under the GPL as well. That would be a sure way to kill FOSS...
So, if an application like a Web service licensed under GPLv3 requires me to put up a link to the source, it is a use restriction. If it only requires that if I wish to redistribute my modified program, fine. No problem with that. But for that, the GPLv3 is not required. That works fine with the GPLv2, since if I redistribute a program, I have to make the source and my changes available, and it is trivial to find the differences (the usage of diff should be quite well known...)
So, then, a) why is this clause in the draft, and b) why do some people feel the need to argue for it with their personal ethics? Limiting the use of a program based on some personal convictions is just wrong. One person doesn't like the use in military applications, another doesn't want the use in some pornographic context, the next one has something against certain religions, the forth one doesn't want his software to be used by a specific political party, etc.
Limitation of use, for any reason, is just plain wrong for FOSS software, and doesn't belong in a FOSS software license. If my use is limited by the license, it is not Open Source anymore.

The GPLv3 draft does not impose any use restrictions -- it imposes *modification* restrictions.

Posted Sep 27, 2006 9:01 UTC (Wed) by xoddam (subscriber, #2322) [Link]

I reread the draft more closely, and it turns out that my conclusion
above (that the Affero licence restriction is ineffectual) is completely
wrong. I'm sorry if I've misled anyone :-)

The reason is that copyright extends to the right to prepare derivative
works. The GPL grants you permission to modify a program, *with
restrictions* (this is nothing new to version 3). In some countries the
principle of fair use applies; if the restrictions in question are
somehow 'unfair' they may be unenforceable.

> I provide the output of the program, which is probably not
> under the GPL. Otherwise, the output of gcc, regardless of
> if it is used to compile a proprietary program or another
> GPL-ed program, would be under the GPL as well.

I was talking (beside the point, as it turns out) about some theoretical
way someone might try to use their exclusive right over distribution to
force you to use their work in a particular way. They can't. They
*particularly* couldn't do so using the GPL, because the GPL (all
versions, text taken from the current GPLv3 draft) contains the
assurance:

"The output from running it is covered by this License only if the
output, given its content, constitutes a covered work."

> So, if [the licence of] an application like a Web service
> ... requires me to put up a link to the source, it is a
> use restriction.

Copyright can impose no restriction on your use of a work once you have a
copy, and the GPL explicitly acknowledges this -- the chief difference
between version 2 and version 3 is that the GPLv2 doesn't qualify it
with "unmodified". This may be the ultimate source of our confusion.

What copyright *can* impose is a restriction on your right to modify the
work, so if the code you received implements a certain feature, the
licence may prohibit you from removing it. The GPL does contain such a
restriction (clause 2c of version 2, or 5c of the draft of version 3):
You must include prominent copyright and licence information in an
interactive program, unless the original work was interactive and does
not do so. (By the by in this day and age of source control I believe
GPLv2 clause 2a, requiring prominent notice of modifications within the
modified files, is honoured mostly in the breach) The Affero General
Public Licence is a licence derived from GPLv2 by adding a clause 2d,
which disallows removal of their "download the source" feature:

http://www.affero.org/oagpl.html

"If the Program as you received it is intended to interact with users
through a computer network and if, in the version you received, any user
interacting with the Program was given the opportunity to request
transmission to that user of the Program's complete source code, you must
not remove that facility from your modified version of the Program or
work based on the Program, and must offer an equivalent opportunity for
all users interacting with your Program through a computer network to
request immediate transmission by HTTP of the complete source code of
your modified version or other derivative work."

If you think that's unfair, travel to a country with extra-strong Fair
Use rights before violating the licence :-)

The draft GPLv3 alone does not contain any such requirement. What it
*does* do is allow people who are redistributing things under the terms
of the licence to use a (slightly) different licence. One of the
permitted additional restrictions is an "Affero clause".

> So, then, a) why is this clause in the draft,

This clause exists so that code under GPLv3 may be combined with code
under another licence which already has restrictions that *aren't* in
GPLv3. The result may be developed and distributed under the
intersection of the permissions in the two licences. The GPLv2 does not
permit this, as *no* extra restrictions may be imposed. In general terms
this is about expanding the GPL ecosystem, and a specific short-term goal
is to allow the efforts of the Apache Foundation and the Free Software
Foundation to develop free Java class libraries to be combined and
distributed together under a "GPLv3 + Apache patent clauses" licence.

If anything, the bit about Web applications was added as an afterthought,
because one company has already produced software under a licence which
is GPLv2 plus the restriction under discussion. This means that Affero
can move to "GPLv3 + Affero clause" when the GPLv3 is ready, and that
third parties may combine GPLv3 code with such Affero code without
worrying about licence incompatibility -- once again, this isn't possible
with the GPLv2.

All the restrictions under discussion are restrictions on modification
and redistribution, not use.

> b) why do some people feel the need to argue for it with their
> personal ethics?

I wasn't aware they were. It's a pretty esoteric clause, IMO. In any
case, if they were arguing for the actual text, they weren't arguing for
use restrictions. For what it's worth, the FSF argues for its licence
changes not from 'personal' ethics but from the ethics of the 'Four
Freedoms', which I'm sure I don't need to repeat.

The GPLv3 draft does not impose any use restrictions -- it imposes *modification* restrictions.

Posted Sep 27, 2006 14:50 UTC (Wed) by JoeF (subscriber, #4486) [Link]

That applies to distribution, as the first sentence of section2 states: "You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications"
No problems with that.
But limiting my right to modify the work as I wish, if I don't distribute it, is just wrong. That's what proprietary software does. At that point, GPLv3 software would not be free as in freedom anymore, it would be free as in beer.

"b) why do some people feel the need to argue for it with their personal ethics?"
I wasn't aware they were.

Well, I was referring to somebody else in this thread who accused me of being unethical.

Anyway, I stand by my position that this would be a use restriction which does not belong in an Open Source license.

The GPLv3 draft does not impose any use restrictions -- it imposes *modification* restrictions.

Posted Sep 27, 2006 15:09 UTC (Wed) by Jel (guest, #22988) [Link]

The GPL is not an open source license, it's a free software license.

The GPLv3 draft does not impose any use restrictions -- it imposes *modification* restrictions.

Posted Sep 27, 2006 15:32 UTC (Wed) by JoeF (subscriber, #4486) [Link]

The GPLv2, yes. GPLv3 is not a free software license, because it restricts the use. Unless you define free as in "free beer".

The GPLv3 draft does not impose any use restrictions -- it imposes *modification* restrictions.

Posted Sep 27, 2006 15:42 UTC (Wed) by Jel (guest, #22988) [Link]

*sigh* Well, we're going around in circles here. Again, we'll have to
agree to disagree I guess. Sorry we couldn't find more common ground.

The GPLv3 draft does not impose any use restrictions -- it imposes *modification* restrictions.

Posted Sep 27, 2006 16:02 UTC (Wed) by JoeF (subscriber, #4486) [Link]

Well, if you had better arguments than accusing me of being unethical...
A license that restricts my use of a software is not free. Proprietary licenses restrict my freedom to use the software any way I want. A free license should not do that, or it ceases to be free.

The GPLv3 draft does not impose any use restrictions -- it imposes *modification* restrictions.

Posted Sep 27, 2006 16:13 UTC (Wed) by Jel (guest, #22988) [Link]

I didn't accuse you of being unethical. I said that the position you're
taking on this issue is unethical. There's a difference. One is an
attack against you, whilst the other is just an analysis of an issue,
which you will not take personally if you're objective. As for the
quality of my argument... the burden of proof is on you; you're the one
claiming that GPLv3 is somehow different from GPLv2, despite the authors
saying that it's a logical continuation, and me agreeing with them.
Anyway, without wanting to cause offense, I don't find this discussion
very interesting, so I'm going to leave it here.

The GPLv3 draft does not impose any use restrictions -- it imposes *modification* restrictions.

Posted Sep 27, 2006 17:16 UTC (Wed) by JoeF (subscriber, #4486) [Link]

Well, your analysis of the issue is deeply flawed, then.
The issue is if the GPLv3 would restrict the use of a GPLed program. And it seems that it does. That makes the current GPLv3 draft unfree. I am sorry if you are unable to see that.

The GPLv3 draft does not impose any use restrictions -- it imposes *modification* restrictions.

Posted Sep 27, 2006 17:39 UTC (Wed) by Jel (guest, #22988) [Link]

Well, again, I disagree, and stand by my points. Take them or leave
them.

The GPLv3 does not contain the Affero clause

Posted Sep 28, 2006 1:12 UTC (Thu) by xoddam (subscriber, #2322) [Link]

Wrong on two counts.

1. Neither version of the GPL contains any restriction on your right to
use the software you received. Modification is not "use".

2. The GPLv2 and GPLv3 contain essentially the same restrictions on
modification. The GPLv3 does point out that your unlimited right to use
the software applies to the *unmodified* version you received, where the
language of the GPLv2 permits you to read it as an unlimited right to use
any possible version. In neither case is it the copyright licence which
grants the right to use the program -- this is just a reminder.

The GPLv3 does not contain the Affero clause and does not restrict
modification any further than the GPLv2 already does.

What it does do is *permit* a downstream redistributor to *add* an
Affero-type clause -- which would results in relicensed software, in
exactly the same way as it is possible to take BSD code and put it in a
proprietary or GPL program. "GPLv3 + Affero clause" is not the same as
plain GPLv3.

The GPLv3 does not contain the Affero clause

Posted Sep 28, 2006 1:39 UTC (Thu) by JoeF (subscriber, #4486) [Link]

Modification is not "use".
Why not? I see this claim, which I consider wrong. I have the source code, and I have the freedom to do with the source code as I please.
The GPLv2 covers copyright, i.e., the right to copy the code. The current GPLv3 draft tries to limit what I can do with the code in the privacy of my own home. That's fundamentally wrong, if you value your freedom.

The GPLv3 does point out that your unlimited right to use the software applies to the *unmodified* version you received
Yes. And that is where one of the "4 freedoms" is removed. And that's what I object to.

The GPLv3 does not contain the Affero clause
Neither does the GPLv2. So, again, no change needed.

The GPLv3 permits essentially the same modifications as the GPLv2

Posted Sep 28, 2006 2:22 UTC (Thu) by xoddam (subscriber, #2322) [Link]

> The GPLv2 covers copyright, i.e., the right to copy the code.

The GPLv2 covers whatever copyright law covers in your country, including
preparation of derivative works if copyright covers that where you are.

> The current GPLv3 draft tries to limit what I can do with the
> code in the privacy of my own home.

The GPLv3 draft DOES NOT DIFFER from the GPLv2 in the essentials of the
permission it grants to modify. The GPL version 2 *ALSO* permits only
certain changes. If you do it in the privacy of your home, no-one is
going to sue you, not even if you do it to qmail or proprietary software
which you have no permission to modify whatsoever. That's fair use.
Exactly the same doctrine applies to making copies in the privacy of your
own home, but no-one will claim copyright doesn't grant an exclusive
right to make copies.

If you want to do it in a more public fashion, eg. by running a public
web service based on an unauthorised modification of a copyrighted work,
see a lawyer.

> > The GPLv3 does point out that your unlimited right to
> > use the software applies to the *unmodified* version you received

> Yes. And that is where one of the "4 freedoms" is removed.
> And that's what I object to.

I'm sure you have a point here, but I'm not sure how it applies to
copyleft licences or to copyright law. The GPL has *always*, and
*deliberately*, prohibited certain things which the "4 freedoms" in their
broad interpretation allow. For instance removal of copyright notices
and the licence itself. The GPLv3 doesn't change this limited
restriction of freedom IN ANY WAY.

The Affero licence -- by relying heavily on the limited permission to
modify in the way that simple copyleft does not require -- does take
copyleft a step further than the GPL ever did. Many of us were not even
aware that copyright includes the exclusive right to make derivative
works -- I've argued the opposite myself on these pages -- so it is
indeed a qualitative change in the way copyright law is wielded. But
even so, it's not a major change to the kind of permission granted.

from your other reply:
> ... I have come to expect from zealots.

I suggested you might have more fun playing with some other kids and you
called me a nasty name. I'm telling Teacher now.

The GPLv3 permits essentially the same modifications as the GPLv2

Posted Sep 28, 2006 4:28 UTC (Thu) by JoeF (subscriber, #4486) [Link]

The GPLv3 draft DOES NOT DIFFER from the GPLv2 in the essentials of the permission it grants to modify.
Oh, that "essentials" is such a good legal term. Is that all you can come up with?

I suggested you might have more fun playing with some other kids and you called me a nasty name. I'm telling Teacher now.
What a witty reply... You are such a good boy. Did you come up with it all on your own? That's a contender for "quote of the year".
Go play with the other kids in the sandbox. Call back when you have grown up.

That's all, folks

Posted Sep 28, 2006 6:35 UTC (Thu) by xoddam (subscriber, #2322) [Link]

> Oh, that "essentials" is such a good legal term.
> Is that all you can come up with?

Real lawyers are thin on the ground here, you're in the wrong place if
you want legal advice. I'm not a lawyer and didn't claim to be.

Nor had I read the licences as closely as I should have before
participating in such a flamefest. If the posts above are the thanks I
get for spending my time deciphering legalese on your behalf, then yes,
that is all I will come up with for you, sir.

That's all, folks

Posted Sep 28, 2006 8:17 UTC (Thu) by JoeF (subscriber, #4486) [Link]

I don't need your help to "decipher" legalese. I can do so much better on my own, thank you very much.
And indeed, your attempt to decipher legalese has led you to some wrong conclusions. Instead of recognizing that, you lash out at people who may have a better grasp of it (while I am not a lawyer, I deal with US-style legalese pretty much daily, and I even somewhat enjoy it.)
Fact is and remains that the current GPLv3 draft would restrict my freedoms to use GPLed software. No amount of insults like calling my position "unethical" changes that. On the contrary, I consider it unethical to call opposing viewpoints unethical. Nobody who actually is interested in a real discussion would do that. Only people who want to avoid discussion could even come up with the idea to call other viewpoints "unethical".
Granted, it wasn't you who hurled that insult, but your posts were only marginally more civil, with your (paraphrased) "it's the GPL way or the highway." That's hubris and arrogance, and if you become arrogant, you end up being just another Microsoft.
I use the GPLv2 in my own software because I value the freedoms it provides. And that includes the freedom to use GPLv2-licensed software any way I like, provided I don't distribute it. And using it in a Web service is not distributing it. It is "using" it, modifications of the source or not. It is not a distribution of the work in any sense of the word.
I do not wish to be told by anybody, not even RMS, that these freedoms are all of a sudden not all that important, and that RMS and the FSF know what's best for me. Of course, the FSF can take these freedoms away in the GPLv3, that's their prerogative. But then it's not a free license anymore, not in the sense that RMS has been going around for years talking about freedom.

That's all, folks

Posted Sep 30, 2006 22:04 UTC (Sat) by h2 (guest, #27965) [Link]

xoddam, your posts have been consistently informative and well thought out. As well as coherent. Thanks.

The fact that other people are not able, or willing, to match your level will hopefully not dissuade you from continuing to post. Since this type of non-discourse is a given in any public forum, all I can do is thank you for the patience you've shown to others who clearly do not grasp the question nearly as well as you do, which is personally more than I would have been able to do.