Maintainer role definition #206
Merged
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
|
This pull request is in response to this issue from a year ago: #184 |
prisae
approved these changes
Jan 11, 2024
|
Not much happened regarding your review request, and the holiday season did probably not help. I really appreciate your ongoing work on this @JustinGOSSES - it would indeed be great if we could broaden the maintainer spectrum. Might it be worth to write a short message about this in the Mattermost~OpenGeoscience channel? |
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.
This pull request adds a new file maintainerRole.md file and makes small changes to several existing files all for the purpose of documenting the maintainer role. This is being done to try and make it easier to attract new maintainers to the project.
An issue template has also been created to be used to "apply" to be a maintainer. Issues don't exist on forked repositories, so there might be some trial and error in this repo to get that to work correctly as I can't test it in the fork.
There is also a single line change related to a DOI badge that should be merged in first in a separate pull request: #205 . It is included here to avoid a mere conflict.