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

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> wrote:
>>
>>
>>> On Feb 18, 2022, at 12:41 PM, Tommy Pauly 
>>> <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
>
>> 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> 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
>>>>
>>>> Best,
>>>> Tommy
>>>> -- 
>>>> Edm mailing list
>>>> Edm@iab.org
>>>> https://www.iab.org/mailman/listinfo/edm
>>>
>>> -- 
>>> Edm mailing list
>>> Edm@iab.org
>>> https://www.iab.org/mailman/listinfo/edm
>>
>