Re: [Ietf-and-github] Closing issues

"Martin Thomson" <mt@lowentropy.net> Mon, 04 November 2019 04:04 UTC

Return-Path: <mt@lowentropy.net>
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 B3F331202A0 for <ietf-and-github@ietfa.amsl.com>; Sun, 3 Nov 2019 20:04:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b=i8oTjOrD; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=loTauYQF
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 z-wlrgPy9RwF for <ietf-and-github@ietfa.amsl.com>; Sun, 3 Nov 2019 20:04:51 -0800 (PST)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8E2D120122 for <ietf-and-github@ietf.org>; Sun, 3 Nov 2019 20:04:50 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 2F78D21BBA for <ietf-and-github@ietf.org>; Sun, 3 Nov 2019 23:04:50 -0500 (EST)
Received: from imap2 ([10.202.2.52]) by compute1.internal (MEProxy); Sun, 03 Nov 2019 23:04:50 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm3; bh=CqQIfGkx+0jc49WzoqBBwHUBVADXwM0 ldxrBUB7lRJw=; b=i8oTjOrDtne2AoxzP/92q4bDQf3SqtW+o2x/h621tJ9x3GJ bTcwG6oNSYmK796aJXG1PmHHnB+ZfMV2p8yqPCh/4JwundY+j70W1CvPopQacoOE XCpgzUQ+rIFEPWuEpN50vw8fYVDQtR1slEPjbR+eMGzXP0OLGnyIQ7KyQxssqKXN SH6wSAr1/+NkEyiyIOpB4fkC2WR7B2Xs6lucWVeTerQURy1wLX544L/WnXhxFojS Ur8xTxZsyszcGBskV2MEB6Qq7XhAdl2gjlGNcILQFlCANQqzBb9m1l03HLuuowE6 6wxgyHdEkbxyIGZaWih6d3w59UljfVs8q66co+A==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=CqQIfG kx+0jc49WzoqBBwHUBVADXwM0ldxrBUB7lRJw=; b=loTauYQFPYuodLaQiY+akA K65vb5Ymq41tmaXjeqvGRLXPrKJu+mk9HwYKy0eFoFLJgw5L7x+IQxJPcjCL49d7 /qA4I3EkvN/DRPq3+LjI3gTrUEDDo+fjD5Ax8OZSLgvfuuKYWrlOnqk9iuAIKDpk kUjPpqg8LgQEBLjt875r7584pXXJV1DX+c3Hym/OHpH4ikaL7hVjxqlKbJiIIXYp HP8UC4YZOGnCCPVYspoI81xXUnyECxproE8uAJDKzHuClO/vDpcyvKiPGIdnLhYa YSnK9llPsg5Okeclr+a4nTaRfKVuNoVEzw7VMGgu2jCsC35MbCSyTPEr1nL6ybXg ==
X-ME-Sender: <xms:YaO_XVd3ClT2w9tu_LQLfGauQz-qytAik9Nt01kpkYrasLHiGrss8A>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudduvddgieegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsehttd ertderredtnecuhfhrohhmpedfofgrrhhtihhnucfvhhhomhhsohhnfdcuoehmtheslhho figvnhhtrhhophihrdhnvghtqeenucffohhmrghinhepghhithhhuhgsrdgtohhmnecurf grrhgrmhepmhgrihhlfhhrohhmpehmtheslhhofigvnhhtrhhophihrdhnvghtnecuvehl uhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:YaO_XZOZdH4idRqb5qfGqUJ7P3zbTAglP8pIK0JUe_HCVqsyMd3Lrg> <xmx:YaO_XcJrbNuZWmYdF2DFKAMdiu1OdwIoa-PKRW8HJV1XhpB2ffGYoQ> <xmx:YaO_XaF2rJABbwkduMvj7oFiGtM7VEvlU1lzShVCEaPuUw_Ka-tv2w> <xmx:YqO_XQLQ2GoKUejU5tQvxAPEyYA3sbuDbahCupp825Z0Reqc5ELBeA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id AA9FAE00A3; Sun, 3 Nov 2019 23:04:49 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-509-ge3ec61c-fmstable-20191030v1
Mime-Version: 1.0
Message-Id: <7f33737d-0bc0-4ac9-b263-d8449b31fd6c@www.fastmail.com>
In-Reply-To: <a1be63d2-67c7-4efe-a0b6-5e18531c0cce@www.fastmail.com>
References: <CAChr6SyD=SE=z=Rvsp11orymu1=DMfvYe3X-xmwdCV8_3ygdJA@mail.gmail.com> <a1be63d2-67c7-4efe-a0b6-5e18531c0cce@www.fastmail.com>
Date: Mon, 04 Nov 2019 15:04:30 +1100
From: Martin Thomson <mt@lowentropy.net>
To: ietf-and-github@ietf.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/lqNNTiNqZotFfyEfXrv_GweRcZA>
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: Mon, 04 Nov 2019 04:04:54 -0000

On Sat, Nov 2, 2019, at 11:06, Christopher Wood wrote:
>    "Chairs MUST provide guidance on who is permitted to close an issue 
> and under what conditions."

I wanted to point out that this is the critical text, however most repositories don't operate under IETF Working Group processes.  Unless the Working Group formally assumes control over a repository, the owner of the repository can do as they please with it.

There is also advice in that document that advises chairs to give editors considerable latitude in how they manage document repositories.  It's only in the case where the issues in a repository serve as a formal record of the state of Working Group process that you need a formal process around the closing of issues.

Opened https://github.com/ietf-gitwg/using-github/issues/27 to look at making the on-ramp a little more ramp-like.  I think that people starting the process probably won't want to concern themselves with formalizing every aspect of the way that tool works.  But once they start depending on some feature, that is when strict rules need to be in place.