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 12:16:15 -0400	[thread overview]
Message-ID: <20160829121615.25e5ddce@gandalf.local.home> (raw)
In-Reply-To: <1472486062.2376.26.camel@HansenPartnership.com>

On Mon, 29 Aug 2016 08:54:22 -0700
James Bottomley <James.Bottomley@HansenPartnership.com> wrote:


> The rest of this is a bit offtopic (it would be on topic in the GPL

Sorry for hijacking your thread ;-)

> defence thread).  However, all I will say is that at the moment, if you
> don't own copyrights on your own contributions to Linux (and if you
> took no actions to make this happen, you likely don't), you have no
> legal standing in any GPL enforcement and a court would likely not even
> bother listening to your opinion.

Personally, I have a small amount of copyrights in the kernel that were
done while I was self employed. But a lot more belong to my current
employer. I have mixed feelings about trying to own those. One, I trust
my current employer with those copyrights, and two, they paid me to do
that code. It was never done "on my own time". I don't feel right
trying to claim copyright for code I was paid for, even if it was all
my idea to create.

But that may not be the case in the future, and I would like to know my
options.

-- Steve

  reply	other threads:[~2016-08-29 16:17 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 [this message]
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

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=20160829121615.25e5ddce@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