mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Morton Harrow <mharrow@linuxmail.org>
Cc: Miod Vallat <miod@online.fr>,
	licensing@fsf.org, linux-kernel@vger.kernel.org, rms@gnu.org,
	claire.newman@canonical.com, announce@fsfeurope.org,
	misc@openbsd.org, ubuntu-users@lists.ubuntu.com,
	fedora-list@redhat.com, netbsd-users@netbsd.org,
	freebsd-questions@freebsd.org
Subject: Re: GPL version 4
Date: Wed, 16 Jul 2008 17:41:50 -0400	[thread overview]
Message-ID: <33958.1216244510@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Thu, 17 Jul 2008 05:31:15 +0800." <20080716213115.C747F7BC45@ws5-10.us4.outblaze.com>

[-- Attachment #1: Type: text/plain, Size: 898 bytes --]

On Thu, 17 Jul 2008 05:31:15 +0800, Morton Harrow said:

> I see with pain in my heart that the GPLv3 doesn't actually give the
> users of GPLv3 software the liberty and freedom the FSF has been
> fighting for. Instead they are forced to play by the strict set of
> terms the GPLv3 provides.

You missed an important philosophical point.  In Richard Stallman's world view,
it isn't the user's freedoms that matter, it's the *software*s freedom.

> For example, as a liberated computer user, I might like to incorporate
> a high quality piece of GPLv3 software in a commercial product,
> which for bussiness strategic reasons happens to be closed source software.
> But the GPLv3 denies my claim for this freedom to do this.

Right, because doing so would impact the *software*s freedom.

> I fail to see how that strengthens me in a Free and Liberal Software World.

Sometimes, it's not about you.

[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

  reply	other threads:[~2008-07-16 21:42 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-16 21:31 Morton Harrow
2008-07-16 21:41 ` Valdis.Kletnieks [this message]
2008-07-16 22:23   ` Matthias Kilian
2008-12-14 21:12   ` Mark Kirkwood
2008-12-15  0:27     ` Marco Peereboom
2008-12-15  1:31       ` Mark Kirkwood
2008-12-15  1:44         ` bofh
2008-12-15  1:43     ` Damien Miller
     [not found]     ` <E1LCDed-0001OK-UC@fencepost.gnu.org>
2008-12-15 20:51       ` Chad Perrin
2008-07-16 22:06 ` David Collier-Brown
2008-07-17 21:17   ` linux-os (Dick Johnson)
2008-07-17 21:24     ` Valdis.Kletnieks
2008-07-16 22:08 ` Al Viro
2008-07-17  2:12 ` Kasper Sandberg
2008-07-17 11:21 ` Alexandre Oliva
     [not found] <aQmTc-5A5-3@gated-at.bofh.it>
2008-07-18 19:42 ` Bodo Eggert
2008-07-19  0:47   ` David Schwartz
2008-07-19  3:05     ` Eric Furman
     [not found]     ` <E1KKQd9-000114-IV@fencepost.gnu.org>
2008-07-20  8:34       ` Aleksej Saushev
2008-07-20 12:21         ` Charles L. Nelson
2008-07-20 15:15         ` Kasper Sandberg
  -- strict thread matches above, loose matches on Subject: below --
2008-07-17  8:31 Julian H. Stacey
2008-07-16 18:09 Morton Harrow
2008-07-16 18:43 ` Adrian Bunk
2008-07-16 19:14 ` Valdis.Kletnieks
2008-07-16 21:48 ` Jan Engelhardt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=33958.1216244510@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=announce@fsfeurope.org \
    --cc=claire.newman@canonical.com \
    --cc=fedora-list@redhat.com \
    --cc=freebsd-questions@freebsd.org \
    --cc=licensing@fsf.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mharrow@linuxmail.org \
    --cc=miod@online.fr \
    --cc=misc@openbsd.org \
    --cc=netbsd-users@netbsd.org \
    --cc=rms@gnu.org \
    --cc=ubuntu-users@lists.ubuntu.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®