docs: update CONTRIBUTING with some community guidelines

Acked-by: Tom Hromatka <tom.hromatka@oracle.com>
Signed-off-by: Paul Moore <paul@paul-moore.com>

2 files changed, 33 insertions, 1 deletions

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 76e2bb2..7130b90 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,4 +1,4 @@
-How to Submit Patches to the libseccomp Project
+How to Contribute to the libseccomp Project
 ===============================================================================
 https://github.com/seccomp/libseccomp
 
@@ -8,6 +8,20 @@ to the rules described here, but by following the instructions below you
 should have a much easier time getting your work merged with the upstream
 project.
 
+## Interacting with the Community
+
+> "Be excellent to each other." - *Bill S. Preston, Esq.*
+
+The libseccomp project aims to be a welcoming place and we ask that anyone who
+interacts with the project, and the greater community, treat each other with
+dignity and respect.  Individuals who do not behave in such a manner will be
+warned and asked to adjust their behavior; in extreme cases the individual
+may be blocked from the project.
+
+Examples of inappropriate behavior includes: profane, abusive, or prejudicial
+language directed at another person, vandalism (e.g. GitHub issue/PR "litter"),
+or spam.
+
 ## Test Your Code Using Existing Tests
 
 There are three possible tests you can run to verify your code.  The first
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