mirror of
https://github.com/reactos/reactos.git
synced 2025-04-20 20:36:35 +00:00
[MAINTAINERS] Define who can be maintainer and how to be added to the file
This commit is contained in:
parent
09bffcab1e
commit
e516c2950b
1 changed files with 7 additions and 1 deletions
|
@ -9,6 +9,7 @@ area of ReactOS. Being a maintainer means the following:
|
||||||
- that person has good knownledge in the area
|
- that person has good knownledge in the area
|
||||||
- that person is able to enforce consistency in the area
|
- that person is able to enforce consistency in the area
|
||||||
- that person may be available for giving help in the area
|
- that person may be available for giving help in the area
|
||||||
|
- that person has push access on the repository
|
||||||
Being a maintainer does not mean the following:
|
Being a maintainer does not mean the following:
|
||||||
- that person is dedicated to the area
|
- that person is dedicated to the area
|
||||||
- that person is working full-time on the area/on ReactOS
|
- that person is working full-time on the area/on ReactOS
|
||||||
|
@ -25,7 +26,8 @@ from all the listed reviewers.
|
||||||
Also, when submitted a pull request on GitHub, rules defined in
|
Also, when submitted a pull request on GitHub, rules defined in
|
||||||
CONTRIBUTING.md apply. And if the maintainer is not available and
|
CONTRIBUTING.md apply. And if the maintainer is not available and
|
||||||
reviewers approved the pull request, developers feeling confident
|
reviewers approved the pull request, developers feeling confident
|
||||||
can merge the pull request.
|
can merge the pull request. Note that reviewers do not necessarily
|
||||||
|
have push access to the repository.
|
||||||
When submitting a bug report on Jira, if you want to be sure to have
|
When submitting a bug report on Jira, if you want to be sure to have
|
||||||
a developer with skills in that area, write @nick from M people.
|
a developer with skills in that area, write @nick from M people.
|
||||||
|
|
||||||
|
@ -37,6 +39,10 @@ managing local patches. He is not here to upstream code on your behalf.
|
||||||
As responsible, he may refuse a local patch if you did not try to
|
As responsible, he may refuse a local patch if you did not try to
|
||||||
upstream your changes.
|
upstream your changes.
|
||||||
|
|
||||||
|
If you want to get listed in that file, either put yourself in the
|
||||||
|
file and push it, or open a pull request. You can also ask a person
|
||||||
|
who has push access to add yourself.
|
||||||
|
|
||||||
This file uses a similar format to the Linux kernel MAINTAINERS file.
|
This file uses a similar format to the Linux kernel MAINTAINERS file.
|
||||||
Descriptions of section entries used here:
|
Descriptions of section entries used here:
|
||||||
M: Primary maintainer. Assign them pull requests
|
M: Primary maintainer. Assign them pull requests
|
||||||
|
|
Loading…
Reference in a new issue