public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Vincent Launchbury <vincent@doublecreations.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Re: Documentation licenses and license_groups
Date: Tue, 05 Jan 2010 22:00:57 -0500	[thread overview]
Message-ID: <4B43FCE9.7060402@doublecreations.com> (raw)
In-Reply-To: <pan.2010.01.05.23.54.07@cox.net>

Duncan wrote:
> Quickly checking wikipedia (without verifying further), I'm probably
> thinking about a different license, but I had it in my head that GPLv1
> had a "no commercial use" clause (or allowed it), and that is why it
> was no longer considered free software, as it impinged on the user's
> freedom to use as they wish.  Pending further research, therefore,
> I'll just say I seem to have been mistaken.

Looking in section 2b, it mentions that you must "[cause work containing
GPL'd code..] to be licensed at no charge to all third parties... "
(excluding warranty protection). This is most probably the issue, that
you can't sell it.  I hadn't realized this before.

> The FSF "or later version" clauses are generally optional

But isn't this a problem with GPL-2 and 3 also? The term GPL-compatible
is too vague--which version is it referring to? For example, see
http://www.fsf.org/licensing/licenses/ again:

   Please note that GPLv2 is, by itself, not compatible with GPLv3.
   However, most software released under GPLv2 allows you to use the
   terms of later versions of the GPL as well.

So doesn't it already assume that GPL-2 code contains the 'later
version' option?

But in any case GPL-1 is probably not suitable for either license group,
if theres a case where it can't be sold.

I still support Ulrich's suggestions though.





  reply	other threads:[~2010-01-06  4:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-05 14:34 [gentoo-dev] Documentation licenses and license_groups Ulrich Mueller
2010-01-05 17:15 ` Vincent Launchbury
2010-01-05 18:07   ` [gentoo-dev] " Duncan
2010-01-05 20:31     ` Ulrich Mueller
2010-01-05 23:54       ` Duncan
2010-01-06  3:00         ` Vincent Launchbury [this message]
2010-01-06  4:34           ` Jeroen Roovers
2010-01-06  5:08             ` Vincent Launchbury
2010-01-06  4:39           ` Jeroen Roovers
2010-01-06  5:45           ` Ulrich Mueller
2010-01-06 16:05     ` Richard Freeman
2010-01-06 23:59       ` Duncan
2010-01-05 18:10   ` [gentoo-dev] " Ulrich Mueller
2010-01-07 10:03 ` Hanno Böck
2010-01-07 11:00   ` Ulrich Mueller
2010-01-07 12:41     ` Hanno Böck
2010-01-09 17:54       ` Ulrich Mueller
2010-01-09 21:31         ` Vincent Launchbury

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=4B43FCE9.7060402@doublecreations.com \
    --to=vincent@doublecreations.com \
    --cc=gentoo-dev@lists.gentoo.org \
    /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