From nobody Fri Mar 20 08:56:59 2020 Return-Path: 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 A4E4D3A0BF2; Fri, 20 Mar 2020 08:56:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.897 X-Spam-Level: X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 8_mynVdOeXVw; Fri, 20 Mar 2020 08:56:29 -0700 (PDT) Received: from wp513.webpack.hosteurope.de (wp513.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8223::]) (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 D43CD3A03F8; Fri, 20 Mar 2020 08:56:11 -0700 (PDT) Received: from p200300dee7239a007961e4d1ac1a08c3.dip0.t-ipconnect.de ([2003:de:e723:9a00:7961:e4d1:ac1a:8c3]); authenticated by wp513.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1jFK0A-00052X-RZ; Fri, 20 Mar 2020 16:56:02 +0100 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) From: Mirja Kuehlewind In-Reply-To: Date: Fri, 20 Mar 2020 16:56:00 +0100 Cc: Paul Hoffman , "ietf-and-github@ietf.org" , IESG Content-Transfer-Encoding: quoted-printable Message-Id: References: <158383623742.15390.14960725517486025456@ietfa.amsl.com> <35046BE2-7120-492F-AE1C-DA74FA1AA2C8@icann.org> To: Barry Leiba X-Mailer: Apple Mail (2.3445.104.11) X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1584719789;16b82477; X-HE-SMSGID: 1jFK0A-00052X-RZ Archived-At: Subject: Re: [Ietf-and-github] =?utf-8?b?W0V4dF0gTWlyamEgS8O8aGxld2luZCdzIERp?= =?utf-8?q?scuss_on_draft-ietf-git-github-wg-configuration-06=3A_=28with_D?= =?utf-8?q?ISCUSS_and_COMMENT=29?= 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" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Mar 2020 15:56:37 -0000 I thought Alissa said that they want to update but not before after the = IETF-107 week=E2=80=A6 > On 20. Mar 2020, at 15:56, Barry Leiba = wrote: >=20 > Where are we on this DISCUSS? >=20 > Barry >=20 > On Thu, Mar 12, 2020 at 9:49 AM Mirja Kuehlewind = wrote: >>=20 >> Hi Paul, >>=20 >> See inline. >>=20 >>> On 11. Mar 2020, at 21:36, Paul Hoffman = wrote: >>>=20 >>> Catching up on the rest of Mirja's comments (not already discussed = on this thread) >>>=20 >>>>>> = ---------------------------------------------------------------------- >>>>>> COMMENT: >>>>>> = ---------------------------------------------------------------------- >>>>>>=20 >>>>>> Other questions/comments: >>>>>>=20 >>>>>> 1) Sec 2.3: >>>>>> "There should likely be an API to specify that there were = personnel changes." >>>>>> Inline with the comment in the shepherd write-up, I find this = sentence really >>>>>> unclear. I'm not even sure where the API should be (datatracker = or GitHub) and >>>>>> what is should do? >>>=20 >>> We will change "API" to "ability in the Datatracker=E2=80=9D. >>=20 >> I=E2=80=99m still not sure what exactly is needed here? Can you maybe = explain what the idea is? >>=20 >>>=20 >>>>>>=20 >>>>>> 2) Sec 2.5: >>>>>> "Creating a new repository for an individual draft" >>>>>> This section indicated that also individual drafts could be = maintained within >>>>>> the official wg organization. I'm not sure if that is practical = or desirable: >>>>>> Which individual docs should the chairs allow repos for and which = not? There >>>>>> can be quite a lot of draft in some groups. >>>=20 >>> Some chairs have indicated it is desirable, so the WG thought it = should be possible. >>=20 >> Yes, I think this is a discussion for the other git draft. >>=20 >>>=20 >>>>>>=20 >>>>>> 3) Also sec 2.5: >>>>>> " As an incremental step, this document proposes that there be = a >>>>>> facility in the Datatracker interface to allow an administrator = of an >>>>>> ietf-wg- organization to request the creation of a new >>>>>> repository within that organization for a single document." >>>>>> For -00 version you usually want to have a repo before you submit = it to the >>>>>> datatracker. So a button on the datatracker page of the draft = does not seems >>>>>> too useful... >>>=20 >>> Document authors can tell the WG chairs that they intend to create a = new WG draft. If that happens, the WG chair creates the repo with either = the intended draft name or something semantically relevant, and tells = the document authors before they turn in the -00. (I think this has = already happened in some WGs=E2=80=A6) >>=20 >> That's fine. But the cited text talks about a datatracker interface = for that. Not sure if that is the right approach. >>=20 >>>=20 >>>>>>=20 >>>>>> 4) Sec 2.6: >>>>>> "At the time of this writing this feature was under development." >>>>>> Wasn't there always/for a long time already a feature where you = can add link to >>>>>> external pages? >>>=20 >>> This is currently true for chairs for their WGs, but not for authors = in their document page. >>=20 >> It was not clear to me that this was intended on the document level. = I think that should be clarified. How would that look like? Authors can = add a GitHub repo name or just any URL? Not sure if authors should do = that or only chairs on a per-document basis; might be different for = individual drafts and wg documents. >>=20 >> Thanks! >> Mirja >>=20 >>=20 >>=20 >>>=20 >>> --Paul Hoffman >>=20 >=20 >=20