Set venue on all markdown drafts

[martinthomson]

Here's what I've used:

venue:
  group: httpbis
  type: Working
  mail: ietf-http-wg@w3.org
  arch: https://lists.w3.org/Archives/Public/ietf-http-wg/
  github: httpwg/http-extensions

[martinthomson]

Hmm, this is display only, so I think we need group: HTTP instead.

[mnot]

Does kramdown-rfc2629 do anything with this yet?

[martinthomson]

Yes, though you might need to update, as usual.

[mnot]

Blocked on cabo/kramdown-rfc#142

[martinthomson]

I see, you don't want to lose the issue tracker link from the existing note. I can take that up, it's a tiny change.

[martinthomson]

@mnot, looking at the notice we have currently, we have (for example):

Working Group information can be found at http://httpwg.github.io/; source code and issues list for this draft can be found at https://github.com/httpwg/http-extensions/labels/6265bis.

(Leaving aside the fact that this form of link renders really poorly once it gets through xml2rfc, even if it works really nicely in Github...)

If we were to change the repository link to point to the one we have there, kramdown-rfc2629 would produce:

Source for this draft and an issue tracker can be found at https://github.com/httpwg/http-extensions/labels/6265bis.

That loses the working group home page. Should we try to add a(n optional) homepage link to the text produced by the venue block?

[mnot]

think so

[martinthomson]

I've just opened cabo/kramdown-rfc#143

With this input:

venue:
  group: HTTP
  type: Working Group
  homepage: https://httpwg.github.io/
  mail: ietf-http-wg@w3.org
  arch: https://lists.w3.org/Archives/Public/ietf-http-wg/
  repo: https://github.com/httpwg/http-extensions/labels/binary-messages

You get XML like so:

    <note title="Discussion Venues" removeInRFC="true">
      <t>
        Discussion of this document takes place on the
        HTTP Working Group mailing list (ietf-http-wg@w3.org),
        which is archived at <eref target="https://lists.w3.org/Archives/Public/ietf-http-wg/"/>.
        Working Group information can be found at <eref target="https://httpwg.github.io/"/>.
      </t>
      <t>Source for this draft and an issue tracker can be found at
        <eref target="https://github.com/httpwg/http-extensions/labels/binary-messages"/>.</t>
    </note>

Seem OK?

[mnot]

It's a bit weird to say the source is available at the issues list, but probably OK.

BTW, it's https://httpwg.org/

[martinthomson]

Link fixed. I shouldn't have copy and pasted...

$ grep httpwg.github *.md
draft-ietf-httpbis-bcp56bis.md:Working Group information can be found at <http://httpwg.github.io/>; source code and issues list for this draft can be found at <https://github.com/httpwg/http-extensions/labels/bcp56bis>.
draft-ietf-httpbis-client-cert-field.md:Working Group information can be found at <http://httpwg.github.io/>; source code and issues list for this draft can be found at <https://github.com/httpwg/http-extensions/labels/client-cert-field>.
draft-ietf-httpbis-expect-ct.md:Working Group information can be found at <http://httpwg.github.io/>; source
draft-ietf-httpbis-rfc6265bis.md:Working Group information can be found at <http://httpwg.github.io/>; source
draft-ietf-httpbis-variants.md:Working Group information can be found at <https://httpwg.github.io/>; source code and issues list

Though we'll be fixing that with this change, I guess.

[cabo]

repo: https://github.com/httpwg/http-extensions/labels/binary-messages

➔

github: httpwg/http-extensions/labels/binary-messages

Just saying.

[mnot]

Can this be closed now?

[cabo]

I just saw a github-issues-label YAML attribute that my code isn't using yet.

[mnot]

That's for the issue links in views like this.