Chris Wilson

We should update these, and tend to be more inclusive in them (aka "I'd rather thank people who didn't do much than not thank someone who did.")

Definitely NOT a match for service workers. This is more like a background app; service workers are short-lived and transient by comparison.

@mnot "Representative" is an interesting word to use here; I think the TAG has had two primary roles in the past, and yes, I was thinking of the specification review...

Specific to "checking that the work from a WG was done properly - e.g. normative references are properly listed and horizontal reviews have been done" - I would expect the...

@fantasai I'm sure no one meant disrespect. The way in which you filed this issue presupposes a particular way of forming a Council - that it's based on the TAG/AB...

Thanks @dwsinger. @fantasai, I was not talking over your efforts to keep the issues separate; nor, as far as I can tell, was anyone else. They were getting slightly conflated,...

I would note that charters and WGs I've seen frequently add deliverables (in scope) and don't consider that a substantive enough change to have to recharter (as long as they're...

Indeed, can we *NOT* use the term "monoculture" to describe this issue? One shared implementation with a very diverse community is not a monoculture, and indeed, to those outside that...

Good thoughts, Mike. A few related things: - The one concern I have is that new implementations appearing shouldn't require a re-issue of the spec to remove that warning. Perhaps...

If there is a consensus that multiple Council reps with the same affiliation should not have separate votes (FWIW, I disagree, as both TAG and AB members are supposed to...