diff options
author | Paul Moore <paul@paul-moore.com> | 2020-09-10 09:27:53 -0400 |
---|---|---|
committer | Paul Moore <paul@paul-moore.com> | 2020-09-15 14:25:47 -0400 |
commit | 3734fdc1f6a863cbef0377db1fe239791794be84 (patch) | |
tree | 9ef17875393806d29a18c7012a24f3123cb59871 /doc | |
parent | 558382e177b3c7511c915e80f7a46b22b95d3dfb (diff) | |
download | libseccomp-3734fdc1f6a863cbef0377db1fe239791794be84.tar.gz |
docs: update CONTRIBUTING with some community guidelines
Acked-by: Tom Hromatka <tom.hromatka@oracle.com>
Signed-off-by: Paul Moore <paul@paul-moore.com>
Diffstat (limited to 'doc')
-rw-r--r-- | doc/admin/MAINTAINER_PROCESS.md | 18 |
1 files changed, 18 insertions, 0 deletions
diff --git a/doc/admin/MAINTAINER_PROCESS.md b/doc/admin/MAINTAINER_PROCESS.md index 6ae61ba..f4d984a 100644 --- a/doc/admin/MAINTAINER_PROCESS.md +++ b/doc/admin/MAINTAINER_PROCESS.md @@ -89,6 +89,24 @@ there is no requirement to do so. Despite the term "moderator" the list is currently unmoderated and should remain the way. +### Handling Inappropriate Community Behavior + +The libseccomp project community is relatively small, and almost always +respectful and considerate. However, there have been some limited cases of +inappropriate behavior and it is the responsibility of the maintainers to deal +with it accordingly. + +As mentioned above, the maintainers are encouraged to communicate with each +other, and this communication is very important in this case. When +inappropriate behavior is identified in the project (e.g. mailing list, GitHub, +etc.) the maintainers should talk with each other as well as the responsible +individual to try and correct the behavior. If the individual continues to act +inappropriately the maintainers can block the individual from the project using +whatever means are available. This should only be done as a last resort, and +with the agreement of all the maintainers. In cases where a quick response is +necessary, a maintainer can unilaterally block an individual, but the block +should be reviewed by all the other maintainers soon afterwards. + ### New Project Releases The libseccomp release process is documented in the RELEASE_PROCESS.md |