From: "Jeff V. Merkey" <jmerkey@gadugi.org>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
Cc: "Jeff V. Merkey" <jmerkey@mail.gadugi.org>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.9 and the GPL Buyout
Date: Tue, 21 Dec 2004 09:19:24 -0700 [thread overview]
Message-ID: <41C84D0C.3020008@gadugi.org> (raw)
In-Reply-To: <200412211234.iBLCYVec006232@laptop11.inf.utfsm.cl>
Horst von Brand wrote:
>Right. But the Cherokee Nation would have to be recognized, and it would
>have to adhere to the Berne Convention and a lot of other stuff for this to
>make any kind of difference. Plus they would need the international clout
>to make their decisions stick. I.e., it won't help a bit.
>
>
We are an A8 classified orgnaization with the Federal Government. This
means we come
before handicapped businesses and minorities for government purchases,
and the highest
levels of the Federal Government are aware of this project. This also
means is a situation
where the United States is using Open source, Federal Law requires ours
be used instead
of Linux or BSD.
>What is wrong with GPL for the kernel? That could be a useful discussion
>(just not here, please). Also note that some 80% of OSS is under GPL/LPGL,
>so staying compatible with those licenses is very important on its own
>right.
>
>What is wrong with starting with the *BSDs for the merged OS, if GPL won't
>do for some weird reason?
>
>Besides, had you asked politely if the LKML crowd would consider a change
>in license to the kernel _for a purpose like you say here_, and _coherent_
>reasons for a change in license, there would have been quite a bit more
>receptiveness. But, as the kernel has thousands of contributors whose work
>is _very_ difficult to separate (probably more than just building the whole
>shebang from scratch), the point is moot anyway.
>
>[...]
>
>
I don't believe this one bit. LKML has some very good folks but it also
has some very immature and childish folks with thier own agendas. It
also has a lot of folks from post-
communist Europe and the views of many of these people are not aligned
with captilist
viewpoints. There will always be hecklers and idiots who just don't get
it, and it really
doesn't matter one bit. The verdict's in, the light moves forward.
:-)
Jeff
next prev parent reply other threads:[~2004-12-21 16:17 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
2004-12-21 16:14 ` Jeff V. Merkey
2004-12-21 12:34 ` Horst von Brand
2004-12-21 16:19 ` Jeff V. Merkey [this message]
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=41C84D0C.3020008@gadugi.org \
--to=jmerkey@gadugi.org \
--cc=jmerkey@mail.gadugi.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vonbrand@inf.utfsm.cl \
/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