Refreshed trusted committer file

Author: maxcapraro

meta/trusted-committers.md

@@ -1,22 +1,37 @@
 # Trusted Committers
 
-Trusted committers/collaborators/contributors (TC's) are those members of our community who we have explicitly added to our Github repository. These people have elevated rights, allowing them to send in changes directly to branches and to accept Pull Requests.
+Trusted committers (TCs) are those members of our working group who have elevated rights and direct write access to this repository. *TCs act as stewards of the working group and community. They aim to make consensus-based decisions in the best interest of the working group.* They also act as the guardians of this repository: TCs react to, referee, and give feedback about incoming contributions.
 
-GitHub refers to these accounts as [collaborators](https://help.github.com/en/articles/adding-outside-collaborators-to-repositories-in-your-organization).
+## Current Trusted Committers
 
-We ask that TC's still adhere to the Pull-Request mechanism, unless they are making changes to documentation where it is not realistic that anyone will review, or if there are easy typos/grammar fixes.
+* @lenucksi
+* @nyeates
+* @gruetter
+* @NewMexicoKid
+* @cewilliams
+
+## Process for Adding new Trusted Committers
 
-## Who we add
-We add most people who send any sizable change. We work on trust - with great privilege comes great responsibility!
+We work based on trust: Our goal is to add most people who contributed a sizeable change - quick and early.
 
-Adding people off-the-bat encourages more contributions, displays trust, allows us to easily tag each other in reviews, and ensures there is always someone around to moderate the site, move reviews along, and accept Pull Requests! If anyone goes on vacation, there are a slew of others that could step in.
+We follow this process (adapted from [here](https://tech.europace.de/voting-in-new-trusted-committers/)):
+
+1. Any trusted committer (TC) can step forward and nominate a new TC in the private Slack channel #innersource-patterns-tcs. The TC should provide the following information:
+   * Name of the candidate
+   * Reason for candidate
+   * Github handle of the candidate
+   * Slack handle of the candidate
+1. Every TC can raise concerns or second the nomination in the #innersource-patterns-tcs channel.
+1. If none of the existing TCs disagrees with the nomination within 72h, [lazy consensus](https://tech.europace.de/lazy-consensus-vs-explicit-voting/) is reached: The nomination is accepted.
+1. The TC who nominated the candidate informs her/him in private about the nomination and its acceptance. The candidate can decide on whether to accept or reject the offer.
+1. If the candidate accepts the offer, the TC who nominated the candidate, makes sure:
+   * New TC is added to this file.
+   * New TC receives write access to this repository.
+   * New TC is added to the #innersource-patterns-tcs channel
+   * New TC is praised on the general InnerSource Commons [mailing list]([email protected])
 
-If you want to become a Collaborator, @ mention one of the [Admins](#admins) in an Issue.
 
 ## Admins
-There are currently a handful of Github Admins for this repository. They hold the ability to add collaborators and modify the repositories nuclear options (delete, rename, etc).
+A handful of individuals are currently the technical GitHub Admins for this repository. This includes most members of the InnerSource Commons' #tech-infra team and members of the [InnerSource Commons GitHub Organization](https://github.com/innersourcecommons). However, please channel working group-specific requests through the trusted committers.
 
-* @nyeates - ask me first
-* @gruetter
-* @NewMexicoKid
-* @cewilliams
+## References