[w3c/browser-payment-api] setup CI for automatic publications with echidna (#184)

@ianbjacobs @sideshowbarker That PR is the first step towards automatic publication with Echidna.
Since three specifications are developed under the same repository, we need to find a way to trigger Echidna for the right document.

The PR:
1. moves each spec in its own directory and adds the related Echidna manifest
2. adds a Travis config file which will identify which specs are updated in the commit and send the right manifest(s) to Echidna

If the proposal looks good to you, you will have to create [Echidna tokens](https://github.com/w3c/echidna/wiki/Token-creation) for the three documents and [encrypt them](https://github.com/w3c/echidna/wiki/Setting-up-Echidna-as-a-GitHub-hook) with travis:
```
travis encrypt TOKEN_PAYMENT_REQUEST=<token for payment request>
travis encrypt TOKEN_PAYMENT_METHOD_ID=<token for payment method identifier>
travis encrypt TOKEN_PAYMENT_METHOD_BASIC_CARD=<token for payment method basic card>
```

`.travis.yml` should then be updated with the encrypted tokens.
You can view, comment on, or merge this pull request online at:

  https://github.com/w3c/browser-payment-api/pull/184

-- Commit Summary --

  * setup CI for automatic publications with echidna

-- File Changes --

    A .travis.yml (18)
    A specs/payment-method-basic-card/W3CTRMANIFEST (1)
    R specs/payment-method-basic-card/basic-card-payment.html (0)
    A specs/payment-method-id/W3CTRMANIFEST (1)
    R specs/payment-method-id/method-identifiers.html (0)
    A specs/payment-request/W3CTRMANIFEST (2)
    R specs/payment-request/paymentrequest.html (0)
    R specs/payment-request/state-transitions.svg (0)

-- Patch Links --

https://github.com/w3c/browser-payment-api/pull/184.patch
https://github.com/w3c/browser-payment-api/pull/184.diff

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/browser-payment-api/pull/184