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 28C943858D34 for ; Fri, 5 Apr 2024 20:32:41 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 28C943858D34 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 28C943858D34 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=1712349162; cv=none; b=G305/VX6ivUcRysFgLcIUMvbNSjmB6IOb00izRXIvHGLy9cospc6dTv3EIAWo6XoD5J0ZYhZBkLX+nIQ7eIvc/I64jE4gM23Y5sICSh6IKwJR7t4DBnbrsXhtd6s3ti1KRVR6zkbk67iSPfnL6txN3gZKeGonfGgT7NhM9fbbcc= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1712349162; c=relaxed/simple; bh=t1/bw8sxNd1caY+0cQsc+79HXQH0++h7eqKMNBWVtVY=; h=DKIM-Signature:Message-ID:Date:MIME-Version:Subject:To:From; b=Ic74cQFjztDKg183k78/cdmM1EYZ7KgU2hOELoZhFjFqk7GZdVLPQzhg4YDXIPtkBpsrNDQsU5aF0mKn3tzw4R9R6V+ptupFoBNDqCJJZBYtCqY9hWTT5bcsben4IajJNqo6rcMPBBlhm4FH8IlzY0FsMlVKmNV8DuDbjWZ3yvc= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1712349160; 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=FP3i4jdZzWrWbBf1hKiFLXW/Wd+1Lrx5INIcww4sE/c=; b=Pt6ygc2HRH/E3ExSFkZtMGD2ZSnTGLwI7S6hHwyHb9kMOKUppcasfnKDKn8H/CwER0u4lw NKisNVUcLY901QUJFZ+JCCUUyvE3Gk7fBuj5F4hb6oHyiDCl5n3+046oN9Ga6tqwNY+62w dtRpLe0bOZMvBznEkf0rwxruyQ9Zlko= Received: from mail-qk1-f198.google.com (mail-qk1-f198.google.com [209.85.222.198]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-357-vg_ETMjQMxafQGz3SybnfQ-1; Fri, 05 Apr 2024 16:32:39 -0400 X-MC-Unique: vg_ETMjQMxafQGz3SybnfQ-1 Received: by mail-qk1-f198.google.com with SMTP id af79cd13be357-7885dd31632so270094185a.0 for ; Fri, 05 Apr 2024 13:32:38 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712349158; x=1712953958; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=FP3i4jdZzWrWbBf1hKiFLXW/Wd+1Lrx5INIcww4sE/c=; b=hdb0VohNXIc/paHo66XrCyr6ECAKgt90CEDyMm5f01HzKIAvlqXRDr953jQBrpgZly drsw9X4s4PKd0gmMm9GI7seOW9g3H+gV4GT0c3k+ASGzAR4Tj/mFsCsFDM5zA5fLauiT vtpE375oipRmYqp8mhXDe6G8nv9L5GEzT7vdB3/hU2EcJcFFzSHkayNKqrKCDnMHUi9l uFtn8njAmkL+R7uaJx/Ixs+yd0Vbc8lzoLjKkurs6iT2HQdkJm3HUNjBtqoQpNP6ymU6 hbxpYddqH7+I6SThC9lKpADOkRZcPkust6bIeeO2TYhmguwk14Hhtg/quDbSrh78vYO8 VfxA== X-Forwarded-Encrypted: i=1; AJvYcCWVrpZYNkEjedn56pqwZPMfKZzrVyPBNJrwYVqX80iS0mrRgn2Slr1e3uJj2PZpNjvzawzSOmetVgJ3IHdxVFt+06TVApVr4rrwow== X-Gm-Message-State: AOJu0YzLcuSEksD/Av6F0ih7NFiXPRjVxA4CsLmeC8xu4D3mEiICp/qU IsqOQkbV6rRetlDzUIMdPaC5T6pk1wqZcA9IY/6fmgRDNZMB2eFVxU92Sbrqspak6D9VI8+JmlU gniJPBZXE/9Ex+ULrogRmQ5PWUpYgsQ/rvg/rpDW0Q+vQc1wxzrrWqzqeD1U= X-Received: by 2002:a05:620a:2225:b0:78d:3b54:eb49 with SMTP id n5-20020a05620a222500b0078d3b54eb49mr2403756qkh.61.1712349158515; Fri, 05 Apr 2024 13:32:38 -0700 (PDT) X-Google-Smtp-Source: AGHT+IE5nJQVTNDueXH3P4Ow2jTXCJEarZcmLG0MbMapPNRoEV7rmzFEFpuGazHoqRRvt2XvxM4Dwg== X-Received: by 2002:a05:620a:2225:b0:78d:3b54:eb49 with SMTP id n5-20020a05620a222500b0078d3b54eb49mr2403744qkh.61.1712349158144; Fri, 05 Apr 2024 13:32:38 -0700 (PDT) Received: from ?IPV6:2804:14d:8084:92c5::1002? ([2804:14d:8084:92c5::1002]) by smtp.gmail.com with ESMTPSA id wk16-20020a05620a579000b0078d2ef6dfe2sm923988qkn.125.2024.04.05.13.32.37 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 05 Apr 2024 13:32:37 -0700 (PDT) Message-ID: Date: Fri, 5 Apr 2024 17:32:35 -0300 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Introducing a GDB Code Of Conduct To: Andrew Burgess , gdb-patches@sourceware.org References: <87edg7nsen.fsf@redhat.com> <878r5mzdh7.fsf@redhat.com> From: Guinevere Larsen In-Reply-To: <878r5mzdh7.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=-4.8 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On 12/22/23 08:24, Andrew Burgess wrote: > Andrew Burgess writes: > >> 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. > I've now added the code of conduct to the GDB website. > > However. I still need some volunteers to join the code of conduct > committee. > > The only requirement is that you have been active in the GDB community > for at lest the last year, that you be willing to sign up to the > gdb-conduct mailing list and be willing to engage with any issues that > are reported there. > > I predict / hope that we'll not see anything much reported there, so my > hope is that this will be pretty much a non-task. > > Remember, this is not about *changing* the way the GDB community works, > but about preserving the great environment we already have. > > Membership of the conduct committee will be made public on the GDB > website. > > If you are willing to help out with this, then let me know and I'll get > you added in the New Year. > > Thanks, > Andrew > Has there been any movement regarding the CoC committee? We've had the page up for quite a while and it would be nice to populate it. Especially with the recent XZ backdoor being led by a harassment/bullying campaign, it would be nice to have people with the ability to shut down that type of behavior could be a good hardening step for the project (not that I have seen any interaction at all that would benefit from a step in, but that's what hardening is for). -- Cheers, Guinevere Larsen She/Her/Hers