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

Erik Kline <ek.ietf@gmail.com> Thu, 12 March 2020 15:21 UTC

Return-Path: <ek.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 0AE1F3A0A6C for <ietf-and-github@ietfa.amsl.com>; Thu, 12 Mar 2020 08:21:09 -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, HTML_MESSAGE=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 4zF1xX5TLpCF for <ietf-and-github@ietfa.amsl.com>; Thu, 12 Mar 2020 08:21:07 -0700 (PDT)
Received: from mail-oi1-x243.google.com (mail-oi1-x243.google.com [IPv6:2607:f8b0:4864:20::243]) (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 2C0643A0789 for <ietf-and-github@ietf.org>; Thu, 12 Mar 2020 08:21:07 -0700 (PDT)
Received: by mail-oi1-x243.google.com with SMTP id d62so5796125oia.11 for <ietf-and-github@ietf.org>; Thu, 12 Mar 2020 08:21:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=LMPXdz+QZsBfMfVJ+BZ6w5ESOp8see0yedy+UQp3pFA=; b=kq9+uSQ65t73jot3CLu4Slza1pFk0Kz4O492lv+bQOFZNOmP6uNoHFyYjRYBuGLUJk SxzsMvt2CqsndoLuRB6Zuxm4MaNTqauWU+CuF6s14tENvxEDGICtXGWoc1H3rrVgPggE LJsUKnX8neiq6TXTr1AmlcQ4j1K8RnqBFiFePFTS9e/r7eB1YciZ4wvUvpjbS2u1zBm+ DuSv2Ho+44K2GB+hDysLgIP9Gbz+mcj4yB8hYVDhKH4ZX7Y1g27i+C9wFT6mgHsPISop 79MXDkbiJ90nqDiXBYxYycal8Ng6SELeU6Nu1iUTNAwKy9vrOm4Mw7M3926l4Zn7SN29 VOog==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=LMPXdz+QZsBfMfVJ+BZ6w5ESOp8see0yedy+UQp3pFA=; b=FcrLkI/TjUdjnRfL8X6q+QsHeqC8Z0jv87M3pshMzKgvqUTjHkkvbB8TG7tLaIXUpr FaDr53fKcSLCY8LMw0k527LxAiJK0uDu2zDbOzmPzr9BSm2Vfkhx2Zdx2N2dSgmXPtHc CrRg1ONjKsP5SHzYEwTbNTrKm6TCXgzawwz10uGAWUHlrzPqW+jIOv3Zk43x+ZHMLunj QJ30lmxnYeTZChLQ/LTC9n3k3IZYAkbwNHF5p3R6i8qTwZEE5r9AsvNsHe+PAm+/m0WC pdZBWa1lb+ABOdDfsx8DARpTeVCPDUnlmTb0N+kWyDGARYFqhSIYmvA1v26ZfRjs4ld2 JGQw==
X-Gm-Message-State: ANhLgQ0uWcHzw4x+uqLdwtlbMGo3rTYoeN2d7cJ0GP9DAC/aAkXsb7WI JXd2FKMZN8Schvj4rpzLH0noAJbUT3Fz6xMD0vM=
X-Google-Smtp-Source: ADFU+vuLhZ47rRU+PIUJxnA2Fb6hWPtl2VHYNxCbXeRmm0albPVlD8baiMknprOfOFZm0p15ewEe8f5LnIjrzjd0rks=
X-Received: by 2002:aca:3196:: with SMTP id x144mr3100147oix.77.1584026466297; Thu, 12 Mar 2020 08:21:06 -0700 (PDT)
MIME-Version: 1.0
References: <158395281137.1671.933778421064897517@ietfa.amsl.com> <03958aff-0e58-1fc6-8d50-ca38f8221ce6@gmail.com> <CAMMESszjUH86oJaX9QH_tU58DZX9PhSHbmUq=4anE9-iRO0tNg@mail.gmail.com> <B806BAE2-4B47-4BEF-AA3D-169B6B4A978C@cooperw.in> <3B60E587-C8A5-4A2C-8D8F-33FAD96E21CE@cooperw.in> <976d4e5c-a18a-d224-bcf4-567cfc59ea65@gmail.com> <3F2E9415-B1AC-491C-812D-4F91D39030E2@gmail.com> <2470dcfa-ced5-2cbd-3c4a-9bbc82fda74a@gmail.com>
In-Reply-To: <2470dcfa-ced5-2cbd-3c4a-9bbc82fda74a@gmail.com>
From: Erik Kline <ek.ietf@gmail.com>
Date: Thu, 12 Mar 2020 08:20:55 -0700
Message-ID: <CAMGpriXasMdZnzSevX4tVHg-6uY1NXOsHVLuTOr-kN_L0xCeqw@mail.gmail.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Cc: Stewart Bryant <stewart.bryant@gmail.com>, ietf-and-github@ietf.org
Content-Type: multipart/alternative; boundary="000000000000d6ab7c05a0a9e6b5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/YjHUYuLfC1JjK11B6xETRe6LZG0>
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: Thu, 12 Mar 2020 15:21:09 -0000

As someone else said, I think the BCP is not that working groups should use
github but rather that if they do chose to this documents BCP
considerations for how to do so.

(But I do think it's disappointing that github.com [and gitlab.com] seem to
be IPv4-only in 2020.)

On Thu, Mar 12, 2020 at 8:12 AM Alexandre Petrescu <
alexandre.petrescu@gmail.com> wrote:

> I pragmatically say - I disagree with BCP github.com IPv4.
>
> I wait a bit and I might unregister from this group, even though I
> recently gladly accepted the invitation to join.  Things move fast :-)
>
> Alex
>
>
> Le 12/03/2020 à 16:05, Stewart Bryant a écrit :
> > Pragmatism should alway trump perfection
> >
> > - Stewart
> >
> >> On 12 Mar 2020, at 14:23, Alexandre Petrescu <
> alexandre.petrescu@gmail.com> wrote:
> >>
> >> Hi,
> >>
> >> I do not understand - will this become a BCP even though github is
> IPv4-only?
> >>
> >> I am asking, because if it is so, then I think I disagree.
> >>
> >> Alex
> >>
> >>
> >> Le 12/03/2020 à 15:16, Alissa Cooper a écrit :
> >>> WG:
> >>> Based on discussion with Alvaro on the IESG telechat today, I said I
> would take out the RFC Editor note about BCP 25 tomorrow if no one from the
> WG objects. This document will then get its own BCP number when it is
> published.
> >>> Alissa
> >>>> On Mar 12, 2020, at 8:40 AM, Alissa Cooper <alissa@cooperw.in> wrote:
> >>>>
> >>>> I am indifferent about this being part of BCP 25. Brian suggested it
> so I added the note. I’m happy to remove the note if necessary.
> >>>>
> >>>> Alissa
> >>>>
> >>>>
> >>>>> On Mar 11, 2020, at 4:39 PM, Alvaro Retana <aretana.ietf@gmail.com>
> wrote:
> >>>>>
> >>>>> 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.
> >>>>>
> >>>>
> >>>> _______________________________________________
> >>>> Ietf-and-github mailing list
> >>>> Ietf-and-github@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/ietf-and-github
> >>> _______________________________________________
> >>> Ietf-and-github mailing list
> >>> Ietf-and-github@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/ietf-and-github
> >>
> >> _______________________________________________
> >> Ietf-and-github mailing list
> >> Ietf-and-github@ietf.org
> >> https://www.ietf.org/mailman/listinfo/ietf-and-github
> >
>
> _______________________________________________
> Ietf-and-github mailing list
> Ietf-and-github@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-and-github
>