From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id 0Q5WJ4axaGWzghMAWB0awg (envelope-from ) for ; Thu, 30 Nov 2023 11:00:06 -0500 Authentication-Results: simark.ca; dkim=pass (1024-bit key; unprotected) header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256 header.s=mimecast20190719 header.b=CfWVQUt/; dkim-atps=neutral Received: by simark.ca (Postfix, from userid 112) id 9588D1E11B; Thu, 30 Nov 2023 11:00:06 -0500 (EST) Received: from server2.sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 7FF2D1E091 for ; Thu, 30 Nov 2023 11:00:04 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id DD5F73882659 for ; Thu, 30 Nov 2023 16:00:03 +0000 (GMT) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTPS id DF8FB385E008 for ; Thu, 30 Nov 2023 15:59:50 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org DF8FB385E008 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org DF8FB385E008 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=170.10.133.124 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1701359992; cv=none; b=xfURr91Z8LlbhmBD3zDHcADCknCZKcTbsSqOOadd/U017LUYMAJjNY5JAlO+A2G+qIgKRpyof1nq9QIWbjKtV9uPpRId0D3e4zW+aq8q+L/yJrgBl71nZV73Q8TARVojAoNuJtrz/890APK/nxp1GwCFRNv/mGjR9v+8Ihb5QsA= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1701359992; c=relaxed/simple; bh=MviNJTcUfgnTKYsniJ9DHPey4Br8YBGQq8RriUD2/LU=; h=DKIM-Signature:From:To:Subject:Date:Message-ID:MIME-Version; b=n/xbjMl4Fcno5VL+2ZEF3V8rFU5230IKT1e8cXvDJOZlJWBAEUTWj6DjZzsUV9mLcTNZOO4mOJHOnvECsAuPXGdzS9K1DNVp1wWHRHaDLcMc63PFjVWHcURVTTUTMa/SzE83ugqF9JPWLlVGpxy84xs3s7NpzPotPUG8m9HCKoo= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1701359990; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=AEgNHd5xvR+MYCbJPlRSCQqKUywgcZMXUvkOZDuN8ZA=; b=CfWVQUt/2+19Jt7pR5ZvMwMtBQigGE4XovGmnKB22lNVirYILus2K7r+QTN/KB8BDIeRYr 4xeF/AgjqvPy/KqEsAWq/KSO9BO5id/q/pZpcVG8IHlHVuC7XnR1YnAVACV5V7bLpSELAJ Lj+siPvmEcFk8859levt8E9wfu5Uamo= Received: from mail-lj1-f200.google.com (mail-lj1-f200.google.com [209.85.208.200]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-690-EzGfFsNFPZuV42jSNTa5uw-1; Thu, 30 Nov 2023 10:59:48 -0500 X-MC-Unique: EzGfFsNFPZuV42jSNTa5uw-1 Received: by mail-lj1-f200.google.com with SMTP id 38308e7fff4ca-2c9b18161b6so12432881fa.3 for ; Thu, 30 Nov 2023 07:59:48 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701359987; x=1701964787; h=mime-version:message-id:date:subject:to:from:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=AEgNHd5xvR+MYCbJPlRSCQqKUywgcZMXUvkOZDuN8ZA=; b=QX10J1nGxYsmDgtrouReom+nk9SZeGwa2m9/RRQEsmZX090V7JEuKE8G/puNQWBxiZ YWkiuOoHpHSZJ4LBDIWmMDLVgw5UNwWHnrRovmzvVLVBd5MTvelMr3P7O31/anBOnIXO /GCfI28KPVgCK7u/mlgw4W5d8sHRhaWvpvxuctzKLrFR417L2kiW9uJNdz2zJo53+d+E HBYuKBVxdWTMz1zsONLfjzot93WLedWuYuOnH+VocW10pb2OdAIXPzVNDloDfhsl+apU 20uAkbH8e9ydBikhAijCchCooYwNz8yMV04zt9L96Ep/oPHe10+Tlp5p2GT14zWwA7e7 lOHA== X-Gm-Message-State: AOJu0YwY9XycCQLeWDtKNq3+CbuNwLcySDocdISS7BeovZEtPPfXJ2XR bbXnTMr8HTyZVxI+D+O0eyqksaIZqagrKysmndtmggILt0rvsBHrVUftQECLFqfGbflkpjT/3gA SYWK0YvKJNTK9tJ+5rV8fHkH1LRNG+Htge3lOxsWgUzRsmhK86chewqq8Pqs4GTzcM0pi3kXYc+ FDwrnjxw== X-Received: by 2002:a2e:3a03:0:b0:2c9:c03d:58c9 with SMTP id h3-20020a2e3a03000000b002c9c03d58c9mr3563178lja.28.1701359986631; Thu, 30 Nov 2023 07:59:46 -0800 (PST) X-Google-Smtp-Source: AGHT+IGV+ecrbhOO/EEpxq5yoqFlG/cz3+h9RIBUsgTrYMcWUJEVKL0/wJjN0GnhO0PB5c7Gv2ozYg== X-Received: by 2002:a2e:3a03:0:b0:2c9:c03d:58c9 with SMTP id h3-20020a2e3a03000000b002c9c03d58c9mr3563152lja.28.1701359986067; Thu, 30 Nov 2023 07:59:46 -0800 (PST) Received: from localhost (105.226.159.143.dyn.plus.net. [143.159.226.105]) by smtp.gmail.com with ESMTPSA id n16-20020a05600c501000b00407b93d8085sm6154597wmr.27.2023.11.30.07.59.45 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 30 Nov 2023 07:59:45 -0800 (PST) From: Andrew Burgess To: gdb-patches@sourceware.org Subject: Introducing a GDB Code Of Conduct Date: Thu, 30 Nov 2023 15:59:44 +0000 Message-ID: <87edg7nsen.fsf@redhat.com> MIME-Version: 1.0 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=0.9 required=5.0 tests=BAYES_50, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SEXUAL_BODY, SPF_HELO_NONE, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Greetings GDB Community! Many GNU toolchain projects have adopted a Code of Conduct (CoC) recently, and I believe that GDB should do likewise. A CoC is not about imposing new rules onto the GDB community, but is an opportunity for us to document how we already treat each other within our community, so that new people looking to engage with us can easily understand what is expected of them, and what they can expect from others. Additionally, the CoC gives a clear mechanism by which any issues a community member may have can be raised. I have discussed this proposal briefly with the other global maintainers, and their feedback was either supportive, or neutral on this topic, so I'm now opening this conversation to the wider GDB community. The text of the proposed CoC can be found at the end of this email, and I look forward to hearing people's thoughts. Like anything, the CoC should grow and evolve as the GDB community continues to grow and evolve, this is not a once and done deal. But, we need something in place to evolve from. With that in mind, unless someone identifies a show stopping issue with the text below, then I am proposing that I will make this live some time around mid-December 2023. After that changes to the CoC can be handled in the normal way, via discussion on the list. For a CoC to work, we will need a CoC committee that can respond to any issues that are raised. I believe that a CoC should be administered by the community, for the community. And so, I'm looking for active community members, ideally, with at least a year of contributions (big or small) to GDB who would be willing to volunteer to join the CoC committee. Let me know on-list or privately if you are interested, I hope the work involved would pretty minimal. If there are any other questions, then please feel free to ask. Thanks, Andrew --- The GDB Code of Conduct GDB is a Free Software project, part of the GNU Project. Like other Free Software projects, GDB and its community are made up of professionals, volunteers, and users from all over the world. This diversity is a definite strength of GDB and its community, but it also presents some unique challenges, and can sometimes lead to mis-communications, misunderstandings, and (hopefully, rarely) to frustration and unhappiness. This code presents some ground rules of conduct that we ask everyone -- leaders of the project, its developers and maintainers, its users, and those who seek help and guidance in its use -- to adhere to while they participate in activities and discussions related to GDB. The code applies to all the types of media where we discuss GDB, its development, maintenance, and use, including the GDB mailing lists and IRC channels, the GDB issue tracker, and any other GDB-related forums. Here are the rules that we ask everyone to observe: Be kind to others. Do not insult or put down other participants of discussions. Avoid any language or behavior that could be interpreted as harassment. In general, if someone asks you to stop doing or saying something as part of a discussion, then stop and find alternative words or means of making your point. Be welcoming. We strive to be a community that welcomes and supports people of all backgrounds and identities. This includes, but is not limited to, members of any race, ethnicity, culture, national origin, color, immigration status, social and economic class, educational level, sex, sexual orientation, gender identity and expression, age, size, family status, political beliefs, religion, and mental or physical ability. Be considerate. Think carefully about your words before you publish them. Think about possible consequences of misunderstanding ambiguous words, and replace them in advance with better, clearer ones. Be friendly and patient when communicating with others. Always assume the other participants in a discussion are likely to speak up in good-faith, even if they disagree with you. Remember that most people here write in a language that is not their first one, so in many cases misunderstandings or unfortunate choice of words can easily be explained by that and not by ill will or hostility. Be respectful to participants in discussions and other members of the community, even if you are arguing with them. Not all of us will agree all the time, but disagreement is no excuse for poor behavior and poor manners. Try to understand the causes for the disagreement, and convince rather than suppress dissenting opinions. It is important that we resolve disagreements and differing views constructively; doing so will more often than not result in superior decisions and courses of action, as it draws on the varied backgrounds and different perspectives each one of us has on the issues at hand. The above isn't an exhaustive list; rather, take it in its spirit, as guidelines intended to make the GDB project as welcoming as possible to everyone who wants to participate and contribute, and to allow everyone to speak up freely in the interests of developing GDB and making our community broader and better. See the GNU Kind Communications Guidelines for more guidance on constructive interactions. People who violate this code of conduct should be made aware of their misconduct. In many cases, but not always, this will happen in the same forum where the problematic behavior happened: usually, one or more members of the GDB community will react to any such violation. If that doesn't happen, don't hesitate to speak up and explain why some behavior hurts you or might hurt someone else. Alternatively, you can write to the code of conduct committee at gdb-conduct@sourceware.org, and report the behavior you think is in violation of this code. However the violation is brought to the attention of the code of conduct committee, one or more of them will then decide how best to handle each such situation. Some ways in which they may to respond include: . Explaining to the individual(s) who violated the CoC, either in public or in private email, which part of their conduct is unacceptable and why; . Requesting, repeatedly if needed, that the problematic behavior be stopped, and asking to post an apology if deemed appropriate; . In extreme cases, moderating or blocking the messages of person(s) who violated the CoC, when repeated requests to refrain from unacceptable behavior don't help. Alternatively, the code of conduct committee might decide that the behavior is not in violation of the CoC, in which case they will work with the person who reported it to explain why they believe so. The decision how to handle each potential violation, which of these and other measures to take and in what order, is up to the code of conduct committee, based on any input provided by members of the community (which is always welcome), and also based on the committee's best judgement of what are the most appropriate actions in each case. We call upon the community to accept the decisions of the code of conduct committee in each such case and not try to force them to respond to such incidents in other ways.