Re: [Edm] Implementation status tag name: please bikeshed!

Tommy Pauly <tpauly@apple.com> Wed, 02 March 2022 22:42 UTC

Return-Path: <tpauly@apple.com>
X-Original-To: edm@ietfa.amsl.com
Delivered-To: edm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B76443A0D18; Wed, 2 Mar 2022 14:42:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.11
X-Spam-Level:
X-Spam-Status: No, score=-2.11 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.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 CgwtR-XX_h97; Wed, 2 Mar 2022 14:42:35 -0800 (PST)
Received: from rn-mailsvcp-ppex-lapp34.apple.com (rn-mailsvcp-ppex-lapp34.rno.apple.com [17.179.253.43]) (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 626B13A0CA4; Wed, 2 Mar 2022 14:42:35 -0800 (PST)
Received: from pps.filterd (rn-mailsvcp-ppex-lapp34.rno.apple.com [127.0.0.1]) by rn-mailsvcp-ppex-lapp34.rno.apple.com (8.16.1.2/8.16.1.2) with SMTP id 222MZa7D016568; Wed, 2 Mar 2022 14:42:34 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=from : message-id : content-type : mime-version : subject : date : in-reply-to : cc : to : references; s=20180706; bh=/8DwMsQHkePewZMF/9b1l4W87nAYtsZh1ufLaKbFeYc=; b=flFSbU99p6moUjVs7afornjtwCnhOkxw8knO71hn0xz058PUkK1qvmuCnl4FGQFVyvcs /FTUstV3RljW0RRllyDJCuYmUsh27tpe0UxSX026O2ZXga22au6K7Wf7Pzo9+RQM95Vo xz5qsdh9d20SZ1TipFJ0agdWkr4KkAGo70/iPXm/32p7DQBrfLAUWXhZ25KO5xdCc5Pr dCpJ84BqAggyyyy1IY9tABuoL/uL3P97QQ4ByUfhQu2ud6XlUOm4ll5EDivFAK4EcvML hzg/DJSMrKa0HHWy5iPtJb2vxXbrZa266YjVC04uyqYkkr3C3LzwmuYtkqamZChTaYI2 kQ==
Received: from rn-mailsvcp-mta-lapp01.rno.apple.com (rn-mailsvcp-mta-lapp01.rno.apple.com [10.225.203.149]) by rn-mailsvcp-ppex-lapp34.rno.apple.com with ESMTP id 3eg4vk324f-3 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 02 Mar 2022 14:42:34 -0800
Received: from rn-mailsvcp-mmp-lapp03.rno.apple.com (rn-mailsvcp-mmp-lapp03.rno.apple.com [17.179.253.16]) by rn-mailsvcp-mta-lapp01.rno.apple.com (Oracle Communications Messaging Server 8.1.0.12.20210903 64bit (built Sep 3 2021)) with ESMTPS id <0R8500FWH32YESA0@rn-mailsvcp-mta-lapp01.rno.apple.com>; Wed, 02 Mar 2022 14:42:34 -0800 (PST)
Received: from process_milters-daemon.rn-mailsvcp-mmp-lapp03.rno.apple.com by rn-mailsvcp-mmp-lapp03.rno.apple.com (Oracle Communications Messaging Server 8.1.0.12.20210903 64bit (built Sep 3 2021)) id <0R85008002S0UB00@rn-mailsvcp-mmp-lapp03.rno.apple.com>; Wed, 02 Mar 2022 14:42:34 -0800 (PST)
X-Va-A:
X-Va-T-CD: 1e58dc2e89e8351ba969e2d7b2aff03a
X-Va-E-CD: bff16425e29f11bc55665ed5944d9d5e
X-Va-R-CD: 8e7c58964ea153a7d6d2e879da784ada
X-Va-CD: 0
X-Va-ID: da9b9542-9ddf-400f-999a-29974051e6d4
X-V-A:
X-V-T-CD: 1e58dc2e89e8351ba969e2d7b2aff03a
X-V-E-CD: bff16425e29f11bc55665ed5944d9d5e
X-V-R-CD: 8e7c58964ea153a7d6d2e879da784ada
X-V-CD: 0
X-V-ID: 454c5e83-685f-41d8-be7d-87c0b1a23ee2
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.425, 18.0.816 definitions=2022-03-02_05:2022-02-26, 2022-03-02 signatures=0
Received: from smtpclient.apple (unknown [17.11.184.8]) by rn-mailsvcp-mmp-lapp03.rno.apple.com (Oracle Communications Messaging Server 8.1.0.12.20210903 64bit (built Sep 3 2021)) with ESMTPSA id <0R85005FD32YUO00@rn-mailsvcp-mmp-lapp03.rno.apple.com>; Wed, 02 Mar 2022 14:42:34 -0800 (PST)
From: Tommy Pauly <tpauly@apple.com>
Message-id: <1AA4008A-F454-4C9C-AB5F-944AB15E93EB@apple.com>
Content-type: multipart/alternative; boundary="Apple-Mail=_56857B2C-EFDB-4C22-A2F2-03EE094B0A70"
MIME-version: 1.0 (Mac OS X Mail 16.0 \(3696.80.61.1.1\))
Date: Wed, 02 Mar 2022 14:42:33 -0800
In-reply-to: <b6c5a0c2-fb92-6285-ef11-c96edd46665c@nostrum.com>
Cc: "edm@iab.org" <edm@iab.org>
To: Robert Sparks <rjsparks@nostrum.com>, "Charles Eckel (eckelcu)" <eckelcu=40cisco.com@dmarc.ietf.org>
References: <A59FD713-6D6B-4F90-A66A-1BF67215592F@apple.com> <5D859367-0339-4404-87E2-AF02FDE45487@apple.com> <6E9C77EC-1C82-4778-8B92-C2A78AF36D1A@cisco.com> <D7C96004-4ABA-4CE5-87CF-4B64894947FB@apple.com> <b6c5a0c2-fb92-6285-ef11-c96edd46665c@nostrum.com>
X-Mailer: Apple Mail (2.3696.80.61.1.1)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.425, 18.0.816 definitions=2022-03-02_05:2022-02-26, 2022-03-02 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/edm/xh76UiBAB-O4whap_5hU56eWkuE>
Subject: Re: [Edm] Implementation status tag name: please bikeshed!
X-BeenThere: edm@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Evolvability, Deployability, & Maintainability \(Proposed\) Program" <edm.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/edm>, <mailto:edm-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/edm/>
List-Post: <mailto:edm@iab.org>
List-Help: <mailto:edm-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/edm>, <mailto:edm-request@iab.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2022 22:42:46 -0000

Perfect! I do see it now. I didn’t realize that trac wouldn’t reflect that.

Charles, we should be good to go then for the hackathon.

Best,
Tommy

> On Mar 2, 2022, at 2:04 PM, Robert Sparks <rjsparks@nostrum.com> wrote:
> 
> It should be available already. The ticket hasn't changed as we have a soft-freeze on trac (we're letting people enter new tickets, but making as few other changes as possible) as we wrap up the migration to github.
> 
> RjS
> 
> On 3/2/22 3:30 PM, Tommy Pauly wrote:
>> 
>> 
>>> On Mar 2, 2022, at 1:23 PM, Charles Eckel (eckelcu) <eckelcu=40cisco.com@dmarc.ietf.org <mailto:eckelcu=40cisco.com@dmarc.ietf.org>> wrote:
>>> 
>>> 
>>>> On Feb 18, 2022, at 12:41 PM, Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org <mailto:tpauly=40apple.com@dmarc.ietf.org>> wrote:
>>>> 
>>>> Thanks to everyone who provided feedback via email and GitHub.
>>>> 
>>>> David and I discussed, and I think we’d like to go with:
>>>> - Tag name: “related_implementations” 
>>>> - Display name: "Related Implementations”
>>> 
>>> Works for me.
>>> 
>>>> 
>>>> Robert, could you get that added?
>>> 
>>> Is there a need for an enhancement request to be entered for this, and if so, what is the mechanism for does so?
>> 
>> Robert filed this: https://trac.ietf.org/trac/ietfdb/ticket/3560 <https://trac.ietf.org/trac/ietfdb/ticket/3560>
>> 
>>> I am curious as to the time frame this functionality might be added and if there will be an opportunity to try it out during the IETF 113 Hackathon.
>> 
>> Agreed, if we can get this ahead of IETF 113, we could advertise it in the hackathon and let WG chairs know as well. Robert, what do you expect for timeline?
>> 
>> Tommy
>>> 
>>> Cheers,
>>> Charles
>>> 
>>>> 
>>>> Best,
>>>> Tommy
>>>> 
>>>>> On Feb 4, 2022, at 9:58 AM, Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org <mailto:tpauly=40apple.com@dmarc.ietf.org>> wrote:
>>>>> 
>>>>> At out last call, we discussed adding a single tag that WG chairs and document authors could use to point to a resource for implementation status/info/guidance/code or interop testing.
>>>>> 
>>>>> The question is what the tag name should be! This is a bikeshed, but we should decide on something before IETF 113 so we can add it for people working on the hackathon and in working groups.
>>>>> 
>>>>> For reference, the existing tags are: faq, github_org, github_repo, github_username, gitlab_username, jabber_log, jabber_room, mailing_list, mailing_list_archive, repo, slack, tracker, webpage, wiki, yc_entry, yc_impact
>>>>> 
>>>>> Some options to start us off:
>>>>> • implementations (display as “Implementations”)
>>>>> • impl_status (display as “Implementation Status”)
>>>>> • related_code (display as “Related Code”)
>>>>> 
>>>>> Please reply with other options, or which option you prefer.
>>>>> 
>>>>> You can also chime in on the GitHub issue: https://github.com/intarchboard/program-edm/issues/15 <https://github.com/intarchboard/program-edm/issues/15>
>>>>> 
>>>>> Best,
>>>>> Tommy
>>>>> -- 
>>>>> Edm mailing list
>>>>> Edm@iab.org <mailto:Edm@iab.org>
>>>>> https://www.iab.org/mailman/listinfo/edm <https://www.iab.org/mailman/listinfo/edm>
>>>> 
>>>> -- 
>>>> Edm mailing list
>>>> Edm@iab.org <mailto:Edm@iab.org>
>>>> https://www.iab.org/mailman/listinfo/edm <https://www.iab.org/mailman/listinfo/edm>
>>> 
>>