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: modules/rostests/kmtests/ntos_cc/
  88         F: ntoskrnl/cc/
  89
  90 Cache Manager Rewrite
  91         S: Abandoned
  92         F: ntoskrnl/cache/
  93
  94 CMake Build Scripts
  95         M:
  96         R: learn-more, learn_more, Mark Jansen
  97         R: ThFabba, Thomas Faber
  98         S: Maintained
  99         F: sdk/cmake/
 100         F: */CMakeLists.txt
 101         F: */*.cmake
 102
 103 File Systems
 104         M: HeisSpiter, Pierre Schweitzer
 105         S: Maintained
 106         F: drivers/filesystems/
 107         F: sdk/lib/fslib/
 108         C: Also see "Upstream File Systems"
 109
 110 File Systems Run Time Library
 111         M: HeisSpiter, Pierre Schweitzer
 112         S: Maintained
 113         F: modules/rostests/kmtests/ntos_fsrtl/
 114         F: modules/rostests/kmtests/novp_fsrtl/
 115         F: ntoskrnl/fsrtl/
 116         F: sdk/lib/drivers/ntoskrnl_vista/fsrtl.c
 117
 118 HID Drivers
 119         M:
 120         R: ThFabba, Thomas Faber
 121         S: Maintained
 122         F: drivers/hid/
 123
 124 Kernel
 125         M:
 126         R: HeisSpiter, Pierre Schweitzer
 127         R: ThFabba, Thomas Faber
 128         S: Maintained
 129         F: ntoskrnl/
 130
 131 Network Drivers
 132         M:
 133         R: ThFabba, Thomas Faber
 134         S: Maintained
 135         F: drivers/network/
 136
 137 Network File Systems kernel libraries
 138         M: HeisSpiter, Pierre Schweitzer
 139         S: Maintained
 140         F: sdk/lib/drivers/rdbsslib/
 141         F: sdk/lib/drivers/rxce/
 142
 143 NTDLL
 144         M:
 145         R: HeisSpiter, Pierre Schweitzer
 146         R: learn-more, learn_more, Mark Jansen
 147         R: ThFabba, Thomas Faber
 148         S: Maintained
 149         F: dll/ntdll/
 150
 151 ReactOS API Tests
 152         M:
 153         R: learn-more, learn_more, Mark Jansen
 154         R: ThFabba, Thomas Faber
 155         S: Maintained
 156         F: modules/rostests/apitests/
 157
 158 ReactOS Kernel-Mode Tests
 159         M: ThFabba, Thomas Faber
 160         S: Maintained
 161         F: modules/rostests/kmtests/
 162
 163 ROS internals tools
 164         M: HeisSpiter, Pierre Schweitzer
 165         S: Maintained
 166         F: modules/rosapps/applications/rosinternals/
 167
 168 Run-Time Library (RTL)
 169         M:
 170         R: HeisSpiter, Pierre Schweitzer
 171         R: learn-more, learn_more, Mark Jansen
 172         R: ThFabba, Thomas Faber
 173         S: Maintained
 174         F: sdk/lib/rtl/
 175
 176 Shell Extensions
 177         M:
 178         R: learn-more, learn_more, Mark Jansen
 179         S: Maintained
 180         F: dll/shellext
 181
 182 Upstream File Systems
 183         M: HeisSpiter, Pierre Schweitzer
 184         S: Upstream
 185         F: base/services/nfsd/
 186         F: dll/np/nfs/
 187         F: dll/shellext/shellbtrfs/
 188         F: drivers/filesystems/btrfs/
 189         F: drivers/filesystems/cdfs/
 190         F: drivers/filesystems/ext2/
 191         F: drivers/filesystems/fastfat_new/
 192         F: drivers/filesystems/ffs/
 193         F: drivers/filesystems/nfs/
 194         F: drivers/filesystems/reiserfs/
 195         F: media/doc/README.FSD
 196         F: sdk/lib/fslib/btrfslib/
 197         F: sdk/lib/fslib/ext2lib/
 198         F: sdk/lib/fslib/vfatlib/check/
 199
 200 USB Drivers
 201         M: ThFabba, Thomas Faber
 202         S: Maintained
 203         F: drivers/usb/
 204         F: sdk/lib/drivers/libusb/
 205         F: sdk/include/reactos/drivers/usbport/
 206
 207 Virtual CD-ROM
 208         M: HeisSpiter, Pierre Schweitzer
 209         S: Maintained
 210         F: modules/rosapps/applications/cmdutils/vcdcli/
 211         F: modules/rosapps/drivers/vcdrom/
 212
 213 Virtual Floppy Disk
 214         M: HeisSpiter, Pierre Schweitzer
 215         S: Upstream
 216         F: modules/rosapps/applications/cmdutils/vfdcmd/
 217         F: modules/rosapps/drivers/vfd/
 218
 219 Win32 file functions
 220         M: HeisSpiter, Pierre Schweitzer
 221         S: Maintained
 222         F: dll/win32/kernel32/client/file/
 223
 224 Windows Network File Systems functions
 225         M: HeisSpiter, Pierre Schweitzer
 226         S: Upstream
 227         F: dll/win32/mpr/wnet.c
 228
 229 Wine Tests
 230         M:
 231         R: ThFabba, Thomas Faber
 232         S: Upstream
 233         F: modules/rostests/winetests/