IETF Logo Mail Archive

Re: [Ietf-and-github] Comments related to WG Review: GitHub Integration and Tooling (git)

Alissa Cooper <alissa@cooperw.in> Mon, 04 February 2019 19:58 UTC

Return-Path: <alissa@cooperw.in>
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 80213124C04; Mon, 4 Feb 2019 11:58:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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=cooperw.in header.b=qSdE3Z1G; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=AzHZwxtw
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 Lkv4WNdOAIjg; Mon, 4 Feb 2019 11:58:44 -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 31DB8124B0C; Mon, 4 Feb 2019 11:58:44 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 000A621FED; Mon, 4 Feb 2019 14:58:42 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Mon, 04 Feb 2019 14:58:43 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= from:message-id:content-type:mime-version:subject:date :in-reply-to:cc:to:references; s=fm2; bh=DV4CL6YG1ACayx0LVwcq4vL mIYo5LDd2KPl33JkFNhI=; b=qSdE3Z1G+BPmZUtM2FxpXOeVfJDCkuAWazWyH4b ewdaIVClQFjFixV3QmsV2SuSbAdG1WvOj6fIs8Jr31iE25HqIVTU80VUE7c/+Uzb BtDSx1BdVSn8GejPjwi4TGCcEyuNB3dzP0tQWyfCURbkm4q81IFAdC9oQNLwE0A6 +EXSgIHSD8bAA6a1iK9RASETDl+bFcs//A0G4TD22ivGi9TNW+ABy0dlkdkzDgXd z5QLwFrIBK9FZHta01tR9bRuk2syCEkFXDoctq4gOL/+oTewz7ULZdErdVZRQ5Y3 C6IYdq4I2oLSD7m14Yn2h0ImYDkhum4A3t3ga3fm/bviPvA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=DV4CL6 YG1ACayx0LVwcq4vLmIYo5LDd2KPl33JkFNhI=; b=AzHZwxtw5ESdvrFQrX0OwF EIvI4MbZLBswjAiu2cnVLE8DiH5gakhFeL8WUyWo4G7Lobf5EnQUQLxsumVxoyZz RhLe+7GM+AwRblTrtlQyijAitd4LZJhXvbSVlHj6UsrNvWIUTV3+mfPmPsXvRBzk pIrdCPc4vzgoKWV45IE7F/PNRWlB6E2jR+PZbbyiAwjq3FFnF4S+lbB6qwdzUiw9 Px8dhctu+oD/Zxo2xsM1o53C/+Y+o+VnNMHwao0JptkL7jmov7RaLYQw0UX8xR6J ZSn1MQUGS3oWEWgefhZJS9sx5OViiwbcyb98ZU+lya8dXJTVx8bg6neg5Zuk/Uvg ==
X-ME-Sender: <xms:cplYXKYGNpF_aAA3_BhpS1eCstXBzqBWwdw98RV6RAk-FZruBnIjAA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrkeeggddufedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfquhhtnecuuegrihhlohhuthemucef tddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefhkfgtggfuff gjvfhfofesrgdtmherhhdtjeenucfhrhhomheptehlihhsshgrucevohhophgvrhcuoegr lhhishhsrgestghoohhpvghrfidrihhnqeenucffohhmrghinhepghhithhhuhgsrdgtoh hmpdhivghtfhdrohhrghenucfkphepudejfedrfeekrdduudejrdejudenucfrrghrrghm pehmrghilhhfrhhomheprghlihhsshgrsegtohhophgvrhifrdhinhenucevlhhushhtvg hrufhiiigvpedt
X-ME-Proxy: <xmx:cplYXHNAbeYpFTlAHoOQoRuobAQX87qPCyvfbF4YO8xhnruz5fagfA> <xmx:cplYXDyuGG5KiztEssaGFELPsA0Shxbtm_AzIZppJi1uXM6attOd2w> <xmx:cplYXIBBwVKEWqkZe7V3zlP6vMeNo4XV48KXiJnRolgsVSbkDOdLvQ> <xmx:cplYXI55HmZkpTfcZSGUcFu4p0t7hzxUpZEPIjheGqoNpsncMkTqyg>
Received: from rtp-vpn6-666.cisco.com (unknown [173.38.117.71]) by mail.messagingengine.com (Postfix) with ESMTPA id 052DEE436D; Mon, 4 Feb 2019 14:58:41 -0500 (EST)
From: Alissa Cooper <alissa@cooperw.in>
Message-Id: <B6B17533-2CB2-4487-A44C-E8F7273866FA@cooperw.in>
Content-Type: multipart/alternative; boundary="Apple-Mail=_2A0D97E7-DB63-4C23-9430-C77CDE936470"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Mon, 04 Feb 2019 14:58:40 -0500
In-Reply-To: <CY4PR22MB0983FB4E8612B237C85DF2D8DA900@CY4PR22MB0983.namprd22.prod.outlook.com>
Cc: Alvaro Retana <aretana.ietf@gmail.com>, Eric Rescorla <ekr@rtfm.com>, "Eric Vyncke (evyncke)" <evyncke@cisco.com>, IESG <iesg@ietf.org>, "lloyd.wood@yahoo.co.uk" <lloyd.wood@yahoo.co.uk>, Mike Bishop <mbishop@evequefou.be>
To: "ietf-and-github@ietf.org" <ietf-and-github@ietf.org>
References: <1589093219.3690074.1548676152864@mail.yahoo.com> <39382410-D962-4255-BFD1-8F222F742B1A@cooperw.in> <63798F14-8167-4F4D-B294-64A6379E6C65@cisco.com> <CABcZeBNCRE+eVRVyFA9UwyQoV8fvPMTL=wNEKK4tJtM+eUj-0A@mail.gmail.com> <CAMMESsz=+1_dhY-_DqHTRbcsyG2NS_MS8DaAC0=9z57Swp25Dg@mail.gmail.com> <CY4PR22MB0983FB4E8612B237C85DF2D8DA900@CY4PR22MB0983.namprd22.prod.outlook.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/HhQaNLRknBsYLtUqkpTelxvJqpU>
Subject: Re: [Ietf-and-github] Comments related to WG Review: GitHub Integration and Tooling (git)
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 Feb 2019 19:58:46 -0000

I made a suggested addition in response to this thread so that is clear what is and is not in scope: https://github.com/martinthomson/ietf-git-charter/pull/1/files

Thoughts?

Alissa

> On Jan 30, 2019, at 5:28 PM, Mike Bishop <mbishop@evequefou.be> wrote:
> 
> “…possibility to deal with variants after the initial work is done” sounds an awful lot like a recharter.
>  
> I’m inclined to think that charters don’t need to discuss what will happen after a future recharter, but there is some precedent for doing so.  In QUIC’s charter, for example:  “Upon completion of [HTTP], additional protocols may be added by updating this charter to include them.”
>  
> From: Ietf-and-github <ietf-and-github-bounces@ietf.org <mailto:ietf-and-github-bounces@ietf.org>> On Behalf Of Alvaro Retana
> Sent: Thursday, January 31, 2019 2:51 AM
> To: Eric Rescorla <ekr@rtfm.com <mailto:ekr@rtfm.com>>; Eric Vyncke (evyncke) <evyncke@cisco.com <mailto:evyncke@cisco.com>>
> Cc: ietf-and-github@ietf.org <mailto:ietf-and-github@ietf.org>; Alissa Cooper <alissa@cooperw.in <mailto:alissa@cooperw.in>>; IESG <iesg@ietf.org <mailto:iesg@ietf.org>>; lloyd.wood@yahoo.co.uk <mailto:lloyd.wood@yahoo.co.uk>
> Subject: Re: [Ietf-and-github] Comments related to WG Review: GitHub Integration and Tooling (git)
>  
> On January 29, 2019 at 4:09:09 PM, Eric Rescorla (ekr@rtfm.com <mailto:ekr@rtfm.com>) wrote:
> While the name of the mailing list is not really important per se, I also find weird to explicitly specify ‘Github’ in the charter rather than ‘Git’ or ‘Github-like’.
> Well, this stuff would work for anything that's very close to Github, but I don't want us to spend a lot of time dealing with all the variant Github-type thing.
> Thinking out loud:  Is there a way to generalize the charter to deal with Github-type things, while having the WG explicitly focus on Github initially?  IOW, the deliverables would be focus on Github, with the possibility to deal with variants once the initial work is done.
> 
> My 1c.
> 
> Alvaro.
> 
>  
> _______________________________________________
> Ietf-and-github mailing list
> Ietf-and-github@ietf.org <mailto:Ietf-and-github@ietf.org>
> https://www.ietf.org/mailman/listinfo/ietf-and-github <https://www.ietf.org/mailman/listinfo/ietf-and-github>

v2.23.0 | Report a Bug | By Email