Re: [Ietf-and-github] [Ext] GIT WG disposition

[Spencer Dawkins at IETF <[e-mail]>]

Just following up,

On Thu, Jun 24, 2021 at 12:10 PM Salz, Rich <[e-mail]> wrote:

> Yup, we’re not the github police either.  And some WG’s existed before the
> RFC.
>

We made the decision (correctly, I thought) to include darned little about
the way Github repos are set up and administered in a published BCP, but
that leaves open the question of where we could publicize as a venue for
topics that draft authors should be aware of, that would be pretty
dynamic(*).

The "CircleCI breakage" issue I mentioned earlier in this thread is one
example, along with the related question of what other people are doing
(Travis, Github Actions, or who knows what). So that was in an issue in the
i-d-template repo (https://github.com/martinthomson/i-d-template/issues/293
).

Last week's interesting topic was on tools-discuss - it turns out that
although we are just starting to publish drafts and RFCs with
internationalized names, we're apparently seeing non-transliterated names
in references now (even expired ones), and there might be interesting
consequences. So that was on an IETF mailing list (
https://mailarchive.ietf.org/arch/msg/tools-discuss/eCDha5w4NLx-PX0DzenHC7CSJcE/
).

A day or two before that, I tripped over a bug that kramdown-rfc2629
currently produces v2 rfcxml (aka xml2rfc v2 input), but xml2rfc
command-line by default assumes --v3. If it sees v2 input, it internally
runs the v2->v3 converter, so the tools team needs to change the
datatracker's submit code (which uses xml2rfc as a library) to run v2v3
when it sees v2 now instead of just running the v2 parser. This one was
discussed in a TRAC ticket, by Robert Sparks' request (at
https://trac.ietf.org/trac/ietfdb/ticket/3305).

I know people (I'm co-chair with Michael Richardson and I have zoom taco
lunches with Robert and Henrik almost every Friday), and even for me, this
is kind of a snipe hunt ... I can't imagine being a new participant, and
I'd just as soon not drive people crazy because they have to answer the
same questions multiple times.

Best,

Spencer

(*) Should that be a Github repo? Ducking now ...