From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qt0-x230.google.com (mail-qt0-x230.google.com [IPv6:2607:f8b0:400d:c0d::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 7D8C23B2A4 for ; Fri, 23 Dec 2016 11:05:56 -0500 (EST) Received: by mail-qt0-x230.google.com with SMTP id d45so42339354qta.1 for ; Fri, 23 Dec 2016 08:05:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-transfer-encoding; bh=z55coZMvS2f5qSqvLoo95Sy41N+xztL0hm71SfzOb3Q=; b=U+BKIsBjwPnjfOVa6Tg92eXxcrtkQ7gQbZjoV5lLIZEnYnep1EqucE0hrrScmFc5B1 3z0z9GhnZ0j3/mvz6ppPVJ9/zg9+zIlMiy8GBgeoX95+5oK8Qtr3JQ7MwBE4HrDm8bYz SZPk/mBm/RQws52FaG98+LfZ1wklC4j9f8iKTMs5CSrtjW4F4erdYun9CWCdKcgt5Aj/ g9tHBJFfqgb58UIDQs01Kj5L2juAALJzcoNEFZXP4/JpWhG/zcIfSzVeQdnDMrgR4f22 dtR0l7GwnB0aKrQoZeQsussdbU/skdZgvrzsY2uWp68EZpMmqz5i6wDGqpWjwiunzfJe 6VKA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-transfer-encoding; bh=z55coZMvS2f5qSqvLoo95Sy41N+xztL0hm71SfzOb3Q=; b=nB6pGeuBWyxyEJsFrGyRTqmmnLSIZJuMcOY2Rsecj1dgukyVfmD7q0Rio9RWyZAHln UXc0+4nktdVxG5JVfPkMoFX0nQQA2wmY0Q6jWs7oESu48iRsBHWSfxbOlViy7FtPUcKl C3Hy00FrlUdKGwmD9CXSlLIB4qmiicRu3rwkh8ydbPWUh+wjMlPNFKMvxd16+noLM+aJ oYRmA7/tS6gCrPjFAuN0lDQpvaUzjXKVn4RyZJSOBuSehy+c6mCCkSCG4A7fS9W/f6tG 2q9bK3RCXEKa0g4PUiYWMXLF0LyNxBOErzK8YVX4ZA64QXupAKDZ898wekMVHypmq8mp yarQ== X-Gm-Message-State: AIkVDXJ+o/C8B9gAIcmOFWNJDi/dPCCsenSa1g8Es6cjgSO5Wl/aN76Rznc869Ro8xKZpSIpZyNrH8uERTq0/A== X-Received: by 10.200.38.39 with SMTP id u36mr16917907qtu.31.1482509155776; Fri, 23 Dec 2016 08:05:55 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.152.197 with HTTP; Fri, 23 Dec 2016 08:05:55 -0800 (PST) In-Reply-To: <148250741312.16852.14743474459827703109.idtracker@ietfa.amsl.com> References: <148250741312.16852.14743474459827703109.idtracker@ietfa.amsl.com> From: Dave Taht Date: Fri, 23 Dec 2016 08:05:55 -0800 Message-ID: To: "cerowrt-devel@lists.bufferbloat.net" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: [Cerowrt-devel] Fwd: License File for Open Source Repositories X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Dec 2016 16:05:56 -0000 I have no idea what they are trying to do. ---------- Forwarded message ---------- From: IESG Secretary Date: Fri, Dec 23, 2016 at 7:36 AM Subject: License File for Open Source Repositories To: IETF Announcement List 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 =E2=80=94=E2=80=94 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. --=20 Dave T=C3=A4ht Let's go make home routers and wifi faster! With better software! http://blog.cerowrt.org