From: Karen Sandler <karen@sfconservancy.org>
To: ksummit-discuss@lists.linuxfoundation.org
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [Ksummit-discuss] [CORE TOPIC] Owning your own copyrights in Linux
Date: Mon, 29 Aug 2016 15:51:47 -0400 [thread overview]
Message-ID: <1472500307.4534.66.camel@localhost.localdomain> (raw)
In-Reply-To: <1472499769.4534.59.camel@localhost.localdomain>
On Mon, 2016-08-29 at 15:42 -0400, Karen Sandler wrote:
> This has all been quite a discussion!
Apologies, my reply was for the other thread that inspired this one (I
already reposted my email in the right place in the other thread for
archival purposes). To comment briefly on this thread, I think the
session James proposed is important and developers should endeavor to
keep their own copyrights where that makes sense.
If I'm around, I'd be happy to participate and talk about Conservancy's
ContractPatch [1] initiative and if not, I hope attendees get in touch
to collaborate!
karen
[1] https://sfconservancy.org/blog/2016/aug/04/everything-is-negotiable/
next prev parent reply other threads:[~2016-08-29 19:51 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
2016-08-29 19:42 ` Karen Sandler
2016-08-29 19:51 ` Karen Sandler [this message]
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=1472500307.4534.66.camel@localhost.localdomain \
--to=karen@sfconservancy.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=ksummit-discuss@lists.linuxfoundation.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