Re: [rfc-i] Inlining Issue Links in I-D

Joel Halpern <jmh@joelhalpern.com> Wed, 04 October 2023 21:00 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: rfc-interest@ietfa.amsl.com
Delivered-To: rfc-interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A54E0C1522C6 for <rfc-interest@ietfa.amsl.com>; Wed, 4 Oct 2023 14:00:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.198
X-Spam-Level:
X-Spam-Status: No, score=-2.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.091, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HEzUWjI1dtsr for <rfc-interest@ietfa.amsl.com>; Wed, 4 Oct 2023 14:00:06 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 48B96C151084 for <rfc-interest@rfc-editor.org>; Wed, 4 Oct 2023 13:59:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4S16WY0rxGz6G9gk; Wed, 4 Oct 2023 13:59:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1696453177; bh=weUORCSPG06Yn++3RGnEvUKYj2MgfY28V5o/aPA+w/g=; h=Date:Subject:To:References:From:In-Reply-To:From; b=dtyYNypyW4hxUj4/umLx4afENbifr4ZvoQYM0siMbqGA6iuuGZwWuVNLgvMirE/6m qUZ+YSa3KHtGu7DQKDYpm5y08GX2luDZ/1TQjQfk79KAWr/q4jfbpdX/7Yb0LnKR9D duFRXOpAg4hdiL1OQuVPZk7rYreMKE06dU98xCxM=
X-Quarantine-ID: <yDIerlqj9AFo>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.21.150] (unknown [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 4S16WX3Gvxz6G8wG; Wed, 4 Oct 2023 13:59:36 -0700 (PDT)
Message-ID: <aa3480ce-e817-1f1c-3af3-dbfd95b66a2e@joelhalpern.com>
Date: Wed, 04 Oct 2023 16:59:34 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.15.1
Content-Language: en-US
To: Jean Mahoney <jmahoney@amsl.com>, Rahul Gupta <cxres=40protonmail.com@dmarc.ietf.org>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
References: <ozfDRBOqqneS_A21AIUzhuvs5E5XLxdfzGKl77EHCPKmTTuo7ljtQqE4F-P4q9y8eZYED4KDEx8Sq1qjfgZ3VcnBoB-j3AGHX-oIw6Svmrs=@protonmail.com> <5ca3e27d-a291-4b0d-af9c-99ea567fb928@amsl.com>
From: Joel Halpern <jmh@joelhalpern.com>
In-Reply-To: <5ca3e27d-a291-4b0d-af9c-99ea567fb928@amsl.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/0syEEhUzdCKij0zSTJ9gtXQyyr0>
Subject: Re: [rfc-i] Inlining Issue Links in I-D
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Oct 2023 21:00:11 -0000

It is also common for difficult drafts to have an "open issues" section 
of the draft.  Whether to use the draft or github (or both) for such 
things probably varies from WG to WG and even document to document.

Yours,

Joel

On 10/4/2023 4:00 PM, Jean Mahoney wrote:
> Rahul,
>
> On 10/4/23 6:46 AM, Rahul Gupta wrote:
>> Hello again,
>>
>> This is a very specific issue stemming from my conversion to I-D. I 
>> have a few open issues (which will eventually be) in the Github repo 
>> of my draft and I would like to link them from at the very least from 
>> my editor's copy. I am currently doing so by wrapping the issues in a 
>> <cref> and explicitly linking to the Github Issue (footnotes in 
>> kramdown-rfc). Is this the best way to do this?
>
> [JM] The <cref> element [1] allows the author to make editorial 
> comments. Whether the comments are displayed in the output is set with 
> the display attribute (e.g., <cref display="false">). However, I don't 
> know how to hide the equivalent footnotes in kramdown-rfc. The 
> rfc-markdown mailing list would be the place to ask [2].
>
>
>>
>> I am also wondering if there is a culture including issues in a 
>> submitted I-D? 
>
> [JM] Many authors include a section in their I-D that points to the 
> I-D's repo. Authors can include references to GitHub repos [3] and 
> track issues as they wish during I-D development. For example, see [4].
>
>
>> If not, is there a way to keep the issues in the editor's copy and 
>> remove them from the submission in an automated manner?
>
> [JM] I don't know of a GitHub action that currently does that. Maybe 
> someone else has experience with that.
>
>
> Best regards,
> Jean
>
> [1] https://authors.ietf.org/en/rfcxml-vocabulary#cref
> [2] https://www.ietf.org/mailman/listinfo/rfc-markdown
> [3] https://www.rfc-editor.org/styleguide/part2/#ref_repo
> [4] 
> https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-rfc6265bis#name-changes
>
>>
>> Thanks in advance for all the advice,
>>
>> Best Regards
>> Rahul
>>
>>
>>
>> _______________________________________________
>> rfc-interest mailing list
>> rfc-interest@rfc-editor.org
>> https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest
>
> _______________________________________________
> rfc-interest mailing list
> rfc-interest@rfc-editor.org
> https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest