From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id 453083858C78 for ; Mon, 4 Dec 2023 09:27:23 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 453083858C78 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 453083858C78 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=170.10.129.124 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1701682045; cv=none; b=chcTZdW41jtezHpkFPRIxGIlpECXU8oGHA4ZdeKXr9jJFDV86QUsIpA6PSITb3hbkplcLbb4j3XTFMb2AHFXECixxR1VFoPI2SdgJW7WEXBhneOpYeTMKK/GIikmDx+BlLH49d6/3t07yw/oVhfc+VcH2ebQ5S+RpWMiqIPcTU8= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1701682045; c=relaxed/simple; bh=IarKccU+FA3+ingT+ZDbn+ygkGwdYQbQGf5INQnGizc=; h=DKIM-Signature:Message-ID:Date:MIME-Version:Subject:To:From; b=szSooOcQ++ATZWe1Iq5hHfJVZFbqoTq6IwjEme8yv4L99KL4KUCW4Hby+9fqK9dCa3QJKCp+nwyDXIOhx+6cL5CIA6uxdu3yDWaiBJlx7edi+Y1Qvo/LeoYIUxXRYgNMaznQul6D6P9jOC9XgOOxPGWypyCHnolSRyLohgS4VOU= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1701682042; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=ym9OkhN/wnFs5AHQCwR8Z8khchNVYOp/zJjXrK0R9Fw=; b=IZburjuZtp2rtfWTaf3po3WiWQmXCJrjJTmzULRIZHo4NlLjlPkWrVDfReBloCQ0LhKtu5 qbXV3U1plACqHCjm5sMum2wOsPOvQIEsZFNMlv21PV5WAO+tLedAKddyrbUyhzQbcBf5Gy dnnZZHAoGW5HkfoRy9UyCBnE0HJOPHE= Received: from mail-ej1-f69.google.com (mail-ej1-f69.google.com [209.85.218.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-553-IaK1beouNqa1rd-wEN2Gdw-1; Mon, 04 Dec 2023 04:27:21 -0500 X-MC-Unique: IaK1beouNqa1rd-wEN2Gdw-1 Received: by mail-ej1-f69.google.com with SMTP id a640c23a62f3a-a19a0e00b01so262620266b.1 for ; Mon, 04 Dec 2023 01:27:21 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701682040; x=1702286840; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=ym9OkhN/wnFs5AHQCwR8Z8khchNVYOp/zJjXrK0R9Fw=; b=VzYaqQR+G4X/xv/GeeqgnUM/czy7oOj2q2zieTxW6uYo1KBaEBLBG3XF8bzd/Bo/KV b5Jz7wDieZ1PRjj3ps6nxfEJrxo21EIQfREONcSZPXZktfPVqilbaPjZqiyhw4r+h/8u D292/CpQi4tJCrosn/i5LVRyrh0/K8H4ObGBkwiukkyO4d169ZvRLbBQRlRYt+Yux+XX 034ZOkeM426h+XqrMyFhuGiWjqiCnd/77sFod4OKHk2JtjtXjpVSxiYThaZSWnVsD9sj bFKGubRRvKL8C03+045Ehj8IqrRLB0dHCIYmz7if6Y0yFZs3vpfyvfqu66WTJTxBAifp YoHw== X-Gm-Message-State: AOJu0Yx9o3LxQmtoSBQhYrsE1mKkEsP5SubE1qKxl8Fgbm6jAJH4fSgx 1r7aswp0of1Ke3Wm8dd3FYt1BoXJZpvUA+44KfiWN55eAIasv20J1atW/WDCFc5/RV/408yjh15 t1+dVxXovpx3MGJy5zdl1pb0TMddfJQ== X-Received: by 2002:a17:906:710f:b0:a19:a19b:78cb with SMTP id x15-20020a170906710f00b00a19a19b78cbmr2900883ejj.142.1701682040409; Mon, 04 Dec 2023 01:27:20 -0800 (PST) X-Google-Smtp-Source: AGHT+IE4yobIMLU8LfhRqvHw5B/n9hxTNMLKTSlruCv2oloNtfT48Rkmf4PkUiMuJQnZfBalGhMaOw== X-Received: by 2002:a17:906:710f:b0:a19:a19b:78cb with SMTP id x15-20020a170906710f00b00a19a19b78cbmr2900874ejj.142.1701682039962; Mon, 04 Dec 2023 01:27:19 -0800 (PST) Received: from [192.168.0.129] (ip-94-112-227-180.bb.vodafone.cz. [94.112.227.180]) by smtp.gmail.com with ESMTPSA id r25-20020a170906a21900b00a1b65958c54sm1556587ejy.125.2023.12.04.01.27.19 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 04 Dec 2023 01:27:19 -0800 (PST) Message-ID: <0cb2eea6-f730-7374-eac1-4087935d59ba@redhat.com> Date: Mon, 4 Dec 2023 10:27:18 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.15.1 Subject: Re: Introducing a GDB Code Of Conduct To: Andrew Burgess , gdb-patches@sourceware.org References: <87edg7nsen.fsf@redhat.com> From: Guinevere Larsen In-Reply-To: <87edg7nsen.fsf@redhat.com> X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.5 required=5.0 tests=BAYES_50,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_BARRACUDACENTRAL,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H4,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 List-Id: Just dropping by to explicitly say: I am in favor of this code of conduct. -- Cheers, Guinevere Larsen She/Her/Hers On 30/11/2023 16:59, Andrew Burgess wrote: > 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. >