Re: [Ietf-and-github] Tracking drafts

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Thu, 06 February 2020 17:38 UTC

Return-Path: <spencerdawkins.ietf@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 E032512010D for <ietf-and-github@ietfa.amsl.com>; Thu, 6 Feb 2020 09:38:47 -0800 (PST)
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 S1gSdQsm41qr for <ietf-and-github@ietfa.amsl.com>; Thu, 6 Feb 2020 09:38:45 -0800 (PST)
Received: from mail-lj1-x22c.google.com (mail-lj1-x22c.google.com [IPv6:2a00:1450:4864:20::22c]) (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 5D73C1200B9 for <ietf-and-github@ietf.org>; Thu, 6 Feb 2020 09:38:45 -0800 (PST)
Received: by mail-lj1-x22c.google.com with SMTP id q8so7023522ljb.2 for <ietf-and-github@ietf.org>; Thu, 06 Feb 2020 09:38:45 -0800 (PST)
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=IfM5tKDvh+4i/89Nqws4JwKgcXC43DbjCAD/GPIyP68=; b=cNtUvGEuVCA4Ry1z1HUnR4iFNQHZFxSQOwMl1wHB0VU6NU/7NCFNQqlXtHwsSYJxm2 5gTwY7PZRM5rAY5yFI7zWVW6fKzqI3j8O55xIE/X5bduZhjY2ykJhKo2wtVXgZAtOIhp Fy9yUdKojwEI1tIFf6ymrHYH1/wMF+HB0/1Ytn1ruwNnphNI39dQ4+uV5kNkUnpxca2a TEWg5kx3k0f+WoDOmSmL8pWzCJq51x5DRCCjpvnarAoOcS3jfud9chucJiiWVdmym+qa fCFb/jpJCJbCbkW1l2osjqZvhjNr9t5vIeAj9FjmRAN5WdMp/A+8ocumDxmkVx2gSHs5 oVrA==
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=IfM5tKDvh+4i/89Nqws4JwKgcXC43DbjCAD/GPIyP68=; b=ohbsypQEPW2TnC22MmXuHGasLt0ctxAQ7xWdhETBOEuw0X7l9JCW4oQb1KZuPeqAjE 6buX3Oa3O8da+yl3Vpj3guXtL3TqElts0hnB2or3cZK/EzYV2xcgj3gNU0RCeNc1o8xx qGz3jEytIJ494d9dtWYXoKJjA61E+/pDPcerUJYAH/ImHkEvDQQ68sVj4eeGMss1uaAX 5DIR1WklMmaIGWLq62NKpOPXIVsXRGGI44U53X3NNSY8Q4NN5XmCL/CpdOmaTpVKoypm D8qwt0qw7hF3cU5SMMo+PwC3mJcFMllbU+sE/VWk0pgrAdDlxLKfbgLWsSbLM12BuKyt pphQ==
X-Gm-Message-State: APjAAAXyjZ5t0PLjAYIUc6OS2oO96ELuvuTYMYbNqZbiUXhVsTxcl07q FH6g3LvqUPvMcpENiC92lDKga5+w/O//dM/ZBZ9Sis5ix10=
X-Google-Smtp-Source: APXvYqzass65qLhDDEQ8X6eAYZrZ8xpfEsoBztUbHRVGDKfY/my+TXJC7ZXhdzUMUTQ4TSuRBiILyK3lXg953TmjM0A=
X-Received: by 2002:a2e:9d3:: with SMTP id 202mr2762711ljj.60.1581010723476; Thu, 06 Feb 2020 09:38:43 -0800 (PST)
MIME-Version: 1.0
References: <611506f3-82d4-32e9-5ee2-93e1cd3a6a8a@joelhalpern.com> <0661b222-669f-2904-f7e5-ddbbff5073bd@gmail.com> <c8035f5b-6ff8-594a-2527-fece1955bf35@joelhalpern.com> <3E6E2046-E0C7-46B8-859A-F2B0BC5ADF52@akamai.com> <4ae774ff-0cd5-13e5-6d05-620649a32a17@gmail.com> <da3dcddf-383f-411d-92bb-1f77f64aac4b@www.fastmail.com> <6980b3b7-c287-6b17-f7d0-bbbbc20934da@gmail.com>
In-Reply-To: <6980b3b7-c287-6b17-f7d0-bbbbc20934da@gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Thu, 6 Feb 2020 11:38:17 -0600
Message-ID: <CAKKJt-fdk957Zte2ygpvbQgyNh1KpWUJM-fugo2zHd_PA170+g@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Martin Thomson <mt@lowentropy.net>, ietf-and-github@ietf.org
Content-Type: multipart/alternative; boundary="0000000000008f17df059debbeda"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/oxCJJs-mCIN1TI3RrW8JKzu65bo>
Subject: Re: [Ietf-and-github] Tracking drafts
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: Thu, 06 Feb 2020 17:38:48 -0000

FWIW,

On Mon, Feb 3, 2020 at 4:09 PM Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> On 03-Feb-20 20:20, Martin Thomson wrote:
> > On Sun, Feb 2, 2020, at 20:30, Brian E Carpenter wrote:
> >> I think that Joel's point applies more generally, not just to github.
> >
> > This is, I think, a key point.
> >
> >
> https://ietf-gitwg.github.io/using-github/draft-ietf-git-using-github.html#name-internet-draft-publication
> might be expanded to recommend publication of drafts at other times, but I
> have two reasons - on top of the above - that we might not:
> >
> > * This is a document about *working group* procedures.  If we get into
> individual draft management, that's scope creep.
>
> Fair enough. However, I think it is worth making the point somewhere that
> there is an analogy between a subset of participants who use a repo and a
> subset of participants that work as a design team, so the RFC2418
> provisions for design teams should apply.
>
> The more general question (when should a design team or github clique post
> a draft) seems more like a topic for gendispatch.
>

I agree with Martin that saying more than this is scope creep, even if it's
useful to chop off the creepy parts and take them to gendispatch.

I think it IS fair to say "people working on an early version of a draft in
Github is the equivalent of a design team working on an early version of a
draft using private e-mail, so the usual working group practices and
cautions for design teams apply to Github as well", or something like that.

Best,

Spencer


>     Brian
>
> >
> > * I have found that the "link to a Google doc or GitHub repo" pattern
> routinely results in a request for someone to post a draft.  To my mind,
> that has been sufficient thus far.
> >
> > _______________________________________________
> > Ietf-and-github mailing list
> > Ietf-and-github@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf-and-github
> >
>
> _______________________________________________
> Ietf-and-github mailing list
> Ietf-and-github@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-and-github
>