From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] [CORE TOPIC] Owning your own copyrights in Linux
Date: Sun, 28 Aug 2016 10:00:54 -0700 [thread overview]
Message-ID: <1472403654.2420.29.camel@HansenPartnership.com> (raw)
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.
James
next reply other threads:[~2016-08-28 17:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-28 17:00 James Bottomley [this message]
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
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=1472403654.2420.29.camel@HansenPartnership.com \
--to=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