From: "Jeff V. Merkey" <jmerkey@gadugi.org>
To: Bernd Petrovitsch <bernd@firmix.at>
Cc: "Jeff V. Merkey" <jmerkey@mail.gadugi.org>,
Linux Kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.9 and the GPL Buyout
Date: Tue, 21 Dec 2004 09:11:23 -0700 [thread overview]
Message-ID: <41C84B2B.4050408@gadugi.org> (raw)
In-Reply-To: <1103621128.31663.6.camel@tara.firmix.at>
Bernd Petrovitsch wrote:
>On Mon, 2004-12-20 at 15:47 -0600, Jeff V. Merkey wrote:
>[...]
>
>
>>GPL code remains GPL code. Code written and republished under Cherokee
>>Nation Copyrights or Cherokee Nation Public license will become sovereign and
>>
>>
>
>You probably cannot "republish code under a different license" -
>especially not if it was released under Author's rights (in german:
>"Urheberrecht") which is not uncommon in continental Europe.
>Anf getting rid of the GPL (which your "republish under some new
>license" implies) requires IMO the explicit written agreement of all
>concerned persons.
>
>BTW the only possibility of getting rid of Author's right is to wait for
>the death of the last author of a given text/music/source code and wait
>than 70 years (as it stands now).
>
>
>
>>under tribal jurisdiction and laws. We are publishing the draft legislation
>>
>>
>
>So you are simply forking a part of the Linux kernel thus making all of
>the other code inthat project GPL and probably not gaining anything
>else.
>Have fun with your Linux kernel fork similar to all other forks ...
>
> Bernd
>
>
A copyright holder can re-release their code under any license they
choose, even if
they have released under GPL previously. This is because GPL code
really isn't free,
it's owned by the copyright holder. And honestly, the way the GPL is
worded it
in fact affects an implied transfer of copyright ownership to whomeve
receives it.
Truly free code isn't copyrighted by any individual, or is copyrighted
by an organization
that uses a license that really is free.
Jeff
next prev parent reply other threads:[~2004-12-21 16:09 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 [this message]
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
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=41C84B2B.4050408@gadugi.org \
--to=jmerkey@gadugi.org \
--cc=bernd@firmix.at \
--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