From: William Lee Irwin III <wli@holomorphy.com>
To: "Jeff V. Merkey" <jmerkey@mail.gadugi.org>
Cc: linux-kernel@vger.kernel.org, jmerkey@gadugi.org
Subject: Re: Linux 2.6.9 and the GPL Buyout
Date: Tue, 21 Dec 2004 01:56:36 -0800 [thread overview]
Message-ID: <20041221095636.GJ771@holomorphy.com> (raw)
In-Reply-To: <20041220212723.GA8634@mail.gadugi.org>
On Mon, Dec 20, 2004 at 03:27:23PM -0600, Jeff V. Merkey wrote:
[...]
> Despite dubious reporting and wild conjecture, the buyout was not geared
> towards helping SCO, or in concert with M$ as some sort of grand
> conspiracy. It was geared towards creating a new licensing and legal
> model for open source development. The Cherokee Nation is enacting
> legislation to promote open source development. So the whole buyout
> was me and a few folks attempting to convert Linux GPL code into
> a licensing model and Cherokee Nation Copyrights that renders the
> code sovereign and immune from litigation outside of tribal courts
> and jurisdiction. So much for all the SCO and other legal wranglings
> regarding this effort and open source in general. We are immune from
> these people and so are any projects that use our licensing or host
> on our servers. I personally told Darl "Mad Dog" McBride at SCO
> good luck and to buzz off.
[...]
As interesting and informative as this is, maybe there needs to be a
mailing list (linux-politics-discuss?) or something to serve as an
appropriate outlet for these kinds of discussions (as well as bitkeeper
licensing issues, C++ modules, etc.). It's a bit difficult to
appreciate the relevance of this kind of "political" message to a list
dedicated to kernel programming and cold, hard code.
Congratulations on your new directions and position. I hope there will
soon be a place for which your informative announcements are more
appropriate than linux-kernel.
- wli
next prev parent reply other threads:[~2004-12-21 9:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-20 21:27 Linux 2.6.9 and the GPL Buyout Jeff V. Merkey
2004-12-20 21:42 ` Timothy D. Witham
2004-12-20 21:47 ` Jeff V. Merkey
2004-12-21 9:25 ` Bernd Petrovitsch
2004-12-21 16:11 ` Jeff V. Merkey
2004-12-21 18:05 ` Bernd Petrovitsch
2004-12-20 22:26 ` Jesper Juhl
2004-12-20 22:18 ` Jeff V. Merkey
2004-12-20 23:03 ` Jesper Juhl
2004-12-20 22:57 ` Jeff V. Merkey
2004-12-21 2:40 ` Gene Heskett
2004-12-21 16:26 ` Jeff V. Merkey
2004-12-21 19:31 ` Zwane Mwaikambo
2004-12-21 9:56 ` William Lee Irwin III [this message]
2004-12-21 16:14 ` Jeff V. Merkey
2004-12-21 12:34 ` Horst von Brand
2004-12-21 16:19 ` Jeff V. Merkey
2004-12-21 16:51 ` Henning P. Schmiedehausen
2004-12-21 17:19 ` Jeff V. Merkey
2004-12-21 19:04 ` David Woodhouse
2004-12-21 21:11 ` Jeff V. Merkey
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=20041221095636.GJ771@holomorphy.com \
--to=wli@holomorphy.com \
--cc=jmerkey@gadugi.org \
--cc=jmerkey@mail.gadugi.org \
--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