Approaches for the CSS WG

Intro

We want the CSS WG (and other WGs too) to start publishing automatically with Echidna. The workflows for their specs are different to the most of the rest of specs Echidna is handling already:

• They use Bikeshed (instead of ReSpec; where Echidna has had more experience recently).
• They publish EDs on their own site (instead of having WDs on gh-pages as most other groups).

Options

1. CSS WG to publish WDs + Echidna manifests on their public site

Changes required:
No changes on the part of Echidna.
CSS WG: start uploading more/other files to drafts.csswg.org as part of their CI cycle.

Pros:
Consistent with the usage of the rest of groups.

Cons:
Changes required in CSS WG's CI.
“Less security”, ie, the same level of security we have right now for other WGs.

2. CSS WG to send signed TAR to Echidna

Changes required:
Echidna: learn how to verify signed files; store and manage public key(s) associated to tokens.
CSS WG: package their WD as a TAR file; sign it; manage private keys in a safe way (but as part of their CI system).

Pros:

Cons:

3. CSS WG to send TAR to Echidna, authenticating with a W3C account

Changes required:

Pros:

Cons: