IETF Logo Mail Archive

Re: [Rswg] Issue Tracker/Filed Issues

Jean Mahoney <jmahoney@amsl.com> Wed, 12 October 2022 20:28 UTC

Return-Path: <jmahoney@amsl.com>
X-Original-To: rswg@ietfa.amsl.com
Delivered-To: rswg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02B43C14F73E for <rswg@ietfa.amsl.com>; Wed, 12 Oct 2022 13:28:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level:
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 M8b4U6CDvISE for <rswg@ietfa.amsl.com>; Wed, 12 Oct 2022 13:28:09 -0700 (PDT)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (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 40D90C14F727 for <rswg@rfc-editor.org>; Wed, 12 Oct 2022 13:28:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 2A8C0425C35A; Wed, 12 Oct 2022 13:28:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZUPRXJpNvyZc; Wed, 12 Oct 2022 13:28:09 -0700 (PDT)
Received: from [192.168.1.203] (unknown [47.186.48.51]) by c8a.amsl.com (Postfix) with ESMTPSA id E5035425977C; Wed, 12 Oct 2022 13:28:08 -0700 (PDT)
Message-ID: <9bee6b1f-ab81-b50c-d7c2-8acd73c9956e@amsl.com>
Date: Wed, 12 Oct 2022 15:28:08 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.3.2
Content-Language: en-US
To: Jay Daley <exec-director@ietf.org>, Eric Rescorla <ekr@rtfm.com>
Cc: rswg@rfc-editor.org
References: <CABcZeBN+qPVTo1Yn3tDSJSqFOajm3WX-y480Y++fSAEPgAUuyw@mail.gmail.com> <41450DD3-0F35-40AB-8CDA-F44BA75931F5@ietf.org> <4F1384F8-EA49-4731-8661-19591FC2D186@ietf.org>
From: Jean Mahoney <jmahoney@amsl.com>
In-Reply-To: <4F1384F8-EA49-4731-8661-19591FC2D186@ietf.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rswg/J51-l16UgjY9Tc03nCq7DkgsVtc>
Subject: Re: [Rswg] Issue Tracker/Filed Issues
X-BeenThere: rswg@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "RFC Series Working Group \(RSWG\)" <rswg.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rswg>, <mailto:rswg-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rswg/>
List-Post: <mailto:rswg@rfc-editor.org>
List-Help: <mailto:rswg-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rswg>, <mailto:rswg-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Oct 2022 20:28:13 -0000

Hi all,

On 10/10/22 5:58 AM, Jay Daley wrote:
> Ekr
>
>> On 5 Oct 2022, at 11:31, Jay Daley <exec-director@ietf.org> wrote:
>>
>>> On 27 Sep 2022, at 18:43, Eric Rescorla <ekr@rtfm.com> wrote:
>>>
>>> Hi folks,
>>>
>>> In Philadelphia we discussed setting up an issue tracker on GitHub
>>> to track proposed new issues. I have now done so at:
>>>
>>>     https://github.com/rfcseries-wg/new-topics/
>>>
>>> I have seeded the issues with the proposed topics I am aware of.
>>> If I have missed any or described them inaccurately, please file
>>> new issues, comment, etc. Pete is also giving it a scrub to
>>> make sure we missed anything.
>> I've started to add issues.  It would be useful if we had some labels that we could use to group issues - for example there are a couple that could be labelled 'rfc7991bis' and a couple 'rfc7997bis' .
> Or could we perhaps have a separate repo for 7991bis issues that are too detailed for this repo?
[JM] There exists the following repo for 7991bis with 51 open issues so far:
https://github.com/rfc-format/draft-iab-xml2rfc-v3-bis

Best regards,
Jean

>    For example, this proposed change has been identified in the xml2rfc repo: https://github.com/ietf-tools/xml2rfc/issues/898 and it could get lost if left there.
>
> Jay
>
>> Jay
>>
>>> Go ahead and file your new topic proposals. As discussed, any
>>> substantive discussion of the issue beyond fleshing out what it's
>>> about should be on the list.
>>>
>>> Note 1: This repo is just for new topics. Once we drafts, we may
>>> create new repos for those.
>>>
>>> Note 2: I believe I have captured the right language for
>>> CONTRIBUTING.md, but please file PRs/issues if you Think
>>> something is wrong.
>>>
>>> -Ekr
>>>
>>>
>>> -- 
>>> rswg mailing list
>>> rswg@rfc-editor.org
>>> https://mailman.rfc-editor.org/mailman/listinfo/rswg
>> -- 
>> Jay Daley
>> IETF Executive Director
>> exec-director@ietf.org
>>
>> -- 
>> rswg mailing list
>> rswg@rfc-editor.org
>> https://mailman.rfc-editor.org/mailman/listinfo/rswg

v2.23.0 | Report a Bug | By Email