From b315c69f0cc46bd69688ed75a91e4c1fbf627182 Mon Sep 17 00:00:00 2001 From: Chandler Carruth Date: Tue, 18 Oct 2022 10:59:08 -0700 Subject: [PATCH] Begin publishing CoC and moderation transparency reports. (#2295) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Provides a documented cadence, publishing target, and template for Code of Conduct and moderation transparency reports. Based on the initial proposal draft from @CelineausBerlin. Co-authored-by: Céline Dedaj --- docs/project/transparency_reports.md | 81 +++++++++++++++++ proposals/p2295.md | 125 +++++++++++++++++++++++++++ 2 files changed, 206 insertions(+) create mode 100644 docs/project/transparency_reports.md create mode 100644 proposals/p2295.md diff --git a/docs/project/transparency_reports.md b/docs/project/transparency_reports.md new file mode 100644 index 000000000000..198e1a72b1c3 --- /dev/null +++ b/docs/project/transparency_reports.md @@ -0,0 +1,81 @@ +# Conduct and moderation transparency reports + + + +## Overview + +Carbon regularly publishes transparency reports that cover conduct issues that +have come up in our spaces as well as the moderation and other actions taken in +response. We prioritize keeping the Carbon community [welcoming and inclusive]() +and believe this kind of transparency is essential to sustaining that. + +## Cadence and publishing + +We publish a report quarterly in a GitHub discussion thread in the +[transparency reports](https://github.com/carbon-language/carbon-lang/discussions/categories/transparency-reports) +topic. We use the following template for each of these reports. + +We may publish outside of the quarterly cycle if needed for an urgent response. + +## Template + +The Carbon community works to be welcoming and kind among itself and to others, +with a deep commitment to psychological safety, and we want to ensure that +doesn’t change as we grow and evolve. To that end, we have a few ground rules +that we ask all community members to adhere to: + +- be welcoming, +- be friendly and patient, +- be considerate, +- be kind, +- be careful in the words that we choose, when we disagree, we try to + understand why, and recognize when progress has stopped, and take a step + back. + +The following summary is intended to help the community understand what kinds of +Code of Conduct (CoC) incidents were brought to our attention lately, and how we +dealt with them. + +Publishing such transparency reports in the future will help us track progress +and hold ourselves accountable to high standards of community culture. + +### Summary + +_[overview with overall number of interventions and mention of major community +related events during that period]_ + +Please note that some incidents may have escaped our attention. Please help us +keep our spaces welcoming and fostering a spirit of collaboration, and report +any situation that may require our intervention: +https://github.com/carbon-language/carbon-lang/blob/trunk/CODE_OF_CONDUCT.md + +### Our interventions from _[YYYY-MM-DD (start date)]_ through _[YYYY-MM-DD (end date)]_ + +_[mention of preventive measures if applicable]_ + +These are the conduct incidents that were brought to our attention during the +last documentation period with the relevant sections of the Carbon community +Code of Conduct when this report was published: + +- > _[Quote1 from the Code of Conduct related to the following interventions]_ + + _[Number of related incidents, and corresponding moderation interventions]_ + +- > _[Quote2 from the Code of Conduct related to the following interventions]_ + + _[Number of related incidents, and corresponding moderation interventions]_ + +- > _[Quote3 from the Code of Conduct related to the following interventions]_ + + _[Number of related incidents, and corresponding moderation interventions]_ + +_[Final observations]_ + +Thank you all for helping us keep such a fantastic Carbon community, + +-- The Carbon Language community moderation team, together with the Carbon +leads. diff --git a/proposals/p2295.md b/proposals/p2295.md new file mode 100644 index 000000000000..346f7338c703 --- /dev/null +++ b/proposals/p2295.md @@ -0,0 +1,125 @@ +# Begin publishing CoC and moderation transparency reports + + + +[Pull request](https://github.com/carbon-language/carbon-lang/pull/2295) + + + +## Table of contents + +- [Abstract](#abstract) +- [Problem](#problem) +- [Background](#background) +- [Proposal](#proposal) +- [Details](#details) +- [Rationale](#rationale) +- [Alternatives considered](#alternatives-considered) + - [Automated dashboards](#automated-dashboards) + - [Different cadence](#different-cadence) + - [Different publishing options](#different-publishing-options) + + + +## Abstract + +Proposes a documented cadence, publishing target, and template for Code of +Conduct and moderation transparency reports. + +## Problem + +The Carbon community wants to be an example in terms of diversity, equity and +inclusion. One of the best practices that supports such ambition is publishing +transparency reports about misconduct within the community and actions taken in +response. There is no previous experience with reporting back to the community +about this so far. + +## Background + +Transparency reports are not very common practice, but already around. So there +are some ideas to grab from other communities, with their permission. + +## Proposal + +We will benchmark relevant transparency reports to find inspiration to create +our own. We will look at their scope, their format, their regularity and +possibly community feedback we have access to. + +We will create a template for Carbon's transparency reports and maintain that as +part of the project. Our Code of Conduct team will then create and publish +regular reports in the GitHub discussion forum based on that template. + +## Details + +Some examples of transparency reports in which conduct incidents had been +reported: + +Conferences: + +- PyCon US 2022: + https://pycon.blogspot.com/2022/06/pycon-us-2022-transparency-report.html +- CppCon 2021: https://cppcon.org/cppcon-2021-transparency-report/ +- PyConDE 2019: + https://2019.pycon.de/blog/code-of-conduct-transparency-report/ + +Other: + +- LLVM CoC July 15, 2022: https://llvm.org/coc-reports/2022-07-15-report.html +- Linux Foundation 2021: + https://www.linuxfoundation.org/blog/blog/linux-foundation-events-code-of-conduct-transparency-report-2021-event-summary + +We propose a [template](/docs/project/transparency_reports.md#template) for our +own CoC transparency report, which has been greatly inspired by transparency +reports issued by the Python community worldwide. Thank you, Pythonistas! + +We also document there the +[cadence and target of publishing](/docs/project/transparency_reports.md#cadence-and-publishing). + +## Rationale + +Transparent moderation and handling of conduct issues is essential to sustaining +a healthy [community and culture](/docs/project/goals.md#community-and-culture), +one of Carbon's primary goals. We need to clearly and transparently surface the +conduct of our community and how we respond to it. + +## Alternatives considered + +### Automated dashboards + +An automated dashboard (for example “X days since AutoMod detected a “guys” in +our Discord”, “Y incidents of harmful language”) would be great, but we are +still figuring out the basics and principles together before we can automate +more. + +Such a dashboard could be an attractive alternative for the future. + +### Different cadence + +Publishing quarterly may result in some quarters with very little or even +nothing to publish. That seems fine. We considered a slower cadence of annually, +but we worry that would be too slow for folks in the community to hold the +conduct team and leadership accountable as things start to be forgotten. + +We also thought about how to respond rapidly when needed but would prefer to +publish out-of-band when needed rather than run an even more rapid cadence. + +### Different publishing options + +We considered different places to publish the individual transparency reports. + +They don't seem to belong as part of our version controlled repository as they +aren't something that should be persistent -- they reflect a report at a moment +in time. And while we hope to never need it, we should retain the ability to +easily redact information or make permanent edits to them if necessary. GitHub +discussions seem like a good fit overall compared to alternatives like the main +repository, the wiki, etc. + +Using GitHub discussions also allows comments and discussion where folks could +for example ask questions or get more information about how and why we are +taking our moderation approaches. While there is some risk of these discussions +being unproductive, we hope to be able to moderate them as well and still +provide a place where productive and on-topic discussion can still take place.