From patchwork Fri Nov 10 14:23:06 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Laurent Pinchart X-Patchwork-Id: 19200 Return-Path: X-Original-To: parsemail@patchwork.libcamera.org Delivered-To: parsemail@patchwork.libcamera.org Received: from lancelot.ideasonboard.com (lancelot.ideasonboard.com [92.243.16.209]) by patchwork.libcamera.org (Postfix) with ESMTPS id 6B6BDC3284 for ; Fri, 10 Nov 2023 14:23:08 +0000 (UTC) Received: from lancelot.ideasonboard.com (localhost [IPv6:::1]) by lancelot.ideasonboard.com (Postfix) with ESMTP id 9C46C629BB; Fri, 10 Nov 2023 15:23:07 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=libcamera.org; s=mail; t=1699626187; bh=a8js/rF397wKZEpbTDgFXhLVDIxXNR1M4IDJQYthQqE=; h=To:Date:Subject:List-Id:List-Unsubscribe:List-Archive:List-Post: List-Help:List-Subscribe:From:Reply-To:From; b=ANTRoN1u/E6Pn4+RACGU+3CqME8lvAZoW/bhwr8LHq05d+J5HZ2C6T80xMfGA+f3P Wxy/3qy/Hoe/QGnMbQOB7xwGAoQx6EWdeu/ay4QKxsAxVnu02bor+7q9EYL17t3uLm B26SG0NMSl0l3TiO4DLniQZvHB6p+5bVEnQeYNNhJaNYzZ3PE/StO3DcgJsS+o5Ff8 fUa41HKPBkptvM/8/yhD4kR4YnljJj2VnQFTi/85JX/8JgWqAVAc959sH0Ie5iUGdf LgK4TTic5k+bVhLFSemQWyImaPzhyV0NimmLsbwNuAceKZqitdmgFx0ZgbffJD0Uap qqG/o2NPdYH+g== Received: from perceval.ideasonboard.com (perceval.ideasonboard.com [IPv6:2001:4b98:dc2:55:216:3eff:fef7:d647]) by lancelot.ideasonboard.com (Postfix) with ESMTPS id CFF1D61DB6 for ; Fri, 10 Nov 2023 15:23:05 +0100 (CET) Authentication-Results: lancelot.ideasonboard.com; dkim=pass (1024-bit key; unprotected) header.d=ideasonboard.com header.i=@ideasonboard.com header.b="uqiXKMAL"; dkim-atps=neutral Received: from pendragon.ideasonboard.com (213-243-189-158.bb.dnainternet.fi [213.243.189.158]) by perceval.ideasonboard.com (Postfix) with ESMTPSA id 9016649E; Fri, 10 Nov 2023 15:22:42 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ideasonboard.com; s=mail; t=1699626162; bh=a8js/rF397wKZEpbTDgFXhLVDIxXNR1M4IDJQYthQqE=; h=From:To:Subject:Date:From; b=uqiXKMAL6E3MulnK5o27bYU1VipIp0o0gRPYbDVnxhpH0/8W2pwmTAXWnKfoN4iqz Sv69nPgJf7IwSYtVkZYVkF/VuP6+ceqccZpgUp3eeS5L++RaGneOHwQHh362eSa0rj RujtmzZ2QyidGBncZSRM8zxzdfuhNkdtlZEyu4ZY= To: libcamera-devel@lists.libcamera.org Date: Fri, 10 Nov 2023 16:23:06 +0200 Message-ID: <20231110142311.3818-1-laurent.pinchart@ideasonboard.com> X-Mailer: git-send-email 2.41.0 MIME-Version: 1.0 Subject: [libcamera-devel] [PATCH v1 0/5] Add a code of conduct to libcamera X-BeenThere: libcamera-devel@lists.libcamera.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-Patchwork-Original-From: Laurent Pinchart via libcamera-devel From: Laurent Pinchart Reply-To: Laurent Pinchart Errors-To: libcamera-devel-bounces@lists.libcamera.org Sender: "libcamera-devel" Hello everybody, libcamera doesn't have a formal code of conduct. This doesn't mean that the project doesn't expect its maintainers, contributors and community members in general to behave decently towards each other, only that we have never taken the time to formalize and state our expectations explicitly. Adoption of different codes of conduct in free software communities has increased over the past few years. I believe it is time for libcamera to also formalize what constitutes acceptable and non-acceptable behaviours, which I think just explicitly confirms the standards that everybody was already expecting. As indicated in the first patch in the series, codes of conduct, like software licenses, can be written in a myriad of ways. And like software licenses, using a widely adopted code of conduct instead of writing our own help bringing clarity. I propose in this series to use the Contributor Covenant v1.4([1]), stewarded by the Organization for Ethical Source. Not only is it widely adopted, it is also quite notably used by freedesktop.org, which libcamera will likely work with in the future to implement a CI infrastructure. The first patch in the series imports the Contributor Covenant Code of Conduct verbatim in its original Markdown form to ease change tracking. The rest of the patches then turn it into reST, add license and contact information, and integrate it in the documentation build. If anyone has any concern with libcamera adopting this particular code of conduct, please feel free to contact me privately for a constructive discussion if you don't feel safe expressing your concerns in public. My limited knowledge of the topic doesn't allow me to tell if wide adoption of codes of conduct have by itself made free software communities significantly better places (any pointer to serious studies on this topic would be interesting), but in any case I think it is fair to say that the process has not been detrimental, and, in particular, that the threat of weaponizing codes of conducts that have been raised in the past has never materialized. [1] https://www.contributor-covenant.org/version/1/4/code-of-conduct.html Laurent Pinchart (5): Documentation: Add code of conduct Documentation: code-of-conduct: Convert to reStructuredText Documentation: code-of-conduct: Add license information Documentation: code-of-conduct: Add contact information Documentation: contributing: Integrate the code of conduct Documentation/code-of-conduct.rst | 94 +++++++++++++++++++++++++++++++ Documentation/contributing.rst | 5 ++ Documentation/meson.build | 1 + 3 files changed, 100 insertions(+) create mode 100644 Documentation/code-of-conduct.rst base-commit: 73c7eeb3e4606853b44719a3b355e62c888df652