IETF Logo Mail Archive

Re: [Ietf-and-github] Closing issues

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 02 November 2019 02:22 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 507CA12081A for <ietf-and-github@ietfa.amsl.com>; Fri, 1 Nov 2019 19:22:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, 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 zBfzasoZUQzG for <ietf-and-github@ietfa.amsl.com>; Fri, 1 Nov 2019 19:22:21 -0700 (PDT)
Received: from mail-pf1-x432.google.com (mail-pf1-x432.google.com [IPv6:2607:f8b0:4864:20::432]) (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 412C3120077 for <ietf-and-github@ietf.org>; Fri, 1 Nov 2019 19:22:20 -0700 (PDT)
Received: by mail-pf1-x432.google.com with SMTP id z4so2185222pfn.12 for <ietf-and-github@ietf.org>; Fri, 01 Nov 2019 19:22:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=HfnD+PO7xhfPlRDxHivG/0TaoyJYyS650EyrCmsvfzE=; b=kddDdbpaBO8zafhzwC/pqueCGzgg+cv6qIGXeQl6USHmnXbXXKdvxFJjOWncSQZZPt pI+zyvg+GVOYmioyyRiG/RkK6UwWxAcFY66BmUUNj5RW2pLLyEjKLmyKT3pUHj0uJmtU KVm2WECQSsQbGRwDKYNebV7c2OFEgsAzoKn+ZtswTLQwg7W4+fJi2e5YT9Lyh7nxhJh7 PvhHqMr9ruWB2YhR0PlAQEVMcCS4HjVN9Ef0O3G+m/R2qgFrJerhp2XDHhPJKCukXV0V CNIbSnFj1DK2SjVZa/DRZPbm3bEMjX7yODCP6Fy96A4jWSswSp2UZL9LRrftR/FFt/MY SZ8Q==
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:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=HfnD+PO7xhfPlRDxHivG/0TaoyJYyS650EyrCmsvfzE=; b=VbYzsZppdJURGzdOC1ZCUxkkHKhfrGZy0X8juknu0O3ujbQud21hI2q87xuor8D2aA EmH7liiW+s8Zrvwku6DknLT+3jiEBMUKgF7lYqp1ccYaULA/bWRYrV3UfNKx5YO+ZyAf be87l1ODxr12kHlk55tBeJA4pxYc4UYv4/oFeIMCiewJQLkUDir15RDbOiaf3AugQbJ2 QhD2o9S7VZ4vfmsS4Wv7UkAseeKcbP3EC7cBuZJu/0xzZaZ57LvjugioDA73IgiqgUvi nTvfae+kYdeItVzKzCgnXGKgfrnIwSTpNBshCtSbizJalyuMJmD36EcOSUo/kFG8t/p/ d65w==
X-Gm-Message-State: APjAAAWHgSlMsMfBJQsW11AqStTm5ms8HhYDADyCXjjnLhvgaV0+rHoC tBdfpVDzFIzQK7vQAQft+OusSeHI
X-Google-Smtp-Source: APXvYqzfLhvYY92bcjDD5CBxxJ5NG+6zBdnfTvDbkPfoHUWyYOApkFf2wn1bvoXBgLbvQnMUyocMtw==
X-Received: by 2002:a17:90a:22a6:: with SMTP id s35mr19009885pjc.3.1572661339104; Fri, 01 Nov 2019 19:22:19 -0700 (PDT)
Received: from [192.168.178.30] (46.137.69.111.dynamic.snap.net.nz. [111.69.137.46]) by smtp.gmail.com with ESMTPSA id d5sm9193295pjw.31.2019.11.01.19.22.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 01 Nov 2019 19:22:18 -0700 (PDT)
To: "Joel M. Halpern" <jmh@joelhalpern.com>
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> <1c10b7bd-8580-0ff6-8e3e-0c4e2c48518e@joelhalpern.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <3dbbafe7-43b9-191e-4cc8-ce192c016627@gmail.com>
Date: Sat, 02 Nov 2019 15:22:14 +1300
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: <1c10b7bd-8580-0ff6-8e3e-0c4e2c48518e@joelhalpern.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/r145fYSyOf43W6WdsKcVhz6CL4E>
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 02:22:23 -0000

On 02-Nov-19 14:41, Joel M. Halpern wrote:
> 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.

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

It's already clear in the document that normal IETF process rules
apply, i.e. RFC2418 etc. That certainly implies quite a lot, including
of course that contested decisions are appealable.

Common sense says that editorial issues could be closed by whoever fixes
them, but substantive decisions seem like WG consensus calls. The text says
"Restrictions on closing issues are generally not advisable until a
document has reached a certain degree of maturity."

I'm not sure what that means. Doesn't the fact that a document has been
adopted by the WG mean that it has indeed reached a certain level of
maturity and that future decisions are WG decisions, not author decisions?

Regards
   Brian

> 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
>>
> 
> _______________________________________________
> 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