Re: [Ietf-and-github] Tracking drafts

"Joel M. Halpern" <jmh@joelhalpern.com> Sun, 02 February 2020 05:25 UTC

Return-Path: <jmh@joelhalpern.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 DFF4712004E for <ietf-and-github@ietfa.amsl.com>; Sat, 1 Feb 2020 21:25:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 ZEWGv-BaaCQA for <ietf-and-github@ietfa.amsl.com>; Sat, 1 Feb 2020 21:25:24 -0800 (PST)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E7C2120041 for <ietf-and-github@ietf.org>; Sat, 1 Feb 2020 21:25:24 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 489KD36fqDz6GDt5; Sat, 1 Feb 2020 21:25:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1580621123; bh=lc/CbBhD27Uxb1DUsEUh7hzT7ttwLhvZdeRY3cqOWA4=; h=Subject:To:References:From:Date:In-Reply-To:From; b=lASqBdja4NfEpX4q/y0PkoLmVxNbMjuo0pHcW9wH1S3mUzGOddSjukzV6ebPTMeU4 Sg7zm6L4r+bEmjHwnoV+rS+uiLV7z8zmX8RGR9qI8V4IbvR5AUcY8P3qT3oQxre2PV LVbcd5eleKOrlKVhLaZA4ZxeJ+H97cdgo/76h554=
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.128.43] (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 489KD337PMz6GD2k; Sat, 1 Feb 2020 21:25:23 -0800 (PST)
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "ietf-and-github@ietf.org" <ietf-and-github@ietf.org>
References: <611506f3-82d4-32e9-5ee2-93e1cd3a6a8a@joelhalpern.com> <0661b222-669f-2904-f7e5-ddbbff5073bd@gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <c8035f5b-6ff8-594a-2527-fece1955bf35@joelhalpern.com>
Date: Sun, 2 Feb 2020 00:25:21 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.4.2
MIME-Version: 1.0
In-Reply-To: <0661b222-669f-2904-f7e5-ddbbff5073bd@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/EnE-ttzxZGRvKsGzpBCwwHerzG8>
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 05:25:25 -0000

I do not see a note giving this advice in the draft that is currently up 
for publication.  I hope I am merely missing something.

Yours,
Joel

On 2/1/2020 10:25 PM, Brian E Carpenter wrote:
> 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
>