Revise TSC meeting text w.r.t. WG meeting cadence

[benjie]

@mjmahone raised that the new increased cadence of WG meetings would impact on the TSC document. This edit attempts to maintain roughly the current level of commitment expected of TSC members whilst allowing for the WG to meet more than once per month. Originally I was going to propose 90 days, but to allow for the fact that "the first Thursday" can move around a bit I figured 100 days would be a safer bet (96 seemed too pedantic...).

This is a change to the TSC document, so we must follow the rules. I think this has a material impact on the expectation of TSC members, so I think the following applies:

Pull requests that change governance of the TSC (excluding the charter) must be open for at least 14 days, unless consensus is reached in a meeting with quorum of TSC attending members. If consensus cannot be reached, a pull request may still be landed after a vote by TSC members to override outstanding objections.

[leebyron]

Thanks for making this more resilient. I'm happy to approve as written - but curious what you think about my suggestions

[benjie]

I've changed the latter paragraph and think this is good to merge now :+1: Would love to get more input from @graphql/tsc though!

[mjmahone]

This looks good to me. We can always change to ad-hoc down the road. Technically once we get one more approver on the changes we can merge this (because it doesn't affect the Charter), though I'd probably prefer for the changes to get quorum (4 members, so one more) and either majority of TSC or 72 hours notice + majority of members who attend tomorrow, just as a way of us proving that TSC members are sufficiently aware that they can attend any of the weekly meetings going forwards (especially for TSC members like @andimarek who have likely previously been unable to attend due to timezone issues).

Members who can make the next meeting a TSC-quorum-capable meeting:

• @leebyron (August)
• @benjie (August)
• @IvanGoncharov (August)
• @xuorig (June)
• @mjmahone (August)
• @michaelstaib (August)
• @sachee (July)

[leebyron]

This seems like a great balance to me - predictable sync time when we need it for TSC meetings (first of the month) plus flexible definition of an attending member that's friendly to our incoming schedule additions. 👍

[leebyron]

Thanks for the framing Matt - let's let this hang for 72h from when you called the vote then we'll land it