Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106)

> 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 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.

@marcoscaceres - thanks for this comment. I think I speak for all of the editors (@ianbjacobs , @adamroach , @tommythorsen , @jnormore and myself) when I say that we're fairly new to this (and if not then fairly new to specs that include WebIDL and browser algorithms or new to ReSpec or GitHub or all of it).

So, I am 100% in agreement that we try and avoid accumulating debt that we need to deal with later but also appeal to you to help us out here.

Feel free to point out things we're doing wrong (as you have above) or share some pro tips because we're keen to do them right.

While I appreciate you are putting a lot of effort into the PR spec right now your help as an editor here would be appreciated if you can spare some time. I think that at a minimum @tommythorsen , you and I could have an occasional call to sync up since timezones make it hard for you guys to join the TF calls.

-- 
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-286733329