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