Moving specs to modern infrastructure [missing: html-differences]

[domenic]

Excluding HTML, since it is a special duckling, all specs should ideally:

• Be on Bikeshed
• Not check their source files into the repo, but auto-deploy via Travis
• Deploy commit snapshots
• Include file-issue.js, commit-snapshot-shortcut-key.js, and dfn.js. (Or, instead of dfn.js, we should use Bikeshed's generated definition panels.)

If all of these become true we can start making some nice assumptions, e.g. we can move some script elements into our Bikeshed boilerplate.

What's missing?

• Fullscreen, Notifications, Mimesniff, Storage, Quirks
  • Still check in build output
  • Missing commit snapshots and commit-snapshot-shortcut-key.js
• XHR
  • Still checks in build output
  • Missing commit snapshots and commit-snapshot-shortcut-key.js
  • Still on Anolis; see Convert XHR to bikeshed xhr#97
• Compat
  • Still checks in build output
  • Missing commit snapshots and commit-snapshot-shortcut-key.js
  • dfn.js is in the footer, confusingly
• Console
  • Missing commit snapshots and commit-snapshot-shortcut-key.js (but does not check in build output)
  • Missing dfn.js
  • Both being fixed; see Meta: add commit and branch snapshots console#83
• Streams
  • Is using Bikeshed's definition generator instead of dfn.js (fixed in whatwg/streams@421e621)
• HTML differences from HTML4
  • Uses Anolis Convert to bikeshed html-differences#2
  • No Travis goodness either

[annevk]

Another thing I've started doing with help from @sideshowbarker is running the HTML checker on the output. That's quite nice to have:

• Meta: enable HTML checker streams#650
• Meta: enable HTML checker infra#54
• Meta: enable HTML checker platform.html5.org#44

[annevk]

HTML checker and commit snapshots:

• Meta: enable snapshots fullscreen#73
• Meta: enable snapshots notifications#91
• Meta: enable snapshots mimesniff#17
• Meta: enable snapshots storage#40
• Meta: enable snapshots quirks#9
• Meta: enable snapshots compat#72

[annevk]

You'll have to do Console. I don't have access to that server.

[annevk]

Books and Figures are also missing I just realized. @foolip and I are looking into that.

[foolip]

We ended up not doing that, because it would require first converting to Bikeshed. I think we should leave it be for now.

[foolip]

That is, unless @tabatkins wants to convert them :) (He's said that he's become very good at it.)

[zcorpan]

IIRC main problem with html-differences is that it cross-references lots of terms from HTML that HTML doesn't properly export.

[tabatkins]

Books and Figures are also not web-relevant specs; Håkon moved them out of the CSSWG when we tried to make him cut the spec to things browsers were actually willing to touch.

[foolip]

From poking around in whatwg/misc-server#7, I've found these *.spec.whatwg.org and *.idea.whatwg.org that don't use https://resources.whatwg.org/build/deploy.sh but rather some other deploy.sh:

• books.idea.whatwg.org (simple, no snapshots)
• compat.spec.whatwg.org (extra *.png)
• console.spec.whatwg.org (uses node)
• encoding.spec.whatwg.org (extra *.txt *json *.css)
• figures.idea.whatwg.org (simple, no snapshots)
• html.spec.whatwg.org (uses html-build)
• streams.spec.whatwg.org (uses node)
• url.spec.whatwg.org (extra .htaccess)

How much unification is worth attempting here? One thing that that'd help compat, encoding and url is to teach https://resources.whatwg.org/build/deploy.sh about an EXTRA_FILES variable that could be set to extra files to copy along.

Beyond that, having to change the deploy servers in so many places is a bit of effort. Would it make sense to separate the build and the deploy, so that the deploy bits (decoding the ssh key, rsync) are shared between more scripts?

[domenic]

@foolip, it looks like you're basically discussing #11. This issue was meant to be more about the actual spec content.

[foolip]

Oh, that explains why the lists in this issue didn't make as much sense as I though they should. Thanks :)

[annevk]

This is fixed by whatwg/misc-server#100.