https://git.reactos.org/?p=reactos.git;a=commitdiff;h=e516c2950b84d54ff66ba7...
commit e516c2950b84d54ff66ba795956a1080fa06ea43 Author: Pierre Schweitzer pierre@reactos.org AuthorDate: Mon Sep 10 18:47:29 2018 +0200 Commit: Pierre Schweitzer pierre@reactos.org CommitDate: Wed Sep 12 08:13:28 2018 +0200
[MAINTAINERS] Define who can be maintainer and how to be added to the file --- MAINTAINERS | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS index 934c42fe86..eb7763219b 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -9,6 +9,7 @@ area of ReactOS. Being a maintainer means the following: - that person has good knownledge 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 has push access on the repository Being a maintainer does not mean the following: - that person is dedicated to the area - 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 CONTRIBUTING.md apply. And if the maintainer is not available and 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 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 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. Descriptions of section entries used here: M: Primary maintainer. Assign them pull requests