Set up automatic publication with Travis & Echidna

[tripu]

Only 3 things left (find 3 instances of TO-DO in my changes):

1. Enter the URL to the group's decision to publish.
2. Encrypt the token with Travis and paste the resulting string in .travis.yml (instructions).
3. (Only if the spec is made up of more files than the index HTML) list all those files in echidna-manifest.txt.

[tripu]

The request was submitted OK from Travis to the publication framework. Unfortunately, the e-mail report wasn't sent to the publication list mailing because of a known bug in Echidna :(

Anyway, by looking at the logs in the server, I can tell it failed because it didn't pass Specberus (pubrules checker), which in turn failed because it didn't pass HTML validation (because of square brackets in some <a href>).

[andreastt]

@tripu I think @sideshowbarker fixed this in b88605a.

[sideshowbarker]

@tripu I think @sideshowbarker fixed this in b88605a.

Yeah, but since then the system has gotten hung up on another specberus thing that we're looking into. So it might not be until tomorrow or after that we get it working (it's already nearly 19:00 here in Japan for @tripu and me).

[andreastt]

We are not in a rush about this (-:

[tripu]

@sideshowbarker, @andreastt: Mike fixed that HTML validation error, yes. But Specberus found another one in the document: required patent policy paragraph not found (looking directly in the logs).
(I'm sorry about Echidna not sending e-mail about this; we're looking into that issue!)

[tripu]

(I see you people have been publishing OK with Echidna for a while now, and you may have seen those messages already, but, FYI, @deniak fixed that issue about Echidna not sending detailed e-mail when publications fail in w3c/echidna#216, and deployed in production a few days ago.)