Re: [Ietf-and-github] Alvaro Retana's Discuss on draft-ietf-git-using-github-05: (with DISCUSS and COMMENT)

Alvaro Retana <aretana.ietf@gmail.com> Wed, 11 March 2020 20:40 UTC

Return-Path: <aretana.ietf@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 26E733A0CB7; Wed, 11 Mar 2020 13:40:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, UNPARSEABLE_RELAY=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 s5rQN_WVAmNo; Wed, 11 Mar 2020 13:39:58 -0700 (PDT)
Received: from mail-ed1-x544.google.com (mail-ed1-x544.google.com [IPv6:2a00:1450:4864:20::544]) (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 468943A09CC; Wed, 11 Mar 2020 13:39:58 -0700 (PDT)
Received: by mail-ed1-x544.google.com with SMTP id a20so4612356edj.2; Wed, 11 Mar 2020 13:39:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc:content-transfer-encoding; bh=ySugw6f99OoUo1S+YSzfVibZYeRhwWHpOcuCNPiwxDw=; b=i3pZSfkqwl03Be7TP2lymtm1I1ckNIuea7TN3yZR7D+PX/E1kEnn219SWF8GaVrLwx guj8mexzA6tx1OAfKYhF3z7NRoSVT/ExS75V/rwDb03uBX3fdSFcLfefqNEdN5Xxah8T U5e6cdBxgE6Ga00CJ/gp6vaW6xIAHJHlJ4jaSh++/mgzcPzjchHDO8dNN054aEItiNOk C4dxtGgZybxeTguhdPoj1z1UoO/lwiVmE0KtqMwez24X1jCmAGp093XXKTHKpi+7Ez9d fJcTE5iiwzEXc8nH+/CKOxT4615JrSOzDLmfUhABAp42o8sx9lgwn9Bjf2ZWmUerdOd1 7kUQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc:content-transfer-encoding; bh=ySugw6f99OoUo1S+YSzfVibZYeRhwWHpOcuCNPiwxDw=; b=rixUuHo39OU9n6wSWshAf580GXEs+UvgBEufQRRWK7UJEMSy/xeggoUimfSiNmUhHP 8kp/iTaruRkt0qyZO04l5lf8KwRY08d/RYgEgDWW/KCl77tCpagcpK6lmMvzXuRTrlqD r7CpJia3zvko84mP2+7gyOaMesVS+XY7P9RlVAtqTllQUlub15eqsVZdfulJybgwK4kT WwxOOx1bVkv+CQ+IGKehR5s4TMWz2bo6Ct3uCUitwlQ8UNQ4t8Umz7HWpmqVBOttxvpr PFhU564sXrkW/QrEK2RKtDbayu7x0R9Opi7nrKlvGriajof/mUxFmVhWExGMCiwMknZF V0Og==
X-Gm-Message-State: ANhLgQ1q0M984mdvKVEU4M9Z39J3KnSxoyM9RkU+Mwiw4bmZDsZhI0IL 5Uv6+J8V5JOUeZpSYhuD+6kxXDLG4aFvPHWznbltb4gt
X-Google-Smtp-Source: ADFU+vsYUmbaDP47s1ipwSM3y+Va2ADLq9pZXvPOueUS2+eUM7LHP20XJqHKxXH6rAcXkBkXZalx2H1o6/ypeWay+RA=
X-Received: by 2002:aa7:dc06:: with SMTP id b6mr4850745edu.336.1583959196761; Wed, 11 Mar 2020 13:39:56 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Wed, 11 Mar 2020 13:39:56 -0700
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <03958aff-0e58-1fc6-8d50-ca38f8221ce6@gmail.com>
References: <158395281137.1671.933778421064897517@ietfa.amsl.com> <03958aff-0e58-1fc6-8d50-ca38f8221ce6@gmail.com>
MIME-Version: 1.0
Date: Wed, 11 Mar 2020 13:39:56 -0700
Message-ID: <CAMMESszjUH86oJaX9QH_tU58DZX9PhSHbmUq=4anE9-iRO0tNg@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, The IESG <iesg@ietf.org>
Cc: git-chairs@ietf.org, draft-ietf-git-using-github@ietf.org, Christopher Wood <caw@heapingbits.net>, ietf-and-github@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/eE1_bCShm7pUArpIMTisK8Cw5Z8>
Subject: Re: [Ietf-and-github] Alvaro Retana's Discuss on draft-ietf-git-using-github-05: (with DISCUSS and COMMENT)
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: Wed, 11 Mar 2020 20:40:02 -0000

On March 11, 2020 at 3:32:58 PM, Brian E Carpenter wrote:


Brian:

Hi!


> > ----------------------------------------------------------------------
> > DISCUSS:
> > ----------------------------------------------------------------------
> >
> > This is a process DISCUSS. I don't believe the status of this document as a
> > BCP belonging to BCP 25 was discussed in the WG or with the IETF community.
> >
> > The Charter for the git WG only explicitly mentions BCP 9:
> >
> > The documents produced by this group will not alter the Internet Standards
> > Process (BCP 9). They will describe how to work within it. Whether working
> > groups choose to use GitHub or the documented policies to support their
> > work will remain entirely at their discretion.
> >
> > However, including this document as a part of BCP 25 (IETF Working Group
> > Guidelines and Procedures) results in the interpretation that it represents
> > consensus on how WGs should proceed -- and not that the decision "to use
> > GitHub or the documented policies...[is]...entirely at their discretion."
>
> Would a sentence to that effect in the Abstract and Introduction help?

It wouldn't hurt, but it also doesn't help with my issue: having this
document be part of BCP 25.



...
> > IOW, both (1) the process of reaching the conclusion that this document
> > belongs in BCP 25, and (2) the concept that this document would be part of
> > BCP 25, are the subject of my DISCUSS. I would like for the IESG to discuss
> > this topic.
>
> Have things changed? In the old days this question (which BCP number?) was
> typically left to the discretion of the RFC Editor, possibly with a bit of
> discussion with the AD. I certainly don't object to community discussion, of
> course (and we did do that in the case of BCP 101 recently).

No, I don't think things have changed.  In this case, the AD added a
note to the RFC Editor requesting them to "append this document to BCP
25 at the time of publication."

https://datatracker.ietf.org/doc/draft-ietf-git-using-github/writeup/


However, I believe that BCP 25 is a special case because it applies
directly to WG operation.  The intention of adding documents to it
should (at least) be clear and some discussion should exist.


Thanks!

Alvaro.