FW: License File for Open Source Repositories

IETF Chair <chair@ietf.org> Wed, 04 January 2017 16:20 UTC

Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1574512963A; Wed, 4 Jan 2017 08:20:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level:
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R9Ympj2nf5eI; Wed, 4 Jan 2017 08:20:27 -0800 (PST)
Received: from [10.30.0.120] (unknown [83.150.71.93]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id BC8E6129630; Wed, 4 Jan 2017 08:20:26 -0800 (PST)
Subject: FW: License File for Open Source Repositories
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: text/plain; charset="windows-1252"
From: IETF Chair <chair@ietf.org>
In-Reply-To: <148250741312.16852.14743474459827703109.idtracker@ietfa.amsl.com>
Date: Wed, 04 Jan 2017 18:20:22 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <1EB0F8AB-6828-4A00-B157-E80CE86B7A7C@ietf.org>
References: <148250741312.16852.14743474459827703109.idtracker@ietfa.amsl.com>
To: IETF Discussion Mailing List <ietf@ietf.org>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SnI1oXZRqgp0w9bfnXHB8BXgEDs>
Cc: IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: IESG <iesg@ietf.org>, IETF Discussion Mailing List <ietf@ietf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jan 2017 16:20:31 -0000

With the holidays over, this is a re-send of the request to
review the suggested license file.

Jari

----

> 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.
>