
From nobody Fri Dec 23 08:33:27 2016
Return-Path: <phoffman@imc.org>
X-Original-To: ietf-and-github@ietfa.amsl.com
Delivered-To: ietf-and-github@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07C741298AA for <ietf-and-github@ietfa.amsl.com>; Fri, 23 Dec 2016 08:33:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[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 nCHr52NYbi5F for <ietf-and-github@ietfa.amsl.com>; Fri, 23 Dec 2016 08:33:24 -0800 (PST)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C030C1296AC for <Ietf-and-github@ietf.org>; Fri, 23 Dec 2016 08:33:21 -0800 (PST)
Received: from [10.32.60.100] (50-1-51-163.dsl.dynamic.fusionbroadband.com [50.1.51.163]) (authenticated bits=0) by mail.proper.com (8.15.2/8.14.9) with ESMTPSA id uBNGWfpg043337 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <Ietf-and-github@ietf.org>; Fri, 23 Dec 2016 09:32:42 -0700 (MST) (envelope-from phoffman@imc.org)
X-Authentication-Warning: mail.proper.com: Host 50-1-51-163.dsl.dynamic.fusionbroadband.com [50.1.51.163] claimed to be [10.32.60.100]
From: "Paul Hoffman" <phoffman@imc.org>
To: Ietf-and-github@ietf.org
Date: Fri, 23 Dec 2016 08:33:23 -0800
Message-ID: <62D2E925-F20D-4DAC-8954-7F66AAB9DC09@imc.org>
References: <148250741312.16852.14743474459827703109.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.6r5319)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/yd9XD-tAct54aE9q4uitMf9apwk>
Subject: [Ietf-and-github] Fwd: License File for Open Source Repositories
X-BeenThere: ietf-and-github@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discussion of using GitHub in IETF activities, particularly for Working Groups" <ietf-and-github.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-and-github>, <mailto:ietf-and-github-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-and-github/>
List-Post: <mailto:ietf-and-github@ietf.org>
List-Help: <mailto:ietf-and-github-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-and-github>, <mailto:ietf-and-github-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Dec 2016 16:33:26 -0000

Of interest to this mailing list. Please send all responses that you 
want acted on to the IESG, but it's fine to discuss them here as well.

Forwarded message:

> From: IESG Secretary <iesg-secretary@ietf.org>
> To: IETF Announcement List <ietf-announce@ietf.org>
> Cc: iesg@ietf.org, ietf@ietf.org
> Subject: License File for Open Source Repositories
> Date: Fri, 23 Dec 2016 07:36:53 -0800
>
> 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.

