Skip to content

Commit

Permalink
Adding CODEOWNERS file. Also linking adding clickable links to the tr…
Browse files Browse the repository at this point in the history
…usted commiters.
  • Loading branch information
spier committed Apr 24, 2020
1 parent c6801f7 commit 14a9169
Show file tree
Hide file tree
Showing 2 changed files with 46 additions and 6 deletions.
40 changes: 40 additions & 0 deletions .github/CODEOWNERS
Validating CODEOWNERS rules …
@@ -0,0 +1,40 @@
# See GitHub documentation:
# https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-code-owners

# This is a comment.
# Each line is a file pattern followed by one or more owners.

# These owners will be the default owners for everything in
# 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

# Order is important; the last matching pattern takes the most
# precedence. When someone opens a pull request that only
# modifies JS files, only @js-owner and not the global
# owner(s) will be requested for a review.
# *.js @js-owner

# You can also use email addresses if you prefer. They'll be
# used to look up users just like we do for commit author
# emails.
# *.go docs@example.com

# In this example, @doctocat owns any files in the build/logs
# directory at the root of the repository and any of its
# subdirectories.
# /build/logs/ @doctocat

# The `docs/*` pattern will match files like
# `docs/getting-started.md` but not further nested files like
# `docs/build-app/troubleshooting.md`.
# docs/* docs@example.com

# In this example, @octocat owns any file in an apps directory
# anywhere in your repository.
# apps/ @octocat

# In this example, @doctocat owns any file in the `/docs`
# directory in the root of your repository.
# /docs/ @doctocat
12 changes: 6 additions & 6 deletions TRUSTED-COMMITTERS.md
Expand Up @@ -4,11 +4,11 @@ Trusted committers (TCs) are those members of our working group who have elevate

## Current Trusted Committers

* @lenucksi
* @nyeates
* @gruetter
* @NewMexicoKid
* @cewilliams
* [@lenucksi](https://github.com/lenucksi)
* [@nyeates](https://github.com/nyeates)
* [@gruetter](https://github.com/gruetter)
* [@NewMexicoKid](https://github.com/NewMexicoKid)
* [@cewilliams](https://github.com/cewilliams)

## Process for Adding new Trusted Committers

Expand All @@ -30,6 +30,6 @@ We follow this process (adapted from [here](https://tech.europace.de/voting-in-n
* New TC is added to the #innersource-patterns-tcs channel
* New TC is praised in the [#innersource-patterns](https://app.slack.com/client/T04PXKRM0/C2EFRTS6A) channel.


## 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.

0 comments on commit 14a9169

Please sign in to comment.