ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] Owning your own copyrights in Linux
Date: Mon, 29 Aug 2016 19:07:45 -0400	[thread overview]
Message-ID: <20160829190745.415a6545@gandalf.local.home> (raw)
In-Reply-To: <1472510397.2376.48.camel@HansenPartnership.com>

On Mon, 29 Aug 2016 15:39:57 -0700
James Bottomley <James.Bottomley@HansenPartnership.com> wrote:


> Just on this point, one of the problems with companies is that they
> sell stuff, go bust or get bought out.  Perhaps this will never apply
> to Red Hat (although never say never) but many other people have to
> bear in mind that the entity they trust to hold the kernel copyrights
> today may not be the same entity tomorrow.
> 

I guess the interesting point is what happens to the copyrights if Red
Hat goes bust? Who defends it?

Now if another company were to buy out Red Hat, I guess the copyrights
would then be owned by them. But the code is still under GPLv2, the
worse that can happen is that they simply let others use it like BSD
licensed code. But as with most of the Linux kernel, my code is
interspersed with others code, so any such usage will require
permission from all copyright owners.

Also, I'm guessing that the new owner should be the one to fight for
it. I still feel that Red Hat will be around longer than I am, which
makes things easier when I die. Or perhaps a dual ownership may work in
such a case.

-- Steve

  reply	other threads:[~2016-08-29 23:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-28 17:00 James Bottomley
2016-08-29  6:20 ` Daniel Vetter
2016-08-29 13:07 ` Steven Rostedt
2016-08-29 15:54   ` James Bottomley
2016-08-29 16:16     ` Steven Rostedt
2016-08-29 18:32       ` Jiri Kosina
2016-08-29 18:47         ` Johannes Berg
2016-08-29 19:22           ` James Bottomley
2016-08-29 19:39             ` Jiri Kosina
2016-08-30  5:43             ` Johannes Berg
2016-08-29 19:42         ` Karen Sandler
2016-08-29 19:51           ` Karen Sandler
2016-08-29 22:39       ` James Bottomley
2016-08-29 23:07         ` Steven Rostedt [this message]
2016-08-29 23:17           ` Jiri Kosina
2016-08-29 23:20           ` James Bottomley
2016-08-30  1:28             ` Andy Grover

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=20160829190745.415a6545@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=torvalds@linux-foundation.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