Re: [Ietf-and-github] Tracking drafts

"Joel M. Halpern" <jmh@joelhalpern.com> Sun, 02 February 2020 20:08 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 AE3441200B1 for <ietf-and-github@ietfa.amsl.com>; Sun, 2 Feb 2020 12:08:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 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, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 HSVZK0aLH9wR for <ietf-and-github@ietfa.amsl.com>; Sun, 2 Feb 2020 12:08:44 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 E3616120033 for <ietf-and-github@ietf.org>; Sun, 2 Feb 2020 12:08:44 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 489hqJ5HPlz1nt41; Sun, 2 Feb 2020 12:08:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1580674124; bh=sdyRjberyyrwVjBy6eftFRi4/hcUNYYX7kA6dZufjI4=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=q7tVdaDvnvH7yJWGoFruSp/Ww/Gi8n8HL5QactSlickDiTscpwzu5nUjUhXAj23bc FJtVScBQ+gb9WTgQppxGqQvAan8+QY408SWeI7EzRnI8dXGOd33sfXzhnBwuhpDVP6 E35o9ICSyz4SFqziNxDq+lynddlBfftlxdXpcqXM=
X-Virus-Scanned: Debian amavisd-new at b2.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 mailb2.tigertech.net (Postfix) with ESMTPSA id 489hqJ1rm9z1nsqh; Sun, 2 Feb 2020 12:08:44 -0800 (PST)
To: Fred Baker <fredbaker.ietf@gmail.com>
Cc: "ietf-and-github@ietf.org" <ietf-and-github@ietf.org>
References: <4ae774ff-0cd5-13e5-6d05-620649a32a17@gmail.com> <92EABB82-5C7E-4C80-9927-BB608B181199@gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <f5a9b402-e708-959a-17fb-6f7fa21cbd9d@joelhalpern.com>
Date: Sun, 2 Feb 2020 15:08:42 -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: <92EABB82-5C7E-4C80-9927-BB608B181199@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/0nX7qCYcOrgKxjMXXZVf5nJHJVs>
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 20:08:47 -0000

Actually, I would hope that folks post drafts well before they think 
they are "done".  The reason for my comment is that with folks pointing 
to github more often, I think it is important to emphasis the 
helpfulness of posting that initial draft.

Yours,
Joel

On 2/2/2020 2:48 PM, Fred Baker wrote:
>>> Do we have written advice on when a design group should put its work up?
>>
>> And indeed, the question of when a design team
>> should expose its output to the WG has always been a bit unclear. Something like
>> "When you have something worth saying to the WG, say it as an I-D" perhaps.
> 
> I agree, but I think I might say it a little differently. The point isn’t “we’re done”; the point is “we need the comments of the working group, which might be that we’re done”.
> 
> So the time to file the draft is when all known viewpoints have been addressed, and the document is in readable form. The draft might contain “TBD” sections, or questions. It is, if you will, a request for comments, and a viewpoint that may evoke dispute or commentary, but is designed to bring the group a step closer to consensus on a problem.
> _______________________________________________
> Ietf-and-github mailing list
> Ietf-and-github@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-and-github
>