IETF Logo Mail Archive

Re: [Ietf-and-github] Tracking drafts

"Joel M. Halpern" <jmh@joelhalpern.com> Sun, 02 February 2020 17:06 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 9539012008D for <ietf-and-github@ietfa.amsl.com>; Sun, 2 Feb 2020 09:06:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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] 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 BdoDu9SRs6QO for <ietf-and-github@ietfa.amsl.com>; Sun, 2 Feb 2020 09:05:59 -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 6B0E212004D for <ietf-and-github@ietf.org>; Sun, 2 Feb 2020 09:05:59 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 489cmR2hWkz1nylv; Sun, 2 Feb 2020 09:05:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1580663159; bh=jrb04N1WkCLwN+EjXwy/BF1s7mH1I6+Db+t5oq2lEtk=; h=Subject:To:References:From:Date:In-Reply-To:From; b=AC+lURelpk+Mv0TeBmo6S2xxrkhnzMo9znOXaZtwR7hqJz1+V5w8SMkt4u+oJuG1O nzdTRTs5i9cw5OsvFj8wYJZCCn967q02CKgx2gAqzgYcArs2sCo1tfCYPV3500i2Vl Q8n7Gv5XB1DS2kz/XeA8g8DTdYqb7OUfnpLLiRA0=
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 489cmQ3sTjz1nt41; Sun, 2 Feb 2020 09:05:58 -0800 (PST)
To: "Salz, Rich" <rsalz@akamai.com>, 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> <c8035f5b-6ff8-594a-2527-fece1955bf35@joelhalpern.com> <3E6E2046-E0C7-46B8-859A-F2B0BC5ADF52@akamai.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <228b3c13-97c2-160f-35b7-f05b8d2d42af@joelhalpern.com>
Date: Sun, 2 Feb 2020 12:05:55 -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: <3E6E2046-E0C7-46B8-859A-F2B0BC5ADF52@akamai.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/oJ2vlPgbhh186egCTqxJPd-muqU>
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 17:06:02 -0000

There is a similarity.  I wish there were an easy way to know what 
design teams are being spawned in working groups that I am not 
following.  But I do not know a sensible way to do that.

Currently, I can generally learn of new work because I-Ds are posted. 
In fact, we frequently tell people to post an I-D for their ideas. 
However, I am starting to see folks sending notices of I-Ds that are 
purely in github repositories.  This means that there is no I-D 
announcement.  I am not asking to prohibit that.  But I am asking for 
help so that those of us who are trying to look broadly have some 
assistance in doing so.

Yours,
Joel

On 2/2/2020 11:06 AM, Salz, Rich wrote:
>>     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.
>    
> Do we have written advice on when a design group should put its work up?
> 
> Why do you think this is different, other than being a more open design group?
>

v2.8.7 | Report a Bug | By Email