[MAINTAINERS] Define who can be maintainer and how to be added to the file
[reactos.git] / MAINTAINERS
1 List of maintainers for the ReactOS project
2
3 This file purpose is to give newcomers to the projet the responsible
4 developers when submitting a pull request on GitHub, or opening a bug
5 report on Jira.
6
7 This file will notably establish who is responsible for a specific
8 area of ReactOS. Being a maintainer means the following:
9 - that person has good knownledge in the area
10 - that person is able to enforce consistency in the area
11 - that person may be available for giving help in the area
12 - that person has push access on the repository
13 Being a maintainer does not mean the following:
14 - that person is dedicated to the area
15 - that person is working full-time on the area/on ReactOS
16 - that person is paid
17 - that person is always available
18
19 We have no supported (paid) areas in ReactOS.
20
21 When submitting a pull request on GitHub and looking for reviewers,
22 look at that file and ask for a review from some of the people (M, R
23 - the most recently active in the area) listed in the matching area,
24 also, assign the pull request to the M person. Don't ask for a review
25 from all the listed reviewers.
26 Also, when submitted a pull request on GitHub, rules defined in
27 CONTRIBUTING.md apply. And if the maintainer is not available and
28 reviewers approved the pull request, developers feeling confident
29 can merge the pull request. Note that reviewers do not necessarily
30 have push access to the repository.
31 When submitting a bug report on Jira, if you want to be sure to have
32 a developer with skills in that area, write @nick from M people.
33
34 There should be one and only one primary maintainer per area.
35
36 In case of 3rd party code (also refered as upstream), the maintainer
37 is responsible of updating periodically the source code and of
38 managing local patches. He is not here to upstream code on your behalf.
39 As responsible, he may refuse a local patch if you did not try to
40 upstream your changes.
41
42 If you want to get listed in that file, either put yourself in the
43 file and push it, or open a pull request. You can also ask a person
44 who has push access to add yourself.
45
46 This file uses a similar format to the Linux kernel MAINTAINERS file.
47 Descriptions of section entries used here:
48 M: Primary maintainer. Assign them pull requests
49 Use the GitHub, Jira, Real Name format for entry, squash if
50 some are overlapping
51 R: Reviewers. Ask them for review on pull requests
52 S: Status, one of the following:
53 Maintained: Someone is handling that area
54 Upstream: This is 3rd party code, synced in our tree
55 Abandoned: No one is handling that code anymore
56 F: Files. Directories, files (wildcards allowed) covered in
57 this area
58 C: Comments
59
60 ACPI
61 M:
62 R: ThFabba, Thomas Faber
63 S: Maintained
64 F: drivers/bus/acpi/
65 F: hal/halx86/acpi/
66
67 ACPICA Library
68 M: ThFabba, Thomas Faber
69 S: Upstream
70 F: drivers/bus/acpi/acpica/
71
72 Apisets
73 M: learn-more, learn_more, Mark Jansen
74 S: Maintained
75 F: dll/apisets
76
77 Application Compatibility subystem
78 M: learn-more, learn_more, Mark Jansen
79 S: Maintained
80 F: dll/appcompat
81 F: dll/shellext/acppage
82 F: ntoskrnl/ps/apphelp.c
83
84 Cache Manager
85 M: HeisSpiter, Pierre Schweitzer
86 S: Maintained
87 F: ntoskrnl/cc/
88
89 Cache Manager Rewrite
90 S: Abandoned
91 F: ntoskrnl/cache/
92
93 CMake Build Scripts
94 M:
95 R: learn-more, learn_more, Mark Jansen
96 R: ThFabba, Thomas Faber
97 S: Maintained
98 F: sdk/cmake/
99 F: */CMakeLists.txt
100 F: */*.cmake
101
102 File Systems
103 M: HeisSpiter, Pierre Schweitzer
104 S: Maintained
105 F: drivers/filesystems/
106 F: sdk/lib/fslib/
107 C: Also see "Upstream File Systems"
108
109 File Systems Run Time Library
110 M: HeisSpiter, Pierre Schweitzer
111 S: Maintained
112 F: ntoskrnl/fsrtl/
113 F: sdk/lib/drivers/ntoskrnl_vista/fsrtl.c
114
115 HID Drivers
116 M:
117 R: ThFabba, Thomas Faber
118 S: Maintained
119 F: drivers/hid/
120
121 Kernel
122 M:
123 R: HeisSpiter, Pierre Schweitzer
124 R: ThFabba, Thomas Faber
125 S: Maintained
126 F: ntoskrnl/
127
128 Network Drivers
129 M:
130 R: ThFabba, Thomas Faber
131 S: Maintained
132 F: drivers/network/
133
134 Network File Systems kernel libraries
135 M: HeisSpiter, Pierre Schweitzer
136 S: Maintained
137 F: sdk/lib/drivers/rdbsslib/
138 F: sdk/lib/drivers/rxce/
139
140 NTDLL
141 M:
142 R: HeisSpiter, Pierre Schweitzer
143 R: learn-more, learn_more, Mark Jansen
144 R: ThFabba, Thomas Faber
145 S: Maintained
146 F: dll/ntdll/
147
148 ReactOS API Tests
149 M:
150 R: learn-more, learn_more, Mark Jansen
151 R: ThFabba, Thomas Faber
152 S: Maintained
153 F: modules/rostests/apitests/
154
155 ReactOS Kernel-Mode Tests
156 M: ThFabba, Thomas Faber
157 S: Maintained
158 F: modules/rostests/kmtests/
159
160 ROS internals tools
161 M: HeisSpiter, Pierre Schweitzer
162 S: Maintained
163 F: modules/rosapps/applications/rosinternals/
164
165 Run-Time Library (RTL)
166 M:
167 R: learn-more, learn_more, Mark Jansen
168 R: ThFabba, Thomas Faber
169 S: Maintained
170 F: sdk/lib/rtl/
171
172 Shell Extensions
173 M:
174 R: learn-more, learn_more, Mark Jansen
175 S: Maintained
176 F: dll/shellext
177
178 Upstream File Systems
179 M: HeisSpiter, Pierre Schweitzer
180 S: Upstream
181 F: base/services/nfsd/
182 F: dll/np/nfs/
183 F: dll/shellext/shellbtrfs/
184 F: drivers/filesystems/btrfs/
185 F: drivers/filesystems/cdfs/
186 F: drivers/filesystems/ext2/
187 F: drivers/filesystems/fastfat_new/
188 F: drivers/filesystems/ffs/
189 F: drivers/filesystems/nfs/
190 F: drivers/filesystems/reiserfs/
191 F: media/doc/README.FSD
192 F: sdk/lib/fslib/btrfslib/
193 F: sdk/lib/fslib/ext2lib/
194 F: sdk/lib/fslib/vfatlib/check/
195
196 USB Drivers
197 M: ThFabba, Thomas Faber
198 S: Maintained
199 F: drivers/usb/
200 F: sdk/lib/drivers/libusb/
201 F: sdk/include/reactos/drivers/usbport/
202
203 Virtual CD-ROM
204 M: HeisSpiter, Pierre Schweitzer
205 S: Maintained
206 F: modules/rosapps/applications/cmdutils/vcdcli/
207 F: modules/rosapps/drivers/vcdrom/
208
209 Virtual Floppy Disk
210 M: HeisSpiter, Pierre Schweitzer
211 S: Upstream
212 F: modules/rosapps/applications/cmdutils/vfdcmd/
213 F: modules/rosapps/drivers/vfd/
214
215 Win32 file functions
216 M: HeisSpiter, Pierre Schweitzer
217 S: Maintained
218 F: dll/win32/kernel32/client/file/
219
220 Windows Network File Systems functions
221 M: HeisSpiter, Pierre Schweitzer
222 S: Upstream
223 F: dll/win32/mpr/wnet.c
224
225 Wine Tests
226 M:
227 R: ThFabba, Thomas Faber
228 S: Upstream
229 F: modules/rostests/winetests/