IETF Logo Mail Archive

Re: [Ietf-and-github] Closing issues

"Joel M. Halpern" <jmh@joelhalpern.com> Sat, 02 November 2019 01:42 UTC

Return-Path: <jmh@joelhalpern.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 E2B7F120AC5 for <ietf-and-github@ietfa.amsl.com>; Fri, 1 Nov 2019 18:42:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.679
X-Spam-Level:
X-Spam-Status: No, score=-1.679 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 HIo5SqaGOEPv for <ietf-and-github@ietfa.amsl.com>; Fri, 1 Nov 2019 18:42:09 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D7089120843 for <ietf-and-github@ietf.org>; Fri, 1 Nov 2019 18:41:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 474hcT5SX0z2lHf7 for <ietf-and-github@ietf.org>; Fri, 1 Nov 2019 18:41:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1572658905; bh=emFr/02I5kJrGxV0mtMS+1McKCGipxPldLW3GZeXwiU=; h=Subject:Cc:References:From:Date:In-Reply-To:From; b=o1o/iEmnth8vfl7dyx6JcUNEaGJgZ6qOox6GfEFT7Vat0uef0LkLkd4DD+n3rwqpC t2VpkibOsuYRiFqmtTuad+vN7+denNLbXdH9j/9tJzRyAtgeI35ukLoKj6Pd1qfead Rdo8QJBbvwkdrcmTMRwKeQgmcIeQz7UBRzvsUwwA=
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from [192.168.128.43] (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 474hcT2G3lz2lHdd for <ietf-and-github@ietf.org>; Fri, 1 Nov 2019 18:41:45 -0700 (PDT)
Cc: "ietf-and-github@ietf.org" <ietf-and-github@ietf.org>
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> <CAChr6Sz1pz2JpamQupBDsdTb4ArNJOfVAtZs9BypCnWbaSYEPg@mail.gmail.com> <200DEDAC-A18D-45B4-BC0F-69D8970CED47@akamai.com> <CAChr6Sx7k_WGvkWG-mk-kfV1hwYjUUKb6Rf3sCfihRtD5MO4QA@mail.gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <1c10b7bd-8580-0ff6-8e3e-0c4e2c48518e@joelhalpern.com>
Date: Fri, 01 Nov 2019 21:41:44 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <CAChr6Sx7k_WGvkWG-mk-kfV1hwYjUUKb6Rf3sCfihRtD5MO4QA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/EJLeBf6AszQgR0IJGyUiPMc9OJo>
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:42:11 -0000

Looking at the draft, I think something that would address the issue Rob 
is raising is that the first paragraph of 4.1.2 (about closing issues) 
get an extra sentence.  Along the lines of:
     As noted in section 2.2, this guidance MUST be communicated to and 
agreed by the working groups.

One can argue that this is implicit in the document.  It seems like it 
could help clarity and can't hurt.

Yours,
Joel

On 11/1/2019 9:26 PM, Rob Sayre wrote:
> 
> 
> On Fri, Nov 1, 2019 at 6:15 PM Salz, Rich <rsalz@akamai.com 
> <mailto:rsalz@akamai.com>> wrote:
> 
>       * 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.____
> 
> 
>     Yes, that is a concern that **this** working group is definitely
>     trying to discuss and address.
> 
> 
> Yes, that's why I joined this WG to post my initial message.
> 
> If I really wanted to disagree on a procedural point in a specific WG, I 
> would just fork them and write my own draft.
> 
> thanks,
> Rob
> 
> _______________________________________________
> 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