Re: [Ietf-and-github] [Ext] Mirja Kühlewind's Discuss on draft-ietf-git-github-wg-configuration-06: (with DISCUSS and COMMENT)

Barry Leiba <barryleiba@computer.org> Fri, 20 March 2020 14:57 UTC

Return-Path: <barryleiba@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 2055E3A09DF; Fri, 20 Mar 2020 07:57:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.637
X-Spam-Level:
X-Spam-Status: No, score=-1.637 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no 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 8XevZ0j9tBe0; Fri, 20 Mar 2020 07:57:31 -0700 (PDT)
Received: from mail-il1-f175.google.com (mail-il1-f175.google.com [209.85.166.175]) (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 BF16C3A0A58; Fri, 20 Mar 2020 07:56:48 -0700 (PDT)
Received: by mail-il1-f175.google.com with SMTP id h3so5853657ils.3; Fri, 20 Mar 2020 07:56:48 -0700 (PDT)
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:content-transfer-encoding; bh=XZ4YtJqyCyCeJDFdQe8pT2Tul5tlcwOTh7wzmfBxiEc=; b=CvwKlFOWiXUMYQrl2sAqTZvsGCQKj7HUVwutEh5kK+Vyn6//U7Ym1xO9YSnVUKQFtr xWHWlVJ7xkRkSNqsvY2LFaoy18DGSvTZ0NM7tkXv7xbpwFcdmKSg2tE3J4GH3/5uwU22 rfmyPgUKM/4myJnP5UcSqlPEQZ/pVo6PpSUUk+ic4svQrsCIomCyUY342Hyni+Wk6tOx iZHs9b+yjGJruXJv9ecC9hgL4Hc+wy+/lcNkWrXtJfXf/0mjfWE+1UzzDP0vWuwLRv2i 2Aq8EuUcb5AGyTN8u6LayvkyGX98J/w16F8xPplEK9E5hWJ0etmiPe1tKElo2cdEPgyk c+7A==
X-Gm-Message-State: ANhLgQ37zTsJbnCVtfiByvds3I+Y5Ce/mwY//NjFzxUQys63yLviibOL l+643ItqZGnEe8LjJhEyv42b3HL3gvHMyHRBR21W/A==
X-Google-Smtp-Source: ADFU+vuvTv9xkySg5JSG93P4tCd9imnEuAIeJllOAk0S96divr15rvjwl0XtXajkDrOU9aLtQnYINCGs7kElRaYzNtg=
X-Received: by 2002:a92:9107:: with SMTP id t7mr8659384ild.140.1584716207116; Fri, 20 Mar 2020 07:56:47 -0700 (PDT)
MIME-Version: 1.0
References: <158383623742.15390.14960725517486025456@ietfa.amsl.com> <BD37D562-1DAB-49B5-B7B6-A9A041BA3E45@cooperw.in> <FB1F57E6-759D-49FB-A9B1-17AC1909EE01@kuehlewind.net> <35046BE2-7120-492F-AE1C-DA74FA1AA2C8@icann.org> <DF6369D5-83A4-4748-AE46-9CFDD4084DF1@kuehlewind.net>
In-Reply-To: <DF6369D5-83A4-4748-AE46-9CFDD4084DF1@kuehlewind.net>
From: Barry Leiba <barryleiba@computer.org>
Date: Fri, 20 Mar 2020 10:56:35 -0400
Message-ID: <CALaySJLdUrLu3Yq5+8dgqiJFo1SRPMCDWVHMaxYTVUSJ1wAB+Q@mail.gmail.com>
To: Mirja Kuehlewind <ietf@kuehlewind.net>
Cc: Paul Hoffman <paul.hoffman@icann.org>, "ietf-and-github@ietf.org" <ietf-and-github@ietf.org>, IESG <iesg@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/lvRUlShgm6ykg6GU_03U-0ucNko>
Subject: Re: [Ietf-and-github] [Ext] Mirja Kühlewind's Discuss on draft-ietf-git-github-wg-configuration-06: (with DISCUSS and COMMENT)
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: Fri, 20 Mar 2020 14:57:43 -0000

Where are we on this DISCUSS?

Barry

On Thu, Mar 12, 2020 at 9:49 AM Mirja Kuehlewind <ietf@kuehlewind.net> wrote:
>
> Hi Paul,
>
> See inline.
>
> > On 11. Mar 2020, at 21:36, Paul Hoffman <paul.hoffman@icann.org> wrote:
> >
> > Catching up on the rest of Mirja's comments (not already discussed on this thread)
> >
> >>>> ----------------------------------------------------------------------
> >>>> COMMENT:
> >>>> ----------------------------------------------------------------------
> >>>>
> >>>> Other questions/comments:
> >>>>
> >>>> 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?
> >
> > We will change "API" to "ability in the Datatracker”.
>
> I’m still not sure what exactly is needed here? Can you maybe explain what the idea is?
>
> >
> >>>>
> >>>> 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.
> >
> > Some chairs have indicated it is desirable, so the WG thought it should be possible.
>
> Yes, I think this is a discussion for the other git draft.
>
> >
> >>>>
> >>>> 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-<wgname> 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...
> >
> > 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…)
>
> That's fine. But the cited text talks about a datatracker interface for that. Not sure if that is the right approach.
>
> >
> >>>>
> >>>> 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?
> >
> > This is currently true for chairs for their WGs, but not for authors in their document page.
>
> 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.
>
> Thanks!
> Mirja
>
>
>
> >
> > --Paul Hoffman
>