https://git.reactos.org/?p=reactos.git;a=commitdiff;h=ee4ee2fc1db4baf16f87a…
commit ee4ee2fc1db4baf16f87a28cf2378d983dc7e18c
Author: Eric Kohl <eric.kohl(a)reactos.org>
AuthorDate: Wed Sep 12 17:53:49 2018 +0200
Commit: Eric Kohl <eric.kohl(a)reactos.org>
CommitDate: Wed Sep 12 17:53:49 2018 +0200
[NETAPI32] Remove the obsolete file group.c
---
dll/win32/netapi32/CMakeLists.txt | 1 -
dll/win32/netapi32/group.c | 25 -------------------------
2 files changed, 26 deletions(-)
diff --git a/dll/win32/netapi32/CMakeLists.txt b/dll/win32/netapi32/CMakeLists.txt
index d714bb24b8..dab40b16eb 100644
--- a/dll/win32/netapi32/CMakeLists.txt
+++ b/dll/win32/netapi32/CMakeLists.txt
@@ -20,7 +20,6 @@ list(APPEND SOURCE
dfs.c
display.c
dssetup.c
- group.c
group_new.c
local_group.c
misc.c
diff --git a/dll/win32/netapi32/group.c b/dll/win32/netapi32/group.c
deleted file mode 100644
index e6300f2bb2..0000000000
--- a/dll/win32/netapi32/group.c
+++ /dev/null
@@ -1,25 +0,0 @@
-/*
- * Copyright 2002 Andriy Palamarchuk
- *
- * netapi32 access functions
- *
- * This library is free software; you can redistribute it and/or
- * modify it under the terms of the GNU Lesser General Public
- * License as published by the Free Software Foundation; either
- * version 2.1 of the License, or (at your option) any later version.
- *
- * This library is distributed in the hope that it will be useful,
- * but WITHOUT ANY WARRANTY; without even the implied warranty of
- * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
- * Lesser General Public License for more details.
- *
- * You should have received a copy of the GNU Lesser General Public
- * License along with this library; if not, write to the Free Software
- * Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA
- */
-
-#include "netapi32.h"
-
-WINE_DEFAULT_DEBUG_CHANNEL(netapi32);
-
-/* EOF */
https://git.reactos.org/?p=reactos.git;a=commitdiff;h=e516c2950b84d54ff66ba…
commit e516c2950b84d54ff66ba795956a1080fa06ea43
Author: Pierre Schweitzer <pierre(a)reactos.org>
AuthorDate: Mon Sep 10 18:47:29 2018 +0200
Commit: Pierre Schweitzer <pierre(a)reactos.org>
CommitDate: Wed Sep 12 08:13:28 2018 +0200
[MAINTAINERS] Define who can be maintainer and how to be added to the file
---
MAINTAINERS | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 934c42fe86..eb7763219b 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -9,6 +9,7 @@ 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
@@ -25,7 +26,8 @@ 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.
+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.
@@ -37,6 +39,10 @@ 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
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