| 08:55 | <annevk> | https://github.com/whatwg/dom/issues/844 is great <3 |
| 09:19 | <MikeSmith> | annevk: yeah, for real |
| 16:19 | <annevk> | Domenic: where do the names in https://github.com/whatwg/participate.whatwg.org/blob/master/config.json come from? |
| 16:20 | <annevk> | Domenic: e.g. "Console APIs" is not a thing we use elsewhere |
| 16:21 | <Domenic> | annevk: that is weird. They came from an initial draft of the Participant Agreement that the lawyers/SG put together I think. |
| 16:21 | <annevk> | Domenic: okay, maybe I should do more digging, but they are out-of-sync with Workstreams.md |
| 16:22 | <annevk> | Domenic: I was using that data to generate Workstreams.md and got these weird subtle differences |
| 16:22 | <Domenic> | Yeah, updating them seems totally reasonable |
| 16:24 | <annevk> | Domenic: I guess I'll consider Workstreams.md authoritative; especially if you copied them from an early draft, I remember canonicalizing those at some point |
| 16:24 | annevk | leaves a comment in the relevant issue as well for good measure |
| 16:25 | <Domenic> | Workstreams.md also matches https://spec.whatwg.org/ it seems so that seems like a good call |
| 16:26 | <Domenic> | And from a spot-check of the suspicious ones it matches the <h1>s and <title>s too. |
| 16:26 | <annevk> | Well technically spec.whatwg.org only lists standards, not workstreams |
| 16:27 | <annevk> | (as it probably should) |
| 16:27 | <Domenic> | Fair enough |
| 23:32 | <Bakkot> | anyone offhand have a link to the part of the spec that says that `fetch('https://𝕬.com')` fetches `a.com`? |
| 23:32 | <Bakkot> | I am having trouble figuring out why that happens |