All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Jiri Kosina <jikos@kernel.org>, 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:47:51 +0200	[thread overview]
Message-ID: <1472496471.14003.14.camel@sipsolutions.net> (raw)
In-Reply-To: <alpine.LNX.2.00.1608292021550.22028@cbobk.fhfr.pm>

On Mon, 2016-08-29 at 20:32 +0200, Jiri Kosina wrote:

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

*exclusive* license. That's an important distinction.

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

I'm not really sure it matters *that* much. Where you'd negotiate "own
copyright and give $company the regular license (perhaps plus some
extra license to use it as non-GPL, or some covenant not to sue, or
such)" in the US, you'd have to negotiate "own economic rights [...]"
in other jurisdictions.

Much of the negotiation leading up to that will be very similar,
presumably.

johannes

  reply	other threads:[~2016-08-29 18:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-28 17:00 [Ksummit-discuss] [CORE TOPIC] Owning your own copyrights in Linux 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 [this message]
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=1472496471.14003.14.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=jikos@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.