IETF Logo Mail Archive

Re: [Ext] The RPC's roadmap regarding GitHub

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 05 August 2026 01:54 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: wgchairs@mail2.ietf.org
Delivered-To: wgchairs@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id B846B123CF4A8 for <wgchairs@mail2.ietf.org>; Tue, 4 Aug 2026 18:54:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1785894853; bh=v9In/Bv5yBd69MK4+6aSYNgot4we42S0mxtYuG9T80Y=; h=From:To:Subject:In-Reply-To:References:Date; b=rXG964bYX8hGEg2xHAsI1oIE/DNgxf6F2xsD49YvifkDCoFjs7uVnBtKpB9fvhy48 FsHJrsfMcBPcvFymufIeO50q7mNFoEk0lF5q5Z5YFO+WxpqIOiAwVArpiR818qBdqA mhGRUCHL/dyJWK+piIxb1ViGs9NhAyOA3Ma+gtC4=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qb0lylrEDSqB for <wgchairs@mail2.ietf.org>; Tue, 4 Aug 2026 18:54:13 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 471F0123CF4A0 for <wgchairs@ietf.org>; Tue, 4 Aug 2026 18:54:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id D7A6B1801D; Tue, 04 Aug 2026 21:54:12 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavis, port 10024) with LMTP id CBlYWKGoH9-s; Tue, 4 Aug 2026 21:54:10 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1785894850; bh=PS+cLcDp4IlYhCaRokuGnvSGgDX9RBw6m/dnDeD/rB0=; h=From:To:Subject:In-Reply-To:References:Date:From; b=gZNm6Qy0hhm4GNLij9xtrBJhZP5029JKYOjo2uhIv/HIeIXWJvguPzAsX5Llbm0hu /ZnNLmfOjUZGXvrUtAf0e8WcwufxK1nOeijdU8x/iU/kzvm0NYS6IoQ+lapKaHpXoi xw9N7SoHeS9S/yn02yRdByZSJy/6dtFMbUv05xFdusCROmXaULihK6h0onjsSyTI9m kBRD8k5FLRTZpMgdPsxiosXlZyW/ZDPp+DTC2/rj3DIXz7Xiv12HW15Zr/5ubGRJ+4 soeLdx0M4ppTJQUQ82Nex3ngN9MWP6+pCpwx5N50Tt28yNP+EZHbFAI+br5+AodrAy vqBdPHNgTsrqg==
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id B05AE1800C; Tue, 04 Aug 2026 21:54:10 -0400 (EDT)
Received: from obiwan.sandelman.ca (obiwan.sandelman.ca [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id A84081E2; Tue, 04 Aug 2026 21:54:10 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Paul Hoffman <paul.hoffman@icann.org>, WG Chairs <wgchairs@ietf.org>
Subject: Re: [Ext] The RPC's roadmap regarding GitHub
In-Reply-To: <A3A85C3F-1FC6-4683-9DFF-735BC0927B02@icann.org>
References: <cf16dc44-dee6-417b-8796-84c24b5adf2b@staff.rfc-editor.org> <3XgIjBtmulQvGkAdWqil1TCywq8fUnwW3zwTFZSiT4p9VSYN9ZetdsgKu9gMKYtA9Nr1dkOdezlqFxYBi2RxwUATD6Xi7-Fyu39_qcY6qaQ=@ounsworth.ca> <7F1F1680-8959-4D84-AF4E-E9FECE32081F@kuehlewind.net> <A3A85C3F-1FC6-4683-9DFF-735BC0927B02@icann.org>
X-Mailer: MH-E 8.6+git; nmh 1.8+dev; Emacs 30.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0;<'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Tue, 04 Aug 2026 21:54:10 -0400
Message-ID: <671.1785894850@obiwan.sandelman.ca>
Message-ID-Hash: FI6KCXRH34BBMEMSB3RZZ7R7YO3WZXCK
X-Message-ID-Hash: FI6KCXRH34BBMEMSB3RZZ7R7YO3WZXCK
X-MailFrom: mcr+ietf@sandelman.ca
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-wgchairs.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/NP9nhIyrg7Ngxe02x7YwZc2Qxzg>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Owner: <mailto:wgchairs-owner@ietf.org>
List-Post: <mailto:wgchairs@ietf.org>
List-Subscribe: <mailto:wgchairs-join@ietf.org>
List-Unsubscribe: <mailto:wgchairs-leave@ietf.org>

Paul Hoffman <paul.hoffman@icann.org> wrote:
    > For many reasons, I support Mirja's proposal over Mike's. There are
    > many ways that WGs own repos, with different ownership models. Some WG
    > drafts still live in repos owned by one of the authors. Not everyone
    > uses the same tooling in their repos. And so on.

This is true.

    > The RPC should not have to deal with legacy tooling in repos.

yes/no.
We should be moving to a place where the YANG tooling is used.

OTH, I have documents that have scripts and Makefiles to build the examples,
and I do not want the RPC to need to interact with that.

    > The RPC can fork a repo and use just the .mkd/.xml file there, do what
    > they normally do, then when finished create a pull request for the
    > original repo.

    > It is up to the original repo owner to deal with
    > fighting with merge conflicts or choose to just keep the pre-RPC file
    > separate and start fresh with the RPC output. And it is up to the
    > original repo owner to deal with any other files in the pull request
    > however they want.



--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

**       My working hours and your working hours may be different.         **
** Please do not feel obligated to reply outside your normal working hours **

v2.46.0 | Report a Bug | By Email | System Status