Consolidate human- and machine-readable Living Standard/Workstream lists about meta HOT 13 CLOSED

@tobie I've made it so that no changes are required for you. I'll update OP. (My rationale is that biblio.json has a semi-standardized format and Steering Group's db.json does not and I'm not sure to what extent we want to commit to its stability, especially initially.)

from meta.

What needs to be done? Where is help needed to realize the goal of this issue?

from meta.

@domenic one problem with putting this in whatwg/sg is that changes to whatwg/sg can take a long time.

(Having this would also help with further automating our label setup.)

from meta.

"whatwg/sg's Workstreams.md" and "participate.whatwg.org config.json" disagree on how Workstreams are named. Per discussion with @domenic the latter is likely wrong so those names will subtly change.

from meta.

(The effect of this would be changes visible on https://participate.whatwg.org/agreement.)

from meta.

whatwg/sg#111 and whatwg/whatwg.org#303 are my attempt at solving this. (I also added idea.whatwg.org as target.)

from meta.

Amazing stuff; looking forward to reviewing!

You haven't done participate.whatwg.org's config.json yet, right? I'd be happy to take that on myself; in particular figuring out a way that uses Node.js tools and works for both local development and deploy.

from meta.

Yeah, that's the one that's remaining. Thanks for taking that!

from meta.

@domenic so for labels.py I need all repositories that host a standard. I think it's safe to assume that standards and repos are 1:1 and that the shortname of a standard in its URL is 1:1 with the repo name. Do you agree or do we need a specific shortname or reponame or both field in addition to the URL?

from meta.

Let me know when we need to update specref.

from meta.

I think it's safe to assume that standards and repos are 1:1 and that the shortname of a standard in its URL is 1:1 with the repo name. Do you agree or do we need a specific shortname or reponame or both field in addition to the URL?

I agree with that. I believe we make that assumption in some of the Bikeshed boilerplate too.

from meta.

The whatwg/sg repository now contains db.json. What remains here are

• Update participate.whatwg.org code to consult this canonical resource
• Update labels.py to consult this canonical resource

as far as I can tell. https://github.com/whatwg/spec-factory also needs a small tweak to no longer fetch the file from a branch.

from meta.

This is all done now, hurray!

from meta.