summaryrefslogtreecommitdiff
path: root/CodeOfConduct
diff options
context:
space:
mode:
authorkarolherbst <karolherbst@web>2024-08-15 10:03:12 +0200
committerIkiWiki <ikiwiki.info>2024-08-15 10:03:12 +0200
commit7fd4b6b135707aa3d1f57db5b15f6bf7afe4db5c (patch)
tree860a7d0686d02619c905cd8c1e399ae635460957 /CodeOfConduct
parent51c9f70e6529e61088585b0e9dbda33af1032a0d (diff)
Diffstat (limited to 'CodeOfConduct')
-rw-r--r--CodeOfConduct/Processes.mdwn21
1 files changed, 21 insertions, 0 deletions
diff --git a/CodeOfConduct/Processes.mdwn b/CodeOfConduct/Processes.mdwn
index ba3a2679..c3f79658 100644
--- a/CodeOfConduct/Processes.mdwn
+++ b/CodeOfConduct/Processes.mdwn
@@ -15,3 +15,24 @@ employer if it involves an employee of the same company, or otherwise conclude
there could be a risk of a decision being driven by a Conflict of Interest,
they'll recuse themselves from participation and votings in regards to specific
incidences.
+
+## CoC Committee composition
+
+There shouldn't be more than two members from the same company to avoid the
+impression of a single company having power over the CoC Committee. There also
+should be at least 4 members on the Committee at all times.
+
+The CoC Committee should try its best to select those candidates out of
+potential ones, which would make the team more diverse in terms of represented
+projects and companies, but also in terms of cultural and social background.
+
+Anybody interested in joining the CoC Committee is free to reach out to any of
+the current members directly or to write to <conduct@lists.freedesktop.org>.
+
+It's expected that anybody joining the CoC committee to undergo CoC enforcement
+training, either the one offered by the Board of Directors or something similar
+to that.
+
+Each CoC Committee will be listed on the
+[Code of Conduct page](https://www.freedesktop.org/wiki/CodeOfConduct/#enforcement)
+including their current relevant affiliation to a company or other institution.