tabatkins
Add CG Transition Plan metadata, and build a note into Status based on that.
@deniak Just checking - is it intended to be the case that every cg-monitor.json file must contain a "transition_status", "intended_organization", and "intended_group" key, all plain text, and the "notes" key can potentially contain HTML? I've coded against those assumptions.
@deniak Just checking - is it intended to be the case that every cg-monitor.json file must contain a "transition_status", "intended_organization", and "intended_group" key, all plain text, and the "notes" key can potentially contain HTML? I've coded against those assumptions.
Thanks for reworking the PR. Just to be clear, that feature is only at the stage of prototyping and we are still discussing the details with the WICG chairs so please, do not merge this yet.
Now to answer your questions, we do expect the json to contain the keys transition_status and intended_organization. intended_group might be optional depending on the targeted organization.
As for the notes, I had planed to allow the use of HTML to give editors the possibility to provide more details but that's certainly something we can revise if this is an issue.
Initially, we fought about including these properties as bikeshed metadata but we also want this to work with respec and we will also build other tools relying of these data, hence the json.
