Skip to content
This repository has been archived by the owner on Nov 27, 2023. It is now read-only.

Commit

Permalink
Merge d2b3e02 into 0c75b47
Browse files Browse the repository at this point in the history
  • Loading branch information
spier committed Apr 6, 2020
2 parents 0c75b47 + d2b3e02 commit d1adb66
Show file tree
Hide file tree
Showing 2 changed files with 44 additions and 0 deletions.
19 changes: 19 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -193,6 +193,25 @@ Over the next two months it has been used in at least three Meltwater production

Are you using `gen_rmq` in production? Please let us know, we are curious to learn about your experiences!

## Maintainer

* Mateusz ([@mkorszun](https://github.com/mkorszun))

The maintainers are responsible for the general project oversight, and empowering further trusted committers (see below).

The maintainers are the ones that create new releases of gen_rmq.

## Trusted Committers

* Joel [@vorce](https://github.com/vorce)
* Sebastian [@spier](https://github.com/spier)

**Trusted Committers** (TC's) are members of our community who we have explicitly added to our GitHub repository.

Trusted Committers have elevated rights, allowing them to send in changes directly to branches and to approve Pull Requests.

For details see [TRUSTED-COMMITTERS.md](TRUSTED-COMMITTERS.md).

## License

The [MIT License](LICENSE).
Expand Down
25 changes: 25 additions & 0 deletions TRUSTED-COMMITTERS.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
# Trusted Committers

**Trusted Committers** (TC's) are members of our community who we have explicitly added to our GitHub repository. Trusted Committers have elevated rights, allowing them to send in changes directly to branches and to approve Pull Requests. (GitHub refers to these accounts as [collaborators][collaborators]).

We ask that TC's open Pull-Request when making changes, to make these changes transparent for everybody.

## What you get as a Trusted Committer:

- **WRITE** access to this repository (no need to maintain your own fork)
- More immediate impact on the roadmap and feature development of gen_rmq
- Fame and glory in the gen_rmq community :)

## What we expect from a Trusted Committer:

- Help us to drive the conversations in GitHub Issues (e.g. provide feedback to other user of gen_rmq or answer their questions)
- Review pull requests (e.g. by helping the author of the PR understand what needs to be done in order to get the PR into a mergeable shape)
- Be a role model for for our [Code of Conduct](CODE_OF_CONDUCT.md)

## Adding Trusted Committers

It is our ambition to empower as many trusted Trusted Committers as possible.

When a GitHub user has made a couple of contributions to gen_rmq, we will contact them and ask them if they want to support the development of gen_rmq by becoming a Trusted Committer. We will use a GitHub issue on this repo to do that.

[collaborators]: https://help.github.com/en/articles/adding-outside-collaborators-to-repositories-in-your-organization

0 comments on commit d1adb66

Please sign in to comment.