ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
	Jiri Kosina <jikos@kernel.org>,
	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: Tue, 30 Aug 2016 07:43:00 +0200	[thread overview]
Message-ID: <1472535780.4249.4.camel@sipsolutions.net> (raw)
In-Reply-To: <1472498570.2376.44.camel@HansenPartnership.com>

On Mon, 2016-08-29 at 12:22 -0700, James Bottomley wrote:

> I suspect the eventual contract may look different. 

Yes, I'm sure it would. But getting $employer to accept it would be
similar, I'd assume.

> The problem in Europe is that the concept of ownership of the work is
> usually tied to the moral rights, so you can't give it up (even if
> you give up effective ownership when you sign away the economic
> rights).  In the US negotiation is definitely over ownership and what
> you usually end up with is so called undivided partial ownership,
> which gives either party full rights to enforce and sublicense.   I
> think, although never having had to negotiate this type of agreement
> in europe I'm not really experienced, that you'd need to negotiate to
> the point where each party has a non-exclusive licence with the right
> to sublicense to have some sort of equivalence.
> 
> Is there someone who's done this in Europe?
> 

I'm not aware.

I suspect the agreement text would end up being similar to the FSFE's
FLA (https://fsfe.org/activities/ftf/FLA.en.pdf), with key differences
being around the grant of rights (assuming $employer wants broader
rights than the FSFE here.)

In the US case, I'd assume that there would also be a broader license
granted to the employer than the open-source license governing the work
in question?

johannes

  parent reply	other threads:[~2016-08-30  5:43 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 [this message]
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=1472535780.4249.4.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox