ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Jiri Kosina <jikos@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	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 20:32:21 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LNX.2.00.1608292021550.22028@cbobk.fhfr.pm> (raw)
In-Reply-To: <20160829121615.25e5ddce@gandalf.local.home>

On Mon, 29 Aug 2016, Steven Rostedt wrote:

> 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.

Just for the sake of completness, the situation is quite dramatically 
different in US (where the jurisdiction system is based on common law, 
which means that employer indeed owns the copyright in work created by 
employees), whereas in civil law systems, it's usually legally impossible 
to assign the moral rights away from the actual person creating the work 
(the employer just usually owns a licence to the economic rights).

If there is any kind of session at KS about this matter, this aspect 
should be taken into account.

Thanks,

-- 
Jiri Kosina
SUSE Labs

  reply	other threads:[~2016-08-29 18:32 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 [this message]
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=alpine.LNX.2.00.1608292021550.22028@cbobk.fhfr.pm \
    --to=jikos@kernel.org \
    --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