Merge pull request #1 from InnerSourceCommons/master

Forked rebased from original repository

Author: dterol23

.github/CODEOWNERS

@@ -8,7 +8,7 @@
 # the repo. Unless a later match takes precedence,
 # @global-owner1 and @global-owner2 will be requested for
 # review when someone opens a pull request.
-*       @lenucksi @nyeates @gruetter @NewMexicoKid @cewilliams @spier
+*       @lenucksi @NewMexicoKid @cewilliams @spier
 
 # Order is important; the last matching pattern takes the most
 # precedence. When someone opens a pull request that only

.github/workflows/book.yml

@@ -4,6 +4,7 @@ on:
   push:
     branches:
       - "master"
+      - "book-staging"
 
 jobs:
   book-toc-generation:

.github/workflows/main.yml renamed to .github/workflows/link-checker.yml

@@ -18,6 +18,6 @@ jobs:
       id: lc
       uses: peter-evans/link-checker@v1
       with:
-        args: -v -d . -x "http://creativecommons.org/licenses|https://isc-inviter.herokuapp.com|https://github.com/rcs/rcs-viewer/pull/81|fearlesschangepatterns.com" README.md patterns/ -r
+        args: -v -d . -x "http://creativecommons.org/licenses|https://isc-inviter.herokuapp.com|https://github.com/rcs/rcs-viewer/pull/81|fearlesschangepatterns.com|https://ulir.ul.ie/bitstream/handle/10344/4443/Stol_2014_inner.pdf" README.md patterns/ -r
     - name: Fail if there were link errors
       run: exit ${{ steps.lc.outputs.exit_code }}

.github/workflows/lint-patterns.yml

@@ -6,6 +6,12 @@ on:
     branches:
       - "master"
   pull_request:
+    paths:
+      - ".github/workflows/lint-patterns.yml"
+      - "lint/*"
+      - "patterns/2-structured/*.md"
+      - "patterns/2-structured/project-setup/*.md"
+      - "patterns/3-validated/*.md"
 
 jobs:
   validate:

README.md

@@ -1,16 +1,31 @@
 # Trusted Committers
 
-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.
+Trusted Committers (TCs) are those members of our working group who have elevated rights and direct write access to this repository.
+
+> Trusted Committers 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.
+
+For further information about the concept, also see the [Trusted Committer Pattern](patterns/2-structured/trusted-committer.md).
 
 ## Current Trusted Committers
 
 * [@spier](https://github.com/spier) (added 2020-12-11)
 * [@lenucksi](https://github.com/lenucksi) (added 2020-04-24)
-* [@nyeates](https://github.com/nyeates) (added 2017-03-02)
-* [@gruetter](https://github.com/gruetter) (added 2017-03-02)
 * [@NewMexicoKid](https://github.com/NewMexicoKid) (added 2017-03-02)
 * [@cewilliams](https://github.com/cewilliams) (added 2017-03-02)
 
+## Hall of Fame (aka Alumni)
+
+While Trusted Committers are in principle appointed for lifetime, interests or priorities of a TC can change and they might not have enough time any more to contribute to the project.
+
+In those cases we ask them if we should move them to the Hall of Fame. Doing so allows us to appropriately thank them for all of their fantastic contributions. When doing so we also remove them from `.github/CODEOWNERS`, so that reviews of Pull Requests aren't assigned to them anymore, and GitHub notifications are reduced. That increases the clarity for the community who to expect feedback from when creating PRs.
+
+The alumni in the Hall of Fame can of course always start contributing again in the future and go back to being Trusted Committers if they want to.
+
+* [@gruetter](https://github.com/gruetter) (added 2017-03-02)
+* [@nyeates](https://github.com/nyeates) (added 2017-03-02)
+
 ## Process for Adding new Trusted Committers
 
 We work based on trust: Our goal is to add most people who contributed a sizeable change - quick and early.
@@ -34,4 +49,6 @@ We follow this process (adapted from [here](https://tech.europace.de/voting-in-n
 
 ## Admins
 
-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.
+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.