This is not aimed at @tommythorsen - but in general, can we please be extremely disciplined with adding things to this spec. We've had to waste a lot of time on the Payment Request spec dealing with technical debt built up by adding bad markup, random phrasing, conformance statements that don't actually apply to any products, etc. Can we also be disciplined with running [HTML5 Tidy](https://github.com/htacg/tidy-html5) over the document before any commit goes in - and make sure ReSpec is being utilized to the fullest (i.e., don't use `<code>` tags). And make sure we don't pollute the commit history with random commit messages. Also, no one should be committing directly to `gh-pages`. @sideshowbarker, can you please set up branch protection to stop people doing that - i.e., only allow pull requests? ReSpec is already screaming that this document has over 66 issues. That's already really alarming - we need to do better and not rush things into the spec. If Editors need a "how to best use ReSpec" tutorial during the F2F, I'm happy to run that. -- 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/webpayments-payment-apps-api/pull/106#issuecomment-286677425
Received on Wednesday, 15 March 2017 08:50:57 UTC