Skip to content

Commit 8d821c9

Browse files
Merge pull request #108 from include-cpp/coc-update
Transparency Report and automatic index
2 parents 28c96b9 + cc024af commit 8d821c9

11 files changed

+74
-18
lines changed

_config.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -277,6 +277,7 @@ tag_archive:
277277
# category: /categories/:name/
278278
# tag: /tags/:name/
279279

280+
categories: [communication, report, cppcon]
280281

281282
# HTML Compression
282283
# - https://jch.penibelst.de/

_data/navigation.yml

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,13 +21,18 @@ sidebar:
2121
url: /what-can-i-do/
2222
- title: "Community sponsors"
2323
url: /community-sponsors/
24+
- title: "Code of Conduct"
25+
url: /discord/
26+
children:
27+
- title: "Our Code of conduct"
28+
url: /code-of-conduct/
29+
- title: "Transparency reports"
30+
url: /reports/
2431
- title: Discord Server
2532
url: /discord/
2633
children:
2734
- title: "Join Discord"
2835
url: /discord/
29-
- title: "Code of conduct"
30-
url: /code-of-conduct/
3136
- title: "Moderation"
3237
url: /moderation/
3338
- title: Conferences and Events
@@ -41,6 +46,8 @@ sidebar:
4146
url: /conferences/organising-conferences/
4247
- title: "Toolbox"
4348
url: https://github.com/include-cpp/toolboxes/blob/main/README.md
49+
- title: "Communications"
50+
url: /posts/
4451
- title: "Shop"
4552
url: /shop/
4653
children:

index.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -6,13 +6,13 @@ toc: true
66

77
## CppCon Safety
88

9-
[#include <C++> update on CppCon](/posts/cppcon-update/)
10-
11-
[#include <C++> stands with Patricia](/posts/patricia-statement-of-support/)
12-
13-
[Our communication regarding CppCon 2021.](/posts/communication-cppcon/)
14-
15-
[About the unapproved release of some working documents.](/posts/communication-working-document/)
9+
<ul>
10+
{% for page in site.pages reversed %}
11+
{% if page.categories contains 'cppcon' %}
12+
<li><a href="{{ page.url }}">{{ page.title }}</a></li>
13+
{% endif %} <!-- resource-p -->
14+
{% endfor %} <!-- page -->
15+
</ul>
1616

1717
{% include_relative conferences/current_funding_campaign.md %}
1818

moderation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ title: "#include <C++> Discord Moderation Guidelines"
66
Introduction
77
------------
88

9-
It is important that all users’ questions, answers and comments are in line with the [`#include` Discord Code of Conduct]({{site.baseurl}}/code-of-conduct), as well as with the category and topic, or channel, they belong to. When deciding to approach a user, moderators and administrators must always assume intentions are good, which is usually the case. Over-moderation is harmful to the atmosphere of the community and should be avoided.
9+
It is important that all users’ questions, answers and comments are in line with the [`#include <C++>` Code of Conduct]({{site.baseurl}}/code-of-conduct), as well as with the category and topic, or channel, they belong to. When deciding to approach a user, moderators and administrators must always assume intentions are good, which is usually the case. Over-moderation is harmful to the atmosphere of the community and should be avoided.
1010

1111
Expectations for moderator enforcement
1212
--------------------------------------

posts/communication-working-document.md renamed to posts/20220308-communication-working-document.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
---
22
layout: archive
33
title: "Communication about our working document"
4+
categories: [communication, cppcon]
45
---
56

67
8 March 2022
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,7 @@
22
layout: home
33
title: "#include <C++> Position on CppCon Safety"
44
toc: true
5+
categories: [communication, cppcon]
56
---
67

78
14 March 2022

posts/patricia-statement-of-support.md renamed to posts/20220318-patricia-statement-of-support.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
---
22
layout: archive
33
title: "#include <C++> stands with Patricia"
4+
categories: [communication, cppcon]
45
---
56

67
18 March 2022
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,7 @@
22
layout: home
33
title: "#include <C++> Update on CppCon"
44
toc: true
5+
categories: [communication, cppcon]
56
---
67

78
23 June 2022

posts/index.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
---
22
layout: home
3-
title: "Our Posts"
3+
title: "Our Communications"
44
---
55

6-
[#include <C++> update on CppCon](/posts/cppcon-update/)
7-
8-
[#include <C++> stands with Patricia](/posts/patricia-statement-of-support/)
9-
10-
[Our communication regarding CppCon 2021.](/posts/communication-cppcon/)
11-
12-
[About the unapproved release of some working documents.](/posts/communication-working-document/)
6+
<ul>
7+
{% for page in site.pages reversed %}
8+
{% if page.categories contains 'communication' %}
9+
<li><a href="{{ page.url }}">{{ page.title }}</a></li>
10+
{% endif %} <!-- resource-p -->
11+
{% endfor %} <!-- page -->
12+
</ul>

reports/20220720_report.md

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
---
2+
layout: home
3+
title: "July 20th 2022 Transparency Report"
4+
toc: true
5+
categories: [report]
6+
---
7+
8+
`#include <C++>` is an unincorporated international group of volunteers, who conduct business through a discord server.
9+
10+
On July 20th 2022 a `#include <C++>` code of conduct complaint was raised against an admin. The subject of the complaint was a tweet posted on the admin's personal Twitter account that was strongly disparaging toward two prominent C++ community members. The plaintiff arguments were that this tweet was against our mission of building a friendly community and that the tweet could be considered as libel which was a crime.
11+
12+
The recipient of the complaint spoke to the admins except for the target of the complaint. They decided to create a separate discord server and invite moderators from the `#include <C++>` server to discuss the complaint. Eleven moderators and admins joined the discussion, which commenced on July 21st.
13+
14+
The team decided that the tweet was not a violation of the `#include <C++>` code of conduct in the way that the reporter flagged (9 no)
15+
16+
The team decided that the tweet was not a violation of any other part of the code of conduct. (9 no)
17+
18+
The team decided that there should be no immediate adjustment to the code of conduct. There was no agreement whether there should be later adjustment. (1 yes, 4 no, 4 later)
19+
20+
There was strong agreement that the team issue a response to the person the report was against.
21+
(9 yes)
22+
23+
The team reported back to the reported individual to tell them about the complaint and inform them that it was not considered a breach of the CoC. In the same report, the team also gave feedback on the tweet, pointing out concerns some of the members of the team had, but without requiring any specific action from the reported individual.
24+
This was supported by 8 members, a two-thirds majority. The message was sent to the subject of the complaint at July 25th 2022, 19:14 UTC
25+
26+
During discussion, the group agreed to pin a new tweet to the #include twitter account:
27+
28+
> “#​include <C++> is an international group of volunteers with plural and diverse opinions and backgrounds. It cannot be assumed that a personal tweet can represent our position: only tweets from this account do so. They are arrived at by building consensus, which can be very slow.”
29+
30+
It should be noted that none of the agreements reported here were unanimous: although there were no objections to some proposals, there were abstentions on every vote.
31+
32+
Also, there was no recorded process for handling CoC complaints. This will be addressed shortly. Historically, we have used channels with participation restricted to organisers, moderators and admins.

0 commit comments

Comments
 (0)