mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Morton Harrow" <mharrow@linuxmail.org>
To: "Miod Vallat" <miod@online.fr>
Cc: 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 05:31:15 +0800	[thread overview]
Message-ID: <20080716213115.C747F7BC45@ws5-10.us4.outblaze.com> (raw)


> ----- Original Message -----
> From: "Miod Vallat" <miod@online.fr>
> To: "Morton Harrow" <mharrow@linuxmail.org>
> Subject: Re: GPL version 4
> Date: Wed, 16 Jul 2008 20:06:23 +0000
> 
> 
> Shouldn't GPL versions follow the bright example of TeX, and thus the
> next version be 3.1?

Hi Miod,

Most of the people who have replied seem to be missing the point.

In addition to the announcement of the GPLv4, I was trying to discuss
another point.

The Free Software Foundation and their mission ("Since 1985 we've been
fighting for essential freedoms of computer users", please see
http://www.fsf.org) are not in line with their GPLv3.

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,
which for bussiness strategic reasons happens to be closed source software.
But the GPLv3 denies my claim for this freedom to do this.

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

With kind regards,
M.H.

=


-- 
Powered by Outblaze

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

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-16 21:31 Morton Harrow [this message]
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
     [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=20080716213115.C747F7BC45@ws5-10.us4.outblaze.com \
    --to=mharrow@linuxmail.org \
    --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=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®