IETF Logo Mail Archive

Re: [Ietf-and-github] Closing issues

Rob Sayre <sayrer@gmail.com> Sat, 02 November 2019 01:09 UTC

Return-Path: <sayrer@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 F1D311200B9 for <ietf-and-github@ietfa.amsl.com>; Fri, 1 Nov 2019 18:09:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 hu5OBPqsnuMu for <ietf-and-github@ietfa.amsl.com>; Fri, 1 Nov 2019 18:09:13 -0700 (PDT)
Received: from mail-il1-x136.google.com (mail-il1-x136.google.com [IPv6:2607:f8b0:4864:20::136]) (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 B32FC12008B for <ietf-and-github@ietf.org>; Fri, 1 Nov 2019 18:09:13 -0700 (PDT)
Received: by mail-il1-x136.google.com with SMTP id y5so10151617ilb.5 for <ietf-and-github@ietf.org>; Fri, 01 Nov 2019 18:09:13 -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=X2DlG6wWObO7FAXsQQUlPS4tTFlRmppxA3FekVh9X1I=; b=DIMIFLX3LF3Brj1GC1qHyW9Gzq1jawto47qeE/gCXOvCNN7YeILV9q76e7BcTjD1zk Hh1gB8yLJSOykX1p9r1Lfo8JkeAiz6uIgrW6ej7WAPBGOc3TIG47bhElFmmoIY015jYL /sgp6VQZzvMyXIml2a8d7KwW0zgc7SdqG6/6MjxVuMTp7qkAWWN2xpsZ/czYs9eV8HkY Xv7BH5J0QVbmv0ilHcf0CS/alF2MFsjhvh0Po0w4QVTcwGPKLkFis4liHtnmdv3hS061 NKxNdgaVwzJocmNFQ2EtivlbWsql+LguumgPFuRS7mgr6hd5YZFyR7H8xcrFCADyK80x 67jA==
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=X2DlG6wWObO7FAXsQQUlPS4tTFlRmppxA3FekVh9X1I=; b=WcUXrd56m/JyCScHdY6IY5WpukS115U12CTB6m7azdKxL3pXZL1CMWWjME9eYh1Hf6 nnlhkkCLLgukaW5ZdWiPD2Ii1SC5o14kVbkqBzx6hRjkickHPW4LXFYp7ZsZ8JK2PyWd kMm6rsUW1Bs1zb7FHcIhnB0Ci60xMC0ApFkHaQmwNXXJ06M14JUXhuIjQfXs0sULrw96 JtgFEednj+bGSTVakxZx3baP4v7/SGm7+3xru+YiVylIPEi7BtXTsF9YS01xJYmwECGJ Sn+YmHAsPebPjYGrG0S6uGSegYYf+uppvYqTBf10/RtHSd7VtxDdnVbEcJdbz4tSGhwX AeuA==
X-Gm-Message-State: APjAAAXPfBc85laMpEPr+675hX8b7VkPd5BqCjYXI2cjKZNLSbX7zX+7 XtTI3qATU0qpj0AWzSLnp2pIy/ONn0bTvUPp1Pk=
X-Google-Smtp-Source: APXvYqwPMAWZDyxLnLc2dyrsJQepXuwX10UBbhgugDWyVsCG165KulBxarT65i7L5UFo0dzJOsTi1rFVQe0E/1/rD4Y=
X-Received: by 2002:a92:8394:: with SMTP id p20mr16187219ilk.73.1572656952931; Fri, 01 Nov 2019 18:09:12 -0700 (PDT)
MIME-Version: 1.0
References: <CAChr6SyD=SE=z=Rvsp11orymu1=DMfvYe3X-xmwdCV8_3ygdJA@mail.gmail.com> <a1be63d2-67c7-4efe-a0b6-5e18531c0cce@www.fastmail.com> <CAChr6SyZoasUYt0BUryppAwHz7JS0ncSGZP-iY-zQTGQAZLLzw@mail.gmail.com> <CAChr6Sw+SDCUd_FDPG-z-Lg=T3ZH3YgjBjMzB8A1W3mJsSk2zg@mail.gmail.com> <9E634E81-48C5-4EDA-B98E-972A7CACF641@akamai.com>
In-Reply-To: <9E634E81-48C5-4EDA-B98E-972A7CACF641@akamai.com>
From: Rob Sayre <sayrer@gmail.com>
Date: Fri, 01 Nov 2019 18:09:01 -0700
Message-ID: <CAChr6Sz1pz2JpamQupBDsdTb4ArNJOfVAtZs9BypCnWbaSYEPg@mail.gmail.com>
To: "Salz, Rich" <rsalz@akamai.com>
Cc: Christopher Wood <caw@heapingbits.net>, "ietf-and-github@ietf.org" <ietf-and-github@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000087dec059652bbf7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/BwyVFY5IUiieeSfbNMNhCbSFo80>
Subject: Re: [Ietf-and-github] Closing issues
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: Sat, 02 Nov 2019 01:09:16 -0000

On Fri, Nov 1, 2019 at 6:02 PM Salz, Rich <rsalz@akamai.com> wrote:

>
>
> *>* But I do think it means that public WG GitHub terms would increase
> confidence in the IETF.
>
>
> I don’t see what github transparency is any different from the
> already-existing mailing list transparency.
>

Hello,

I'm sorry if I was unclear. As far as I know, there are a lot of procedures
around declaring consensus on mailing lists in the IETF.

My concern is that topics can be deemed appropriate for GitHub, and
diverted from a WG mailing list. That might
inappropriately suppress discussion if those issues can then be closed
based on non-public terms in GitHub.

thanks,
Rob

v2.23.0 | Report a Bug | By Email