From: Joshua David Williams <yurimxpxman.lkml@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: GPLv3 dispute solution - new open source license?
Date: Mon, 18 Jun 2007 17:47:23 -0400 [thread overview]
Message-ID: <200706181747.23230.yurimxpxman@gmail.com> (raw)
On 6/18/07, H. Peter Anvin <hpa@zytor.com> wrote:
> You probably don't want do design a license without involving a
> competent lawyer. We don't expect lawyers to write kernel code, either.
True enough, and I realized this when I wrote my initial post, but it's not
what I wrote so much as the concept. I haven't seen the idea come up in any
threads, so I thought I'd throw it out there.
Open source and free software are clearly two different things, so it doesn't
make sense that an open source project would use a free software license. The
FSF has made it very clear that their objectives are very different from
ours.
The GPLv2 is a great license, but it's not perfect. The FSF recognised several
of the problems when they introduced the first public draft of v3. Since they
are heading in an opposite direction from the open source community, I
believe that we are now facing a clear dividing line between the two camps.
We cannot cling to the fifteen year-old license forever, expecting to never
be burnt.
If we can't adopt the GPLv3, it seems obvious to me that we need our own
solution.
--
It's a commonly known fact that most intruders come in through Windows.
next reply other threads:[~2007-06-18 21:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 21:47 Joshua David Williams [this message]
2007-06-18 22:01 ` GPLv3 dispute solution - new open source license? Carlo Wood
2007-06-18 23:24 ` Alan Cox
2007-06-18 23:22 ` alan
-- strict thread matches above, loose matches on Subject: below --
2007-06-18 22:07 Joshua David Williams
2007-06-18 22:43 ` david
2007-06-19 2:39 ` Alexandre Oliva
2007-06-18 21:25 Joshua David Williams
2007-06-18 21:38 ` H. Peter Anvin
2007-06-19 21:37 ` Chris Snook
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=200706181747.23230.yurimxpxman@gmail.com \
--to=yurimxpxman.lkml@gmail.com \
--cc=linux-kernel@vger.kernel.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