1
0
Fork 0

Split maintainer responsibilities into list

This commit is contained in:
Lizzy Fleckenstein 2021-10-26 12:11:18 +02:00
parent ea0f52763c
commit 1bd972bff7
Signed by untrusted user: LizzyFleckenstein03
GPG Key ID: 06927A5199D6C9B2
1 changed files with 14 additions and 8 deletions

View File

@ -299,19 +299,25 @@ your code. You should be on the Discord (or, if you really don't like
Discord, Matrix or IRC). Discord, Matrix or IRC).
### Maintainer status ### Maintainer status
Maintainers are responsible for making sure issues are addressed and Maintainers carry the main responsibility for the project.
pull requests are reviewed and merged, by assigning either themselves or
Developers to issues / PRs. Maintainers are responsible for making
releases, making sure guidelines are kept and making project decisions
based on what the community wants. Maintainers grant/revoke developer
access. Currently there are two maintainers with different
responsibility fields:
#### Maintainer responsibilities
- Making sure issues are addressed and pull requests are reviewed and
merged, by assigning either themselves or Developers to issues / PRs
- Making releases
- Making sure guidelines are kept
- Making project decisions based on what the community wants
- Granting/revoking developer access
- Enforcing the code of conduct (See CODE_OF_CONDUCT.md)
- Moderating official community spaces (See Links section)
- Resolving conflicts and problems within the community
#### Current maintainers
* Fleckenstein - responsible for gameplay review, publishing releases, * Fleckenstein - responsible for gameplay review, publishing releases,
technical guidelines and issue/PR delegation technical guidelines and issue/PR delegation
* Nicu - responsible for community related issues * Nicu - responsible for community related issues
#### Creating releases #### Release process
* Launch MineClone2 to make sure it still runs * Launch MineClone2 to make sure it still runs
* Update the version number in README.md * Update the version number in README.md
* Use `git tag <version number>` to tag the latest commit with the * Use `git tag <version number>` to tag the latest commit with the