Re: License File for Open Source Repositories

Dave Taht <> Sun, 25 December 2016 01:58 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E3715129731; Sat, 24 Dec 2016 17:58:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 20TbgylEdWjL; Sat, 24 Dec 2016 17:58:28 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:400d:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 60431129721; Sat, 24 Dec 2016 17:58:28 -0800 (PST)
Received: by with SMTP id t184so174597528qkd.0; Sat, 24 Dec 2016 17:58:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=LY0jASLJ+G7fEgc2s2Q5OWeOtIMa1ywRo2Dbh+Qii9E=; b=PF6AiPYITF7haFMrQ1CJeiDlcNRrI8N3DBZYt3BsnKVtURvDULKo0OUG53i5rIz9bV Xe6qPbVXnTHUsX+sEtzJMlzhrQH5KLUakgMG3lplACKSQCHzvRjPuzBmq7ATZ8eWFIrb 5a9ZdgdggYiWpel6YMe3CG6pk7ypyFXN5Bs0yGZofz7WbzxA+M+Glp4Jru0ila4p0Luj MUj+dXrYRzaXBu7N+v9bRJZbgYC0ouhJMPGUjfnnjI1sseuU+kGV3GP+RiCmfLKOBDyD Db88Ce1amb7xU/5H1hlcdFSwtLHVM2w1gMVdLJLU7q+NHsQoR0NHcvg9sW3xrXmYwGEe FuQg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=LY0jASLJ+G7fEgc2s2Q5OWeOtIMa1ywRo2Dbh+Qii9E=; b=HuoaDSVPEkpna4IuxNadYuIX9HOMF0JlSGaV9m0gI21EficvSptqnc+hc2syWlS3o9 +sYNm5icjZ7li7uTATO+fD5MxkOSs/RaESNbLoEShZHV8Mr3BEnc0XOZZTmMj8I7HVCK 9/0x9Ay6d+78Zfl+PA6qxbTiTpY0JkKtIzwuSGfiJKzX0Xh8GAR3gdftexwz1+I/8PuV Bzi8eRryL00tBEVDdRgII1P1842HwIecahDBHIvicgyIy3BR8jAIVOJzj2FgDtUFkg8/ aCXhFgi7G6V+tlLsAdJvc7fHmGXXyKQ/hL3znt/5dn/E86W0YSyAOtHSdMTB8HnLDLo1 PIQw==
X-Gm-Message-State: AIkVDXJvHDemn+AGyUnAZy72sewF6qyWcrAVZp6P5jGIh0BfODMvFQdALmOgbYHFGbX6SSRLzqRXcLfjVUPE9w==
X-Received: by with SMTP id 15mr21322993qkj.118.1482631107438; Sat, 24 Dec 2016 17:58:27 -0800 (PST)
MIME-Version: 1.0
Received: by with HTTP; Sat, 24 Dec 2016 17:58:26 -0800 (PST)
In-Reply-To: <>
References: <> <> <>
From: Dave Taht <>
Date: Sat, 24 Dec 2016 17:58:26 -0800
Message-ID: <>
Subject: Re: License File for Open Source Repositories
To: joel jaeggli <>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <>
Cc: IETF Discussion Mailing List <>, IETF Announcement List <>, The IESG <>
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 25 Dec 2016 01:58:30 -0000

On Sat, Dec 24, 2016 at 2:52 PM, joel jaeggli <> wrote:
> On 12/23/16 12:12 PM, Dave Taht wrote:
>> "open source != BSD". There are better licenses out there - notably
>> apache 2.0 is pretty clear, legally, in places where BSD is not. I am
>> also under the impression that GPLv2 has an implicit patent grant
>> (which would be a real boon in clearing some matters up long before it
>> would ever become an issue).
>> But IANAL. Have you taken this proposed policy up with OSI?
> The statement addresses the use of and obligations of contributors to
> repositories. It does not, nor does it intend to change the licensing
> terms of contributions, present in bcp 78,79 and the TLP.

The non-answer seems to be that OSI has not been consulted.

>> On Fri, Dec 23, 2016 at 7:36 AM, IESG Secretary <> wrote:
>>> 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 ( 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
>>> (, BCP 79
>>> ( and the IETF Trust Legal
>>> Provisions (TLP) Relating to IETF Documents
>>> (
>>> 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!