Automatic publication of specs · W3C's Systeam · TPAC 2015

Who are we?

Intro

• The goal is complete automation: publish as part of your CI cycle
• Simple REST API
• Public e-mail notifications: public-tr-notifications@w3.org
• More and more groups working on GitHub publish now via Travis CI
• Faster, easier publication: benefits editors, chairs and team
• Currently handling WDs only (limitations)
• New? Start here: https://labs.w3.org/echidna/

The pieces

1. Echidna 1.3.1 (core)
2. Specberus 1.2.1 (pubrules checker)
3. ReSpec
4. Spec Generator
5. echidna-manifester (helps generating Echidna manifests)
6. echpub (CLI wrapper)
7. Third Party Resources Checker
8. Insafe (URL checker)

☑ Done recently

• Updated for Process 2015
• E-mail sent when things fail, too
• Better info on notifications by e-mail
• Support for “joint publication” (specs by multiple deliverers)
• Support for same-day publication
• Support for a permissive document license
• Support for exceptions

Exceptions

• They are, well, …exceptional
• Legitimate use: CSS WG
• Don't rely on them

☐ To-do

• New types of specs, and support for more corner cases
• Better error messages
• Specberus to replace the old pubrules checker (next year)
• Smarter extraction of metadata
• Checking broken links/fragments
• Richer API *
• Dashboard + Stats

* Stay here for the next session!

New types of specs coming soon

1. All types of WDs
2. Note
3. FPWD

Wrapping up

• Early tests and feedback from people outside the Systeam
  was very valuable in the early stages.
• Still, having more contributors would help speed things up
  and better serve users
• Public discussion:
  • public-pubrules-comments@w3.org
  • #pub