From: "b.n." <brullonulla@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] 2 to 3??
Date: Wed, 18 Jul 2007 09:28:40 +0000 [thread overview]
Message-ID: <469DDD48.2060006@gmail.com> (raw)
In-Reply-To: <200707131811.27626.mcbrides9@comcast.net>
Personally I'm quite happy with both GPLv2 and GPLv3. Frankly, my only
real, serious concern is the fact that the two licences are incompatible.
The fact compatibility has not explicitly allowed sounds plain crazy to
me. This means that GPLv2-only projects won't exchange code anymore with
GPLv3-only or GPLv3-and-later projects, thus splitting the ecosystem in
half, with benefit for no one.
When I tried asking about how to have some degree of compatibility
between GPLv2 and GPLv3 in code I write, everyone told me "just license
it under GPLv2 or any later version". The problem is that in this case I
have to blindly trust the FSF about anything that will come out of it.
GPLv3 raised serious concerns to many, and I also tried to follow
carefully the thing, even if at the end, for all my purposes, I find
them more or less equivalent. But how can I know what GPLv4 or v5 will
be? Will I still like it? Using the "any later version" clause puts me
in the hands of FSF without chance of coming back. Not using it (and
just using "v2 and v3") puts me at the stake whenever GPLv4 will be out.
What should I do, in your opinion?
m.
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-07-18 7:12 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 22:11 [gentoo-user] 2 to 3?? Jerry McBride
2007-07-13 22:27 ` Bo Ørsted Andresen
2007-07-18 9:28 ` b.n. [this message]
2007-07-18 16:23 ` Boyd Stephen Smith Jr.
-- strict thread matches above, loose matches on Subject: below --
2007-07-16 0:52 burlingk
2007-07-16 12:15 ` Mark Shields
2007-07-16 21:53 ` Jerry McBride
2007-07-17 1:26 ` Volker Armin Hemmann
2007-07-17 1:59 ` Boyd Stephen Smith Jr.
2007-07-17 1:26 ` Volker Armin Hemmann
2007-07-17 2:08 ` Henk Boom
2007-07-17 10:14 burlingk
2007-07-17 10:42 ` Abraham Marín Pérez
2007-07-17 11:01 ` Graham Murray
2007-07-17 12:48 ` Stroller
2007-07-17 16:19 ` Volker Armin Hemmann
2007-07-18 13:13 ` Stroller
2007-07-18 17:40 ` Volker Armin Hemmann
2007-07-18 18:10 ` Boyd Stephen Smith Jr.
2007-07-18 22:34 ` Stroller
2007-07-18 23:48 ` Volker Armin Hemmann
2007-07-19 0:41 ` Boyd Stephen Smith Jr.
2007-07-19 2:10 ` Stroller
2007-07-19 1:58 ` Stroller
2007-07-17 17:14 ` Boyd Stephen Smith Jr.
2007-07-17 19:29 ` Mike Edenfield
2007-07-17 12:12 burlingk
2007-07-17 11:29 ` Abraham Marín Pérez
2007-07-17 17:38 burlingk
2007-07-17 17:27 ` Boyd Stephen Smith Jr.
2007-07-18 12:38 ` Alan McKinnon
2007-07-18 14:13 ` Stroller
2007-07-18 16:15 ` Boyd Stephen Smith Jr.
2007-07-18 13:48 ` Stroller
2007-07-18 16:33 ` Boyd Stephen Smith Jr.
2007-07-17 17:57 burlingk
2007-07-18 13:51 ` Stroller
2007-07-18 4:18 burlingk
2007-07-18 4:26 burlingk
2007-07-18 11:07 burlingk
2007-07-18 12:29 ` Dan Cowsill
2007-07-19 5:54 burlingk
2007-07-19 6:13 burlingk
2007-07-19 5:59 ` Boyd Stephen Smith Jr.
2007-07-19 14:37 burlingk
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=469DDD48.2060006@gmail.com \
--to=brullonulla@gmail.com \
--cc=gentoo-user@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