From: Michael Richardson <mcr@sandelman.ca>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel\@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Fwd: License File for Open Source Repositories
Date: Sat, 24 Dec 2016 14:21:58 -0500 [thread overview]
Message-ID: <16945.1482607318@obiwan.sandelman.ca> (raw)
In-Reply-To: <CAA93jw7CUxHLnH8XxPXHoAW9ADOi1DGdxSAoOBcHAyDRWOxSeQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 866 bytes --]
Dave Taht <dave.taht@gmail.com> wrote:
> I have no idea what they are trying to do.
When an IETF Internet-draft is on github, it still belongs to the IETF.
As such, someone who submits a pull request, etc. needs to understand that
they are still covered by the IETF Note Well, same as if they posted to the
mailing list, or uploaded a document to ietf.org.
This matters for things like protocol actions that might be covered by
(software) patents.
What the IESG is trying to do, is normalize the text associated with this.
Normal licenses make the lawyers happier, because they can charge more
for doing less work.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2016-12-24 19:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <148250741312.16852.14743474459827703109.idtracker@ietfa.amsl.com>
2016-12-23 16:05 ` Dave Taht
2016-12-23 19:23 ` Marc Petit-Huguenin
2016-12-24 19:21 ` Michael Richardson [this message]
2016-12-23 19:44 dpreed
2016-12-23 20:17 ` Dave Taht
2016-12-23 20:35 ` Marc Petit-Huguenin
2016-12-24 1:35 ` Jonathan Morton
2016-12-24 2:01 ` Marc Petit-Huguenin
2016-12-24 2:05 ` Dave Taht
2016-12-24 20:21 ` Michael Richardson
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16945.1482607318@obiwan.sandelman.ca \
--to=mcr@sandelman.ca \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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