From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Fwd: License File for Open Source Repositories
Date: Fri, 23 Dec 2016 08:05:55 -0800 [thread overview]
Message-ID: <CAA93jw7CUxHLnH8XxPXHoAW9ADOi1DGdxSAoOBcHAyDRWOxSeQ@mail.gmail.com> (raw)
In-Reply-To: <148250741312.16852.14743474459827703109.idtracker@ietfa.amsl.com>
I have no idea what they are trying to do.
---------- Forwarded message ----------
From: IESG Secretary <iesg-secretary@ietf.org>
Date: Fri, Dec 23, 2016 at 7:36 AM
Subject: License File for Open Source Repositories
To: IETF Announcement List <ietf-announce@ietf.org>
Cc: iesg@ietf.org, ietf@ietf.org
The IESG has observed that many working groups work with open source
repositories even for their work on specifications. That's great, and
we're happy to see this development, as it fits well the working style
of at least some of our working groups. This style is also likely to be
more popular in the future.
As always, we'd like to understand areas where we can either be helpful
in bringing in some new things such as tooling, or where we need to
integrate better between the repository world and the IETF process. As
an example of the latter, we're wondering whether it would be helpful to
have a standard boilerplate for these repositories with respect to the
usual copyright and other matters. The intent is for such text to be
placed in a suitable file (e.g., "CONTRIBUTING"), probably along with
some additional information that is already present in these files in
many repositories. The idea is that people should treat, e.g., text
contributions to a draft-foo.xml in a repository much in the same way as
they treat text contributions on the list, at least when it comes to
copyright, IPR, and other similar issues.
We have worked together with the IETF legal team and few key experts
from the IETF who are actively using these repositories, and suggest the
following text.
We're looking to make a decision on this matter on our January 19th,
2017 IESG Telechat, and would appreciate feedback before then. This
message will be resent after the holiday period is over to make sure it
is noticed. Please send comments to the IESG (iesg@ietf.org) by 2017-01-17.
The IESG
——
This repository relates to activities in the Internet Engineering Task
Force(IETF). All material in this repository is considered Contributions
to the IETF Standards Process, as defined in the intellectual property
policies of IETF currently designated as BCP 78
(https://www.rfc-editor.org/info/bcp78), BCP 79
(https://www.rfc-editor.org/info/bcp79) and the IETF Trust Legal
Provisions (TLP) Relating to IETF Documents
(http://trustee.ietf.org/trust-legal-provisions.html).
Any edit, commit, pull-request, comment or other change made to this
repository constitutes Contributions to the IETF Standards Process. You
agree to comply with all applicable IETF policies and procedures,
including, BCP 78, 79, the TLP, and the TLP rules regarding code
components (e.g. being subject to a Simplified BSD License) in
Contributions.
--
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org
next parent reply other threads:[~2016-12-23 16:05 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 [this message]
2016-12-23 19:23 ` Marc Petit-Huguenin
2016-12-24 19:21 ` Michael Richardson
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=CAA93jw7CUxHLnH8XxPXHoAW9ADOi1DGdxSAoOBcHAyDRWOxSeQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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