01/05: Add a maintainers file

[Pierre Schweitzer]

https://git.reactos.org/?p=reactos.git;a=commitdiff;h=a8ce91e7168aa16ca71f4…

commit a8ce91e7168aa16ca71f456556da35ae0f64eaa7
Author:     Pierre Schweitzer <pierre(a)reactos.org>
AuthorDate: Sat Sep 8 11:14:56 2018 +0200
Commit:     Pierre Schweitzer <pierre(a)reactos.org>
CommitDate: Wed Sep 12 08:13:28 2018 +0200

    Add a maintainers file
---
 MAINTAINERS | 131 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 131 insertions(+)

diff --git a/MAINTAINERS b/MAINTAINERS
new file mode 100644
index 0000000000..ea1ab51212
--- /dev/null
+++ b/MAINTAINERS
@@ -0,0 +1,131 @@
+	List of maintainers for the ReactOS project
+
+This file purpose is to give newcomers to the projet the responsible
+developers when submitting a pull request on GitHub, or opening a bug
+report on Jira.
+
+This file will notably establish who is responsible for a specific
+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
+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
+	- that person is paid
+	- that person is always available
+
+We have no supported (paid) areas in ReactOS.
+
+When submitting a pull request on GitHub and looking for reviewers,
+look at that file and ask for a review from some of the people (M, R
+- the most recently active in the area) listed in the matching area,
+also, assign the pull request to the M person. Don't ask for a review
+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.
+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.
+
+There should be one and only one primary maintainer per area.
+
+In case of 3rd party code (also refered as upstream), the maintainer
+is responsible of updating periodically the source code and of
+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.
+
+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
+	   Use the GitHub, Jira, Real Name format for entry, squash if
+	   some are overlapping
+	R: Reviewers. Ask them for review on pull requests
+	S: Status, one of the following:
+	   Maintained:  Someone is handling that area
+	   Upstream: This is 3rd party code, synced in our tree
+	   Abandoned:  No one is handling that code anymore
+	F: Files. Directories, files (wildcards allowed) covered in
+	   this area
+	C: Comments
+
+Cache Manager
+	M: HeisSpiter, Pierre Schweitzer
+	S: Maintained
+	F: ntoskrnl/cc/
+
+Cache Manager Rewrite
+	S: Abandonned
+	F: ntoskrnl/cache/
+
+File Systems
+	M: HeisSpiter, Pierre Schweitzer
+	S: Maintained
+	F: drivers/filesystems/
+	F: sdk/lib/fslib/
+	C: Also see "Upstream File Systems"
+
+File Systems Run Time Library
+	M: HeisSpiter, Pierre Schweitzer
+	S: Maintained
+	F: ntoskrnl/fsrtl/
+	F: sdk/lib/drivers/ntoskrnl_vista/fsrtl.c
+
+IO Manager
+	M:
+	R: HeisSpiter, Pierre Schweitzer
+	S: Maintained
+	F: ntoskrnl/io/iomgr/
+
+Network File Systems kernel libraries
+	M: HeisSpiter, Pierre Schweitzer
+	S: Maintained
+	F: sdk/lib/drivers/rdbsslib/
+	F: sdk/lib/drivers/rxce/
+
+ROS internals tools
+	M: HeisSpiter, Pierre Schweitzer
+	S: Maintained
+	F: modules/rosapps/applications/rosinternals/
+
+Upstream File Systems
+	M: HeisSpiter, Pierre Schweitzer
+	S: Upstream
+	F: base/services/nfsd/
+	F: dll/np/nfs/
+	F: dll/shellext/shellbtrfs/
+	F: drivers/filesystems/btrfs/
+	F: drivers/filesystems/cdfs/
+	F: drivers/filesystems/ext2/
+	F: drivers/filesystems/fastfat_new/
+	F: drivers/filesystems/ffs/
+	F: drivers/filesystems/nfs/
+	F: drivers/filesystems/reiserfs/
+	F: media/doc/README.FSD
+	F: sdk/lib/fslib/btrfslib/
+	F: sdk/lib/fslib/ext2lib/
+	F: sdk/lib/fslib/vfatlib/check/
+
+Virtual CD-ROM
+	M: HeisSpiter, Pierre Schweitzer
+	S: Maintained
+	F: modules/rosapps/applications/cmdutils/vcdcli/
+	F: modules/rosapps/drivers/vcdrom/
+
+Virtual Floppy Disk
+	M: HeisSpiter, Pierre Schweitzer
+	S: Upstream
+	F: modules/rosapps/applications/cmdutils/vfdcmd/
+	F: modules/rosapps/drivers/vfd/
+
+Win32 file functions
+	M: HeisSpiter, Pierre Schweitzer
+	S: Maintained
+	F: dll/win32/kernel32/client/file/
+
+Windows Network File Systems functions
+	M: HeisSpiter, Pierre Schweitzer
+	S: Upstream
+	F: dll/win32/mpr/wnet.c