[MISC] Introducing Stefan Appelhoff as the first Maintainer #176
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
franklin-feingold
approved these changes
Mar 13, 2019
sappelhoff
approved these changes
Mar 14, 2019
franklin-feingold
added a commit
that referenced
this pull request
Mar 19, 2019
emdupre
added
the
community
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Defining a new role - Maintainer - and their "super powers":
I also added a language encouraging authors of papers describing extensions to invite maintainers as coauthors. It's not an enforceable rule, but something that would be nice to follow.
This PR is the minimal way to introduce Maintainers to the organization I can think off. In the future, it might be worth revisiting the idea of triaging PRs.