From nobody Sun Nov 24 01:15:21 2024 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 5FE5B1BD9DB; Fri, 8 Nov 2024 16:18:57 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1731082737; cv=none; b=MFs1t8Ou7ExwmPzcLsQEMdAnIIqx6RhJkVZGBWuZNSd7mgZgwnAKtSo/biY/jHS5qQmg0xqbJvNS0hWCIufmsoFNXpQJxA+DSrVYA0t/MwojaBq77hnbUnD8+VERoIE47GpZcd/XeLJMb0WLLsjOFct51etxC+OrYl5cte9chUY= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1731082737; c=relaxed/simple; bh=5fmDrDaI733DzNBUuUddNJBVI9S5jMQGEEa6zN6Z2Fg=; h=From:To:Cc:Subject:Date:Message-Id:MIME-Version; b=LlcbsJHSl/zoCyrQ5Nvg9EpkmvM09SwvjDEpvXe85sIL2CnFquJI7b/zKmpk0S2CtsdizVmbQpbnyHmaYZ4DVSVIg32piRmf9NPtVq52LgxokIrlrt15slKBo3S4LKvrpr6HzOFuxquEJl5DuT5sEDBt69F+IvW1uG9I2QtwQx4= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=LS/MR9sZ; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="LS/MR9sZ" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 8E746C4CECD; Fri, 8 Nov 2024 16:18:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1731082737; bh=5fmDrDaI733DzNBUuUddNJBVI9S5jMQGEEa6zN6Z2Fg=; h=From:To:Cc:Subject:Date:From; b=LS/MR9sZWlWh5bk47vCMHWuKknjXZVYtqz3R5VS8w0ultVXKzTNQWz/tiJ96w+zuu y+7oN1l6Tg78EyPDMJ7cEuP1pVXqIhOGWYvjjzcJOxPWcjIoBGhCeVQ3sn6H4zTu7y JegmedANk+DDjcvjseIJ5kfQUgtdkEVEqTLCeJ2M= From: Shuah Khan To: gregkh@linuxfoundation.org, corbet@lwn.net Cc: Shuah Khan , workflows@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, Linus Torvalds , Miguel Ojeda , Dave Hansen , Steven Rostedt , Dan Williams Subject: [PATCH] Documentation/CoC: spell out enforcement for unacceptable behaviors Date: Fri, 8 Nov 2024 09:18:53 -0700 Message-Id: <20241108161853.12325-1-skhan@linuxfoundation.org> X-Mailer: git-send-email 2.40.1 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" The Code of Conduct committee's goal first and foremost is to bring about change to ensure our community continues to foster respectful discussions. In the interest of transparency, the CoC enforcement policy is formalized for unacceptable behaviors. Update the Code of Conduct Interpretation document with the enforcement information. Acked-by: Linus Torvalds Acked-by: Greg Kroah-Hartman Acked-by: Miguel Ojeda Acked-by: Dave Hansen Acked-by: Jonathan Corbet Acked-by: Steven Rostedt Acked-by: Dan Williams Signed-off-by: Shuah Khan Acked-by: Theodore Ts'o --- .../code-of-conduct-interpretation.rst | 52 +++++++++++++++++++ 1 file changed, 52 insertions(+) diff --git a/Documentation/process/code-of-conduct-interpretation.rst b/Doc= umentation/process/code-of-conduct-interpretation.rst index 66b07f14714c..21dd1cd871d2 100644 --- a/Documentation/process/code-of-conduct-interpretation.rst +++ b/Documentation/process/code-of-conduct-interpretation.rst @@ -156,3 +156,55 @@ overridden decisions including complete and identifiab= le voting details. Because how we interpret and enforce the Code of Conduct will evolve over time, this document will be updated when necessary to reflect any changes. + +Enforcement for Unacceptable Behavior Code of Conduct Violations +---------------------------------------------------------------- + +The Code of Conduct committee works to ensure that our community continues +to be inclusive and fosters diverse discussions and viewpoints, and works +to improve those characteristics over time. The Code of Conduct committee +takes measures to restore productive and respectful collaboration when an +unacceptable behavior has negatively impacted that relationship. + +Seek public apology for the violation +************************************* + +The Code of Conduct Committee publicly calls out the behavior in the +setting in which the violation has taken place, seeking public apology +for the violation. + +A public apology for the violation is the first step towards rebuilding +the trust. Trust is essential for the continued success and health of the +community which operates on trust and respect. + +Remedial measures if there is no public apology for the violation +***************************************************************** + +The Code of Conduct Committee determines the next course of action +to restore the healthy collaboration by recommending remedial measure(s) +to the TAB for approval. + +- Ban violator from participating in the kernel development process for + a period of up to a full kernel development cycle. The Code of Conduct + Committtee could require public apology as a condition for lifting the + ban. + +The scope of the ban for a period of time could include: + + a. denying patch contributions and pull requests + b. pausing collaboration with the violator by ignoring their + contributions and/or blocking their email account(s) + c. blocking their access to kernel.org accounts and mailing lists + +Once the TAB approves one or more of the measures outlined in the scope of +the ban by a two-thirds vote, the Code of Conduct Committee will enforce +the TAB approved measure(s) in collaboration with the community, maintaine= rs, +sub-maintainers, and kernel.org administrators. + +The effectiveness of the remedial measure(s) approved by the TAB depends +on the trust and cooperation from the community, maintainers, sub-maintain= ers, +and kernel.org administrators in enforcing them. + +The Code of Conduct Committee sincerely hopes that unacceptable behaviors +that require seeking public apologies continue to be exceedingly rare +occurrences in the future. --=20 2.40.1