Docs: Update governance (#13055)

docs/maintainer-guide/governance.md

@@ -85,17 +85,17 @@ The TSC has final authority over this project including:
 * Contribution policy
 * GitHub repository hosting
 
-TSC seats are not time-limited. There is no fixed size of the TSC. The TSC should be of such a size as to ensure adequate coverage of important areas of expertise balanced with the ability to make decisions efficiently.
+TSC seats are not time-limited. The size of the TSC can not be larger than five members. This size ensures adequate coverage of important areas of expertise balanced with the ability to make decisions efficiently.
 
 The TSC may add additional members to the TSC by a standard TSC motion.
 
-A TSC member may be removed from the TSC by voluntary resignation, or by a standard TSC motion.
+A TSC member may be removed from the TSC by voluntary resignation, by a standard TSC motion, or by missing four consecutive TSC meetings. In all cases, the TSC member will revert to Reviewer status unless they prefer Alumni status.
 
 Changes to TSC membership should be posted in the agenda, and may be suggested as any other agenda item (see "TSC Meetings" below).
 
 No more than 1/3 of the TSC members may be affiliated with the same employer. If removal or resignation of a TSC member, or a change of employment by a TSC member, creates a situation where more than 1/3 of the TSC membership shares an employer, then the situation must be immediately remedied by the resignation or removal of one or more TSC members affiliated with the over-represented employer(s).
 
-TSC members have additional responsibilities over and above those of a Committer. These responsibilities ensure the smooth running of the project. TSC members are expected to review code contributions, approve changes to this document, manage the copyrights within the project outputs, and attend regular TSC meetings.
+TSC members have additional responsibilities over and above those of a Reviewer. These responsibilities ensure the smooth running of the project. TSC members are expected to review code contributions, approve changes to this document, manage the copyrights within the project outputs, and attend regular TSC meetings.
 
 TSC members may perform all of the duties of Reviewers, and also:
 
@@ -108,8 +108,6 @@ There is no specific set of requirements or qualifications for TSC members beyon
 
 A Reviewer is invited to become a TSC member by existing TSC members. A nomination will result in discussion and then a decision by the TSC.
 
-**Non-attending TSC Members:** TSC members who will be unavailable for meetings for any period of time may choose to be considered non-attending members. Non-attending members retain their TSC status but do not count as absent from meetings or votes. For instance, if the TSC has seven members with one non-attending member, the effective TSC size is six for meetings and votes. Non-attending members may still attending TSC meetings and participate in votes, in which case they are counted as an attending TSC member.
-
 #### Process for Adding TSC Members
 
 1. Add the GitHub user to the "ESLint TSC" GitHub team
@@ -122,11 +120,6 @@ A Reviewer is invited to become a TSC member by existing TSC members. A nominati
 1. Add the TSC member to the ESLint TSC mailing list as an "Owner"
 1. Tweet congratulations to the new TSC member from the ESLint Twitter account
 
-#### Process for Adding Non-attending TSC Members
-
-1. The TSC member informs the rest of the TSC about their non-attending status
-1. The TSC member is added to the "Non-attending TSC" GitHub team
-
 #### TSC Meetings
 
 The TSC meets every other week in the [TSC Meeting](https://gitter.im/eslint/tsc-meetings) chatroom. The meeting is run by