IETF Logo Mail Archive

Re: [Ietf-and-github] Closing issues

Rob Sayre <sayrer@gmail.com> Sat, 02 November 2019 00:43 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 6CD9C120B63 for <ietf-and-github@ietfa.amsl.com>; Fri, 1 Nov 2019 17:43:26 -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 Wcj6qw3SdaRI for <ietf-and-github@ietfa.amsl.com>; Fri, 1 Nov 2019 17:43:24 -0700 (PDT)
Received: from mail-io1-xd34.google.com (mail-io1-xd34.google.com [IPv6:2607:f8b0:4864:20::d34]) (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 D4FB0120C25 for <ietf-and-github@ietf.org>; Fri, 1 Nov 2019 17:43:22 -0700 (PDT)
Received: by mail-io1-xd34.google.com with SMTP id u8so12713711iom.5 for <ietf-and-github@ietf.org>; Fri, 01 Nov 2019 17:43:22 -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=DNkn1xtUD5axX2iDVM+0IBalOwQ2IP3EBN07ZuYfD5I=; b=ht1mh/zVylfA0FXjoXBtIeTMk3VEWPqbt3QH6oxcSp3z+lnmKLx+X73CStwmB+tWx0 5RcRhTbkBK3fB8zid99FyLb8QqFRK7bybfBuyhl7fiZeoVFsyIYgxrev1LR8xyLySSa2 g2c2fVDXoPQTjM6Q3deSGJu5rTbQ+efpWWFNRObFbHiuJqhvIoe/w594nyhABvqElwxl XBtfFrNjszX3DlRNBvPyG/4hOAvct2+rF93oNYhzcOaHa91uIhf3ZaN04PX5pw39h12m fSTyMbeHRQm6kTKcMWFQCzOFPkgQ5gz3qWjyT/pFz7YS+zTcOdsHF0118x5DHuWbt/GX Ssjw==
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=DNkn1xtUD5axX2iDVM+0IBalOwQ2IP3EBN07ZuYfD5I=; b=BJDqZ9520s5OtJodmp2ymspMTGyPxD/7NKTOfr9oa0gS1NyT5noeIE3MEGaA2JadFG ysjZa280q5OFU6VjT1B8m0CxIWHePwUJ+OvkP15oCZdViEns0oQOOcgCoDb9ILi0MLhZ thWTVM+ghuUpnn570XL4pV2cA86pSo/Ebpv3siSLqdabt14HJq/qQtq4+ieFuUKNwxos CkZuSkGMoku9aj67vouwWIGZ58T+5X7vL909FeF6KIlnY/vE0sihCy7LGgDccH87udyZ OerkaIwaXKuuQ375TcOX4Qnk1mGOahvRKZeJrW6sOnt1L+WXdFKG45vINIKYeRuHyXQ2 zT6w==
X-Gm-Message-State: APjAAAUTaSU5z3SWWRYfkpJoZXMLMfvvzf2HNOW1xu3UV0BoOOdUZTt7 puwIk1lp04IKt/6d9q2FDEAjPZJQGULwAxoRQ+Q=
X-Google-Smtp-Source: APXvYqwsJ9arhpn8zLrXhkVjJnfIX1QybkrkR7ATU+FkjXz6qB95ESraT4I0F780D7yZ9RL17V5xhNupsFy/l49dNzY=
X-Received: by 2002:a6b:400e:: with SMTP id k14mr12922901ioa.254.1572655401922; Fri, 01 Nov 2019 17:43:21 -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>
In-Reply-To: <CAChr6SyZoasUYt0BUryppAwHz7JS0ncSGZP-iY-zQTGQAZLLzw@mail.gmail.com>
From: Rob Sayre <sayrer@gmail.com>
Date: Fri, 01 Nov 2019 17:43:10 -0700
Message-ID: <CAChr6Sw+SDCUd_FDPG-z-Lg=T3ZH3YgjBjMzB8A1W3mJsSk2zg@mail.gmail.com>
To: Christopher Wood <caw@heapingbits.net>
Cc: ietf-and-github@ietf.org
Content-Type: multipart/alternative; boundary="00000000000095f5ec0596525e7b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/9UfKNU7dRX4tdicfzZ44Ik6AGHk>
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 00:43:26 -0000

On Fri, Nov 1, 2019 at 5:08 PM Rob Sayre <sayrer@gmail.com> wrote:

> On Fri, Nov 1, 2019 at 5:07 PM Christopher Wood <caw@heapingbits.net>
> wrote:
>
>> On Fri, Nov 1, 2019, at 5:00 PM, Rob Sayre wrote:
>> > Hi,
>> >
>> > This one happened to me today: an editor unilaterally closed a github
>> > issue I raised.
>> >
>> > The specific subject matter isn't so important for this list, but I
>> > thought it was an interesting problem: Who should be able to close
>> > issues?
>>
>> This will certainly vary across WGs, so the best we can probably do is as
>> the current text in [1] suggests:
>>
>>    "Chairs MUST provide guidance on who is permitted to close an issue
>> and under what conditions."
>
>
> That seems like a good idea. But should those terms be public?
>

I might add: the ethical considerations here are interesting. I have an
open, if uninteresting, security bug filed on all browser vendors at the
moment (I'm not trying to make money: any bounty will be donated).
WebKit/Apple are primarily at fault, as far as I can tell, but I await a
response.

I don't think that situation signals a problem in itself, as I doubt IETF
participants are reading those security bugs. But I do think it means that
public WG GitHub terms would increase confidence in the IETF.

thanks,
Rob

v2.23.0 | Report a Bug | By Email