Re: [Ietf-and-github] Tracking drafts
Brian E Carpenter <brian.e.carpenter@gmail.com> Sun, 02 February 2020 03:25 UTC
Return-Path: <brian.e.carpenter@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 5E925120043
for <ietf-and-github@ietfa.amsl.com>; Sat, 1 Feb 2020 19:25:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, SPF_HELO_NONE=0.001,
SPF_PASS=-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 xBRY_aaTEQob for <ietf-and-github@ietfa.amsl.com>;
Sat, 1 Feb 2020 19:25:22 -0800 (PST)
Received: from mail-pj1-x102a.google.com (mail-pj1-x102a.google.com
[IPv6:2607:f8b0:4864:20::102a])
(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 0FD32120020
for <ietf-and-github@ietf.org>; Sat, 1 Feb 2020 19:25:22 -0800 (PST)
Received: by mail-pj1-x102a.google.com with SMTP id q39so4824060pjc.0
for <ietf-and-github@ietf.org>; Sat, 01 Feb 2020 19:25:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=subject:to:references:from:message-id:date:user-agent:mime-version
:in-reply-to:content-language:content-transfer-encoding;
bh=qzzqIFL5BM/zbFraiZGvUxBIcIPx/vDdzY9T++8iCPw=;
b=KRWclQy4/HuIDn77+WiZ0JXBJijJN3vLYm8jsYbrvQh7sthQJeOxYVtqnf9MXp+dth
KxVGrDFhoXdFdhvrJ2yP/25slKSm5oe1eOuxoxaz4nTILqG4g3NXv6+rRrZrg3Xjpu9+
qpvSm3Jvtl5fwap0TQIi+Q3PTZcnNDyA4N9i3f31/FFM19z47VrTaeMsvnjaQ6qf5wej
qUvVLTUKC0g8nNle6LNi0oM/oAz+HSoWly63WhUDcVBY7wzd0G91u/dLN5j8RD/DCDGH
/Pkg9NzVHb3MQ2q0Fq0nTv+UcbViENWm+OhtVmxyW/t52oRw+2G51FIHKEbOaPMeNiV2
CGww==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:subject:to:references:from:message-id:date
:user-agent:mime-version:in-reply-to:content-language
:content-transfer-encoding;
bh=qzzqIFL5BM/zbFraiZGvUxBIcIPx/vDdzY9T++8iCPw=;
b=efnE3Y/X4NxzjdTIKApAiz613AkSAtyy9P2Ti8C0snzSID6LeodvXI4VmFeErpnAyt
j6fTZ2SZ7rvHePEM7Qy2Q5pKQRl/wGS3SaXumhsXJ3jm/LiYu+j2iT/JTw0O8ZPf89l7
KMkVIk6mTHvWraklsZAPEdgYsN0v0RXdyl6ZXpOgUtlnbdTU1u8g+PA/Zc/2wX5wlNgE
OKIDQ3m+peusIRR5Fvg59ARrDknp/GmgU28uq+f0PwYPSRwNd3ev+jXUEWH7mIACicli
6562y9dkBFYwr94PpEnf4zMeduTTntX8PQvDoMDBw2mUkP3cHN1EPxrKEGZbTDgq/amR
6FYQ==
X-Gm-Message-State: APjAAAW0wfuLCaSVkvEUGzzeLAITh3zw2VYbsjQf2sfaoe8qDnWOf9SY
cxAH96Lz7nHGkdTuBwF87L6KoFBO
X-Google-Smtp-Source: APXvYqzjDqEMBJdtBlCBkHIGzBHBJKls1RgdKO2m+X+TQ4qZbeJOTAF2GPFM32FLdE83/sKNBblV9Q==
X-Received: by 2002:a17:90a:be03:: with SMTP id
a3mr20363722pjs.99.1580613921084;
Sat, 01 Feb 2020 19:25:21 -0800 (PST)
Received: from [192.168.178.30] (88.161.69.111.dynamic.snap.net.nz.
[111.69.161.88])
by smtp.gmail.com with ESMTPSA id p24sm14709911pgk.19.2020.02.01.19.25.19
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Sat, 01 Feb 2020 19:25:20 -0800 (PST)
To: "Joel M. Halpern" <jmh@joelhalpern.com>,
"ietf-and-github@ietf.org" <ietf-and-github@ietf.org>
References: <611506f3-82d4-32e9-5ee2-93e1cd3a6a8a@joelhalpern.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <0661b222-669f-2904-f7e5-ddbbff5073bd@gmail.com>
Date: Sun, 2 Feb 2020 16:25:16 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <611506f3-82d4-32e9-5ee2-93e1cd3a6a8a@joelhalpern.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/Q35pgnIbizUuMPdbpB0U16SLRYk>
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: Sun, 02 Feb 2020 03:25:23 -0000
On 02-Feb-20 10:32, Joel M. Halpern wrote:
> One of the things I do in order to find out about work outside of WGs I
> am involved in is that I read the internet-draft announcements.
>
> Mostly, I am happy to get updates there when new versions of drafts are
> sufficiently stable to be worth checking. So intermediate minor updates
> only being made to the github is not a problem.
>
> But it struck me that if early versions of drafts are only on github,
> and discussed on the WG list, this makes it much harder for me (and
> others who are trying to track work outside their center of attention)
> to know about the work.
>
> I am not sure what the right answer is. It seems that it would help if
> the guidelines encouraged people to post I-Ds as early as practical.
I'd be shocked if that wasn't the case. Otherwise we will get people
posting pre-cooked drafts and blocking discussion by saying it's too late,
we decided that on github.
This is quite similar to the dilemma of when a design team should open
up its thinking to the WG. Too soon is boring for everybody, too late
damages the open process.
Brian
- [Ietf-and-github] Tracking drafts Joel M. Halpern
- Re: [Ietf-and-github] Tracking drafts Brian E Carpenter
- Re: [Ietf-and-github] Tracking drafts Joel M. Halpern
- Re: [Ietf-and-github] Tracking drafts Salz, Rich
- Re: [Ietf-and-github] Tracking drafts Joel M. Halpern
- Re: [Ietf-and-github] Tracking drafts Joel M. Halpern
- Re: [Ietf-and-github] Tracking drafts Salz, Rich
- Re: [Ietf-and-github] Tracking drafts Brian E Carpenter
- Re: [Ietf-and-github] Tracking drafts Fred Baker
- Re: [Ietf-and-github] Tracking drafts Joel M. Halpern
- Re: [Ietf-and-github] Tracking drafts Martin Thomson
- Re: [Ietf-and-github] Tracking drafts Brian E Carpenter
- Re: [Ietf-and-github] Tracking drafts Spencer Dawkins at IETF
- Re: [Ietf-and-github] Tracking drafts Martin Thomson
- Re: [Ietf-and-github] Tracking drafts Brian E Carpenter
- Re: [Ietf-and-github] Tracking drafts Rob Sayre
- Re: [Ietf-and-github] Tracking drafts Salz, Rich
- Re: [Ietf-and-github] Tracking drafts STARK, BARBARA H
- Re: [Ietf-and-github] Tracking drafts Rob Sayre
- Re: [Ietf-and-github] Tracking drafts Martin Thomson
- Re: [Ietf-and-github] Tracking drafts Rob Sayre
- Re: [Ietf-and-github] Tracking drafts Salz, Rich
- Re: [Ietf-and-github] Tracking drafts Spencer Dawkins at IETF
- Re: [Ietf-and-github] Tracking drafts Martin Thomson
- Re: [Ietf-and-github] Tracking drafts Salz, Rich
- Re: [Ietf-and-github] Tracking drafts Rob Sayre
- Re: [Ietf-and-github] Tracking drafts Martin Thomson
- Re: [Ietf-and-github] Tracking drafts Eric Rescorla
- Re: [Ietf-and-github] Tracking drafts STARK, BARBARA H
- Re: [Ietf-and-github] Tracking drafts Rob Sayre
- Re: [Ietf-and-github] Tracking drafts Martin Thomson
- Re: [Ietf-and-github] Tracking drafts Salz, Rich
- Re: [Ietf-and-github] Tracking drafts Christopher Wood