summaryrefslogtreecommitdiff
path: root/Documentation/community/code_of_conduct.md
diff options
context:
space:
mode:
authorMartin Roth <gaumless@gmail.com>2024-02-19 17:39:18 -0700
committerMartin L Roth <gaumless@gmail.com>2024-10-14 15:29:46 +0000
commit7c57f9aec65506d59313bd6f09ca8c8a2e4edb4c (patch)
treeadc9d1e4c70180cf2148292bd413b235b5434841 /Documentation/community/code_of_conduct.md
parent520c6cbfb9bd18d3af000350f5c871560c00d2fc (diff)
Documentation: Update the code of conduct
This change reiterates that the coreboot leadership may revoke a user's privileges. This does not change anything, as it already says "The community organizers may take any action they deem appropriate, up to and including a temporary ban or permanent expulsion from the community without warning". Also add a note that the discussions are private. If someone wants to make the issue public, the coreboot leadership can't stop them, but the board believes in handling these issues privately. Finally, add a note that if there's an issue with someone on the arbitration board, issues may be taken directly to the leadership board. Change-Id: I5e2010a16f31f892bd1761b56b96ea773877dea0 Signed-off-by: Martin Roth <gaumless@gmail.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/80619 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Eric Lai <ericllai@google.com> Reviewed-by: David Hendricks <david.hendricks@gmail.com>
Diffstat (limited to 'Documentation/community/code_of_conduct.md')
-rw-r--r--Documentation/community/code_of_conduct.md25
1 files changed, 21 insertions, 4 deletions
diff --git a/Documentation/community/code_of_conduct.md b/Documentation/community/code_of_conduct.md
index e1f512877e..ffff110c16 100644
--- a/Documentation/community/code_of_conduct.md
+++ b/Documentation/community/code_of_conduct.md
@@ -86,8 +86,13 @@ organizers may take any action they deem appropriate, up to and including
a temporary ban or permanent expulsion from the community without warning
(and without refund in the case of a paid event).
-Community organizers can be members of the arbitration team, or organizers
-of events and online communities.
+As a part of running the project, coreboot leadership has the right to
+revoke privileges as they see fit. This is not done lightly. Over the
+history of the coreboot project, there have been only a handful of times
+where an action needed to be taken.
+
+Community organizers can be members of the arbitration team, the
+leadership board, or organizers of events and online communities.
## Addressing Grievances
@@ -95,6 +100,11 @@ If you feel you have been falsely or unfairly accused of violating this
Code of Conduct, you should notify the arbitration team with a concise
description of your grievance.
+Discussions about these actions are not done publicly, for obvious
+reasons. If someone believes that the circumstances that led to an
+action have changed, please send an email to all the members of the
+arbitration team and/or leadership board for discussion.
+
## Legal action
Threatening or starting legal action against the project, sibling
@@ -115,11 +125,18 @@ communications pertaining to community business.
## Contact info
-Our arbitration team consists of the following people
-* Stefan Reinauer <stefan.reinauer@coreboot.org> (USA)
+Our arbitration team currently consists of the following people
+* Daniel Pono Takamori <pono@sfconservancy.org> (USA)
* Ronald Minnich <rminnich@coreboot.org> (USA)
* Martin Roth <martin@coreboot.org> (USA)
+If you have an issue with someone on the arbitration team, please reach
+out to the coreboot leadership board directly.
+
+The leadership board's information can be found on the
+[coreboot Leadership and Admin Boards](https://coreboot.org/leadership.html)
+page on the website.
+
## License and attribution
This Code of Conduct is distributed under