[DOCS] Replace MAINTAINERS file with CODEOWNERS

This commit is contained in:
Timo Kreuzer 2019-06-30 16:12:58 +02:00
parent 433c9d327e
commit 46c052e0f2
2 changed files with 302 additions and 271 deletions

302
CODEOWNERS Normal file
View file

@ -0,0 +1,302 @@
## 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
## - 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
## - 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. 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.
## 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.
## 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 GitHub's format for specifying code owners.
## - Lines starting with # are comment lines.
## - All other lines specify a path / file (wildcards allowed) followed
## by the GitHub user name(s) of the code owners.
## See https://help.github.com/en/articles/about-code-owners
## Additionally it tries to use a similar format to the Linux kernel
## MAINTAINERS file within comments.
## Descriptions of comment 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
# 3rd Party File Format Libraries
# M: ThFabba, Thomas Faber
# S: Upstream
# C: See media/doc/3rd Party Files.txt
/dll/3rdparty/libjpeg/ @ThFabba
/dll/3rdparty/libpng/ @ThFabba
/dll/3rdparty/libtiff/ @ThFabba
/dll/3rdparty/libxslt/ @ThFabba
/sdk/include/reactos/libs/libjpeg/ @ThFabba
/sdk/include/reactos/libs/libmpg123/ @ThFabba
/sdk/include/reactos/libs/libpng/ @ThFabba
/sdk/include/reactos/libs/libtiff/ @ThFabba
/sdk/include/reactos/libs/libxml/ @ThFabba
/sdk/include/reactos/libs/libxslt/ @ThFabba
/sdk/lib/3rdparty/libmpg123/ @ThFabba
/sdk/lib/3rdparty/libsamplerate/ @ThFabba
/sdk/lib/3rdparty/libxml2/ @ThFabba
# ACPI
# M:
# R: ThFabba, Thomas Faber
# S: Maintained
/drivers/bus/acpi/ @ThFabba
/hal/halx86/acpi/ @ThFabba
# ACPICA Library
# M: ThFabba, Thomas Faber
# S: Upstream
/drivers/bus/acpi/acpica/ @ThFabba
# Apisets
# M: learn-more, learn_more, Mark Jansen
# S: Maintained
/dll/apisets/ @learn-more
# Application Compatibility subystem
# M: learn-more, learn_more, Mark Jansen
# S: Maintained
/dll/appcompat/ @learn-more
/dll/shellext/acppage/ @learn-more
/ntoskrnl/ps/apphelp.c @learn-more
# Cache Manager
# M: HeisSpiter, Pierre Schweitzer
# S: Maintained
/modules/rostests/kmtests/ntos_cc/ @HeisSpiter
/ntoskrnl/cc/ @HeisSpiter
# Cache Manager Rewrite
# S: Abandoned
/ntoskrnl/cache/
# CMake Build Scripts
# M:
# R: learn-more, learn_more, Mark Jansen
# R: ThFabba, Thomas Faber
# S: Maintained
/sdk/cmake/ @learn-more @ThFabba
CMakeLists.txt @learn-more @ThFabba
*.cmake @learn-more @ThFabba
# File Patch API
# M: learn-more, learn_more, Mark Jansen
# S: Maintained
/dll/win32/mspatcha/ @learn-more
# File Systems
# M: HeisSpiter, Pierre Schweitzer
# S: Maintained
# C: Also see "Upstream File Systems"
/drivers/filesystems/ @HeisSpiter
/sdk/lib/fslib/ @HeisSpiter
# File Systems Run Time Library
# M: HeisSpiter, Pierre Schweitzer
# S: Maintained
/modules/rostests/kmtests/ntos_fsrtl/ @HeisSpiter
/modules/rostests/kmtests/novp_fsrtl/ @HeisSpiter
/ntoskrnl/fsrtl/ @HeisSpiter
/sdk/lib/drivers/ntoskrnl_vista/fsrtl.c @HeisSpiter
# Freeloader
# M:
# R: tkreuzer. ThePhysicist, Timo Kreuzer
# S: Maintained
/boot/freeldr/freeldr/ @tkreuzer
# HAL / APIC
# M: tkreuzer. ThePhysicist, Timo Kreuzer
# S: Maintained
/hal/halx86/apic/ @tkreuzer
# HID Drivers
# M:
# R: ThFabba, Thomas Faber
# S: Maintained
/drivers/hid/ @ThFabba
# Kernel
# M:
# R: HeisSpiter, Pierre Schweitzer
# R: ThFabba, Thomas Faber
# R: tkreuzer. ThePhysicist, Timo Kreuzer
# S: Maintained
/ntoskrnl/ @HeisSpiter @ThFabba @tkreuzer
# mbed TLS
# M: ThFabba, Thomas Faber
# S: Upstream
# C: See media/doc/3rd Party Files.txt
/dll/3rdparty/mbedtls/ @ThFabba
/sdk/include/reactos/libs/mbedtls/ @ThFabba
# Network Drivers
# M:
# R: ThFabba, Thomas Faber
# S: Maintained
/drivers/network/ @ThFabba
# Network File Systems kernel libraries
# M: HeisSpiter, Pierre Schweitzer
# S: Maintained
/sdk/lib/drivers/rdbsslib/ @HeisSpiter
/sdk/lib/drivers/rxce/ @HeisSpiter
# NTDLL
# M:
# R: HeisSpiter, Pierre Schweitzer
# R: learn-more, learn_more, Mark Jansen
# R: ThFabba, Thomas Faber
# R: tkreuzer. ThePhysicist, Timo Kreuzer
# S: Maintained
/dll/ntdll/ @HeisSpiter @learn-more @ThFabba @tkreuzer
# ReactOS API Tests
# M:
# R: learn-more, learn_more, Mark Jansen
# R: ThFabba, Thomas Faber
# S: Maintained
/modules/rostests/apitests/ @learn-more @ThFabba
# ReactOS Kernel-Mode Tests
# M: ThFabba, Thomas Faber
# S: Maintained
/modules/rostests/kmtests/ @ThFabba
# ROS internals tools
# M: HeisSpiter, Pierre Schweitzer
# S: Maintained
/modules/rosapps/applications/rosinternals/ @HeisSpiter
# Run-Time Library (RTL)
# M:
# R: HeisSpiter, Pierre Schweitzer
# R: learn-more, learn_more, Mark Jansen
# R: ThFabba, Thomas Faber
# R: tkreuzer. ThePhysicist, Timo Kreuzer
# S: Maintained
/sdk/lib/rtl/ @HeisSpiter @learn-more @ThFabba @tkreuzer
# Shell Extensions
# M:
# R: learn-more, learn_more, Mark Jansen
# S: Maintained
/dll/shellext @learn-more
# Upstream File Systems
# M: HeisSpiter, Pierre Schweitzer
# S: Upstream
/base/services/nfsd/ @HeisSpiter
/dll/np/nfs/ @HeisSpiter
/dll/shellext/shellbtrfs/ @HeisSpiter
/drivers/filesystems/btrfs/ @HeisSpiter
/drivers/filesystems/cdfs/ @HeisSpiter
/drivers/filesystems/ext2/ @HeisSpiter
/drivers/filesystems/fastfat_new/ @HeisSpiter
/drivers/filesystems/ffs/ @HeisSpiter
/drivers/filesystems/nfs/ @HeisSpiter
/drivers/filesystems/reiserfs/ @HeisSpiter
/media/doc/README.FSD @HeisSpiter
/sdk/lib/fslib/btrfslib/ @HeisSpiter
/sdk/lib/fslib/ext2lib/ @HeisSpiter
/sdk/lib/fslib/vfatlib/check/ @HeisSpiter
# USB Drivers
# M: ThFabba, Thomas Faber
# S: Maintained
/drivers/usb/ @ThFabba
/sdk/lib/drivers/libusb/ @ThFabba
/sdk/include/reactos/drivers/usbport/ @ThFabba
# Virtual CD-ROM
# M: HeisSpiter, Pierre Schweitzer
# S: Maintained
/modules/rosapps/applications/cmdutils/vcdcli/ @HeisSpiter
/modules/rosapps/applications/vcdcontroltool/ @HeisSpiter
/modules/rosapps/drivers/vcdrom/ @HeisSpiter
# Virtual Floppy Disk
# M: HeisSpiter, Pierre Schweitzer
# S: Upstream
/modules/rosapps/applications/cmdutils/vfdcmd/ @HeisSpiter
/modules/rosapps/drivers/vfd/ @HeisSpiter
# Win32 file functions
# M: HeisSpiter, Pierre Schweitzer
# S: Maintained
/dll/win32/kernel32/client/file/ @HeisSpiter
# Windows Network File Systems functions
# M: HeisSpiter, Pierre Schweitzer
# S: Upstream
/dll/win32/mpr/wnet.c @HeisSpiter
# Wine Tests
# M:
# R: ThFabba, Thomas Faber
# S: Upstream
/modules/rostests/winetests/ @ThFabba
# zlib
# M: ThFabba, Thomas Faber
# S: Upstream
# C: See media/doc/3rd Party Files.txt
/sdk/include/reactos/libs/zlib/ @ThFabba
/sdk/lib/3rdparty/zlib/ @ThFabba
# x64 related code (keep this at the bottom)
# M: tkreuzer. ThePhysicist, Timo Kreuzer
# S: Maintained
amd64/ @tkreuzer
/boot/freeldr/freeldr/arch/realmode/amd64.S @tkreuzer
# Translations
de-DE.rc @reactos/lang-german

View file

@ -1,271 +0,0 @@
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
- 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
- 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. 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.
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.
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
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
3rd Party File Format Libraries
M: ThFabba, Thomas Faber
S: Upstream
F: dll/3rdparty/libjpeg/
F: dll/3rdparty/libpng/
F: dll/3rdparty/libtiff/
F: dll/3rdparty/libxslt/
F: sdk/include/reactos/libs/libjpeg/
F: sdk/include/reactos/libs/libmpg123/
F: sdk/include/reactos/libs/libpng/
F: sdk/include/reactos/libs/libtiff/
F: sdk/include/reactos/libs/libxml/
F: sdk/include/reactos/libs/libxslt/
F: sdk/lib/3rdparty/libmpg123/
F: sdk/lib/3rdparty/libsamplerate/
F: sdk/lib/3rdparty/libxml2/
C: See media/doc/3rd Party Files.txt
ACPI
M:
R: ThFabba, Thomas Faber
S: Maintained
F: drivers/bus/acpi/
F: hal/halx86/acpi/
ACPICA Library
M: ThFabba, Thomas Faber
S: Upstream
F: drivers/bus/acpi/acpica/
Apisets
M: learn-more, learn_more, Mark Jansen
S: Maintained
F: dll/apisets
Application Compatibility subystem
M: learn-more, learn_more, Mark Jansen
S: Maintained
F: dll/appcompat
F: dll/shellext/acppage
F: ntoskrnl/ps/apphelp.c
Cache Manager
M: HeisSpiter, Pierre Schweitzer
S: Maintained
F: modules/rostests/kmtests/ntos_cc/
F: ntoskrnl/cc/
Cache Manager Rewrite
S: Abandoned
F: ntoskrnl/cache/
CMake Build Scripts
M:
R: learn-more, learn_more, Mark Jansen
R: ThFabba, Thomas Faber
S: Maintained
F: sdk/cmake/
F: */CMakeLists.txt
F: */*.cmake
File Patch API
M: learn-more, learn_more, Mark Jansen
S: Maintained
F: dll/win32/mspatcha
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: modules/rostests/kmtests/ntos_fsrtl/
F: modules/rostests/kmtests/novp_fsrtl/
F: ntoskrnl/fsrtl/
F: sdk/lib/drivers/ntoskrnl_vista/fsrtl.c
HID Drivers
M:
R: ThFabba, Thomas Faber
S: Maintained
F: drivers/hid/
Kernel
M:
R: HeisSpiter, Pierre Schweitzer
R: ThFabba, Thomas Faber
S: Maintained
F: ntoskrnl/
mbed TLS
M: ThFabba, Thomas Faber
S: Upstream
F: dll/3rdparty/mbedtls/
F: sdk/include/reactos/libs/mbedtls/
C: See media/doc/3rd Party Files.txt
Network Drivers
M:
R: ThFabba, Thomas Faber
S: Maintained
F: drivers/network/
Network File Systems kernel libraries
M: HeisSpiter, Pierre Schweitzer
S: Maintained
F: sdk/lib/drivers/rdbsslib/
F: sdk/lib/drivers/rxce/
NTDLL
M:
R: HeisSpiter, Pierre Schweitzer
R: learn-more, learn_more, Mark Jansen
R: ThFabba, Thomas Faber
S: Maintained
F: dll/ntdll/
ReactOS API Tests
M:
R: learn-more, learn_more, Mark Jansen
R: ThFabba, Thomas Faber
S: Maintained
F: modules/rostests/apitests/
ReactOS Kernel-Mode Tests
M: ThFabba, Thomas Faber
S: Maintained
F: modules/rostests/kmtests/
ROS internals tools
M: HeisSpiter, Pierre Schweitzer
S: Maintained
F: modules/rosapps/applications/rosinternals/
Run-Time Library (RTL)
M:
R: HeisSpiter, Pierre Schweitzer
R: learn-more, learn_more, Mark Jansen
R: ThFabba, Thomas Faber
S: Maintained
F: sdk/lib/rtl/
Shell Extensions
M:
R: learn-more, learn_more, Mark Jansen
S: Maintained
F: dll/shellext
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/
USB Drivers
M: ThFabba, Thomas Faber
S: Maintained
F: drivers/usb/
F: sdk/lib/drivers/libusb/
F: sdk/include/reactos/drivers/usbport/
Virtual CD-ROM
M: HeisSpiter, Pierre Schweitzer
S: Maintained
F: modules/rosapps/applications/cmdutils/vcdcli/
F: modules/rosapps/applications/vcdcontroltool/
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
Wine Tests
M:
R: ThFabba, Thomas Faber
S: Upstream
F: modules/rostests/winetests/
zlib
M: ThFabba, Thomas Faber
S: Upstream
F: sdk/include/reactos/libs/zlib/
F: sdk/lib/3rdparty/zlib/
C: See media/doc/3rd Party Files.txt