IETF Logo Mail Archive

Re: [Ietf-and-github] Propose changing draft-ietf-git-using-github from BCP to Informational

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 13 March 2020 19:20 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 BB2A43A0A81; Fri, 13 Mar 2020 12:20:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 2pbMuBOuSvSf; Fri, 13 Mar 2020 12:20:31 -0700 (PDT)
Received: from mail-pg1-x52a.google.com (mail-pg1-x52a.google.com [IPv6:2607:f8b0:4864:20::52a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC37A3A0A64; Fri, 13 Mar 2020 12:20:30 -0700 (PDT)
Received: by mail-pg1-x52a.google.com with SMTP id b1so5525357pgm.8; Fri, 13 Mar 2020 12:20:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=35jFym2CbRn24MoKImSccLNMKA9Bfxkm5ft+LTTNvTM=; b=r+t+NSZ9xyNVRQvDFyNbp0R9cA5IeVtxdo6TWEP6GAI8XBG3ZjdcemtjpX3sPk2Q/F J5fEykDqX/lbYvEMf14+2ZO6zfV5J4SQlPdLGEVfe9qGDn+IjnsxwNOeLyNnpTl7QRWf WxpilkW35OMK95IDAO0IlTnXk8ErUiEmLiPl4uCTTKYx3+yNtXlQu6NNh3VCxVkgV7Ao 2FDZUAmlr9FfnHcfHA5wrlda8NwENw/lyKknWNB4LVYyErkP/jvl+ruI3Tu9VAGEuGGD 2vDlknSiA32/GTDwdYeN/8LvkP+95+7pzklqpXlCzGeq9wHPff+G7JJLAKmO9oxKvwL4 Q+gQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=35jFym2CbRn24MoKImSccLNMKA9Bfxkm5ft+LTTNvTM=; b=cq1j76VFpBaiSt7BcQpH70YAgx64V+HHhuTqlogvnVB5RBK8GGxbDEq7lditZfyjO6 mJImzOSI5cu8XTXHStAMEZ5hEMfnwCKF7ATMcjkTkoACHCtiPtWFsjpVqq8o5NB2IFD1 h+Xh6CXd/0YuSzyMRiY+V1tMBY+GVLmcBh+pv4nVPR7rNWNgsMRhuPwKdH1pT4towrwd op9TaLOp6kPwzPMYKCococPNxeEfd1HJstNTNgM9BDsYrwa3GK8ijhKQ4tC6fRxN90Zm MrknhhCWW5SOJqHVfX/D/hZA07Q0Afnt5DWbpnn7zM6SKTu5Z1eU+LMW4YKyoIZwxXIj dppg==
X-Gm-Message-State: ANhLgQ2ucPsex5P/z/XzTue1a8GLqhyK1JVCAaLog8sGoGeqxfcx8HBm LlbFtlcr2XgI1qhIRTw1tVrG7mQC
X-Google-Smtp-Source: ADFU+vsyuyVOssGbQwaH7DRwNo1EVENCed54vYDhr5qPMLbT8dk0YCJz7fYrJVnPeEmO9A4xliHHkw==
X-Received: by 2002:aa7:98c9:: with SMTP id e9mr14989194pfm.204.1584127227367; Fri, 13 Mar 2020 12:20:27 -0700 (PDT)
Received: from [192.168.178.30] ([165.84.25.143]) by smtp.gmail.com with ESMTPSA id e3sm26131005pgm.15.2020.03.13.12.20.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 13 Mar 2020 12:20:19 -0700 (PDT)
To: Christopher Wood <caw@heapingbits.net>, ietf-and-github@ietf.org
Cc: "draft-ietf-git-using-github@ietf.org" <draft-ietf-git-using-github@ietf.org>
References: <07e5360a-5b55-4346-b2b4-382b9242e383@www.fastmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <bc332990-114f-b063-da16-556d2c8715e4@gmail.com>
Date: Sat, 14 Mar 2020 08:20:15 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <07e5360a-5b55-4346-b2b4-382b9242e383@www.fastmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/uukHpWbBmxT60feqDDg7rY7YWWA>
Subject: Re: [Ietf-and-github] Propose changing draft-ietf-git-using-github from BCP to Informational
X-BeenThere: ietf-and-github@ietf.org
X-Mailman-Version: 2.1.29
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, 13 Mar 2020 19:20:33 -0000

Hi,

I disagree that it is a minor or inconsequential change. It means that it is no longer a set of rules that a WG must follow if they choose to use GitHub. It just becomes some non-binding suggestions.

This has conseqences for the text, starting with the Abstract:

> This document describes best practices ...

needs to be something like

 This document describes suggested guidelines ...

Then delete section 1.5 and lower-case all the RFC2119 keywords, to avoid confusion.

More seriously, we would lose the normative value of this:

>    In addition to Working Group policies, notices on repositories MUST
>    include citations for the IETF Note Well (https://www.ietf.org/about/
>    note-well/).

which really should be mandatory. Also this:

>    All repositories for Working Group documents within the Working Group
>    organization MUST be public.  

I haven't re-read the whole draft. There may be other things as well that are also important and not necessarily implied by RFC2418 already. So I do not agree to the change of proposed status.

Regards
   Brian Carpenter

On 14-Mar-20 02:48, Christopher Wood wrote:
> During last call, some folks suggested draft-ietf-git-using-github is better suited as an Informational rather than BCP document. This seems like a minor and inconsequential change, though I'd like to hear from the WG to understand if folks object. To that end, if you disagree with this change, can you please let us know why?
> 
> Thanks!
> Chris
> 
> _______________________________________________
> Ietf-and-github mailing list
> Ietf-and-github@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-and-github
>

v2.23.0 | Report a Bug | By Email