mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
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: Thu, 17 Jul 2008 08:21:28 -0300	[thread overview]
Message-ID: <orprpcu56v.fsf@oliva.athome.lsd.ic.unicamp.br> (raw)
In-Reply-To: <20080716213115.C747F7BC45@ws5-10.us4.outblaze.com> (Morton Harrow's message of "Thu\, 17 Jul 2008 05\:31\:15 +0800")

On Jul 16, 2008, "Morton Harrow" <mharrow@linuxmail.org> wrote:

> 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.

> For example, as a liberated computer user, I might like to incorporate
> a high quality piece of GPLv3 software in a commercial product,

You can do that.  There are lots of commercial products containing
GPLv3 software out there.

> which for bussiness strategic reasons happens to be closed source software.
> But the GPLv3 denies my claim for this freedom to do this.

You are mistaken in several levels.

1. Disrespecting others' freedoms is not a matter of freedom, it's a
matter of power.

2. Nothing in the GPL prevents you from doing any of this.  If there
is something that prevents you from doing this, it's copyright law.
You won't find prohibitions in the GPL.

3. If you're unable to combine third-party GPL-incompatible software
with GPL software, it's because the third party prevented you from
doing this, and you accepted it.  Don't blame the GPL for your
acceptance of such terms.

4. If you decide to not release your own code under the GPL, even
though this stops you from releasing the program you wrote with help
from other authors who chose the GPL, that's your decision.  Don't
blame the GPL for the consequences of your own decisions.

-- 
Alexandre Oliva         http://www.lsd.ic.unicamp.br/~oliva/
Free Software Evangelist  oliva@{lsd.ic.unicamp.br, gnu.org}
FSFLA Board Member       ¡Sé Libre! => http://www.fsfla.org/
Red Hat Compiler Engineer   aoliva@{redhat.com, gcc.gnu.org}

  parent reply	other threads:[~2008-07-17 11:22 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
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 [this message]
     [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=orprpcu56v.fsf@oliva.athome.lsd.ic.unicamp.br \
    --to=aoliva@redhat.com \
    --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®