ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [CORE TOPIC] Owning your own copyrights in Linux
Date: Mon, 29 Aug 2016 08:20:36 +0200	[thread overview]
Message-ID: <CAKMK7uGB3rcpp84aUicCzdhJt8D65=qbRLb9mPPRm_p5yemueA@mail.gmail.com> (raw)
In-Reply-To: <1472403654.2420.29.camel@HansenPartnership.com>

On Sun, Aug 28, 2016 at 7:00 PM, James Bottomley
<James.Bottomley@hansenpartnership.com> wrote:
> Regardless of the outcome of the GPL defence thread, I think we do
> mostly agree that distributed copyright ownership is useful in Linux,
> so I'd like to propose a practical topic on how individual developers
> can achieve this.  I'm afraid this will mostly be US centric (since
> that's where I've worked), but there's no reason we can't use similar
> techniques in other jurisdictions.  I've used three techniques over my
> career:
>
>    1. Invention Disclosure Exceptions
>    2. Separate agreements for Copyright ownership (useful because they can
>       be negotiated even after you sign an employment agreement)
>    3. Modifications to the employment agreement itself.
>
> I can describe each of these and the negotiating process, which will
> give real world examples for others to use.
>
> In many ways, this would also be a good plumbers topic, but I can be
> much more frank in the closed day of kernel summit which is why it
> would be good to have the discussion there.

I'm very much interested in this. I think on top of what you're
proposing we should look into making an official recommendation about
the ks attendee's stance on this, maybe something the TAB could do if
we reach some useful consensus. I've also heard that there's people
working on example contracts/clauses already too, again something the
TAB could engage in after ks. At least I believe this will be a lot
easier to negotiate if we make it a collective effort.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

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

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='CAKMK7uGB3rcpp84aUicCzdhJt8D65=qbRLb9mPPRm_p5yemueA@mail.gmail.com' \
    --to=daniel.vetter@ffwll.ch \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=ksummit-discuss@lists.linuxfoundation.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