From: Andy Grover <agrover@redhat.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
Steven Rostedt <rostedt@goodmis.org>
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 18:28:44 -0700 [thread overview]
Message-ID: <d3c2d35e-3321-a678-0aba-45e7802771e8@redhat.com> (raw)
In-Reply-To: <1472512800.2376.53.camel@HansenPartnership.com>
On 08/29/2016 04:20 PM, James Bottomley wrote:
> On Mon, 2016-08-29 at 19:07 -0400, Steven Rostedt wrote:
>> I guess the interesting point is what happens to the copyrights if
>> Red Hat goes bust? Who defends it?
>
> Like all IP, it would get bought out of bankruptcy by someone. It's
> not just defence, it's also offence. Suppose the new owner wanted to
> make a business model of suing others (à la McHardy)? However, these
> are all hypotheticals. The main reason you might want to own your own
> copyrights is to have a say in enforcing them.
FWIW Red Hat lets its developers keep copyright to the code they write.
It's in the employment agreement.
-- Andy
prev parent reply other threads:[~2016-08-30 1:28 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
2016-08-29 23:17 ` Jiri Kosina
2016-08-29 23:20 ` James Bottomley
2016-08-30 1:28 ` Andy Grover [this message]
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=d3c2d35e-3321-a678-0aba-45e7802771e8@redhat.com \
--to=agrover@redhat.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=rostedt@goodmis.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