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 2A0393858D33 for ; Fri, 22 Dec 2023 16:57:40 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 2A0393858D33 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 2A0393858D33 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=1703264262; cv=none; b=dOuBgNaYuBRDJKygfcJO7VNh+oY4+eE8HCXyjq7umB7IHwuOgHk8Ew6OYHhjxmRKmlMv3TvRAKLEwPSSZSKcmCHo4HrQvkME9eJ7X5EKk1Vv9yA41183CnXwbLW5E4+kWd+YMNS66wCt7H4OYyZMi4ML3QxfnvOvfsRekzk5alA= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1703264262; c=relaxed/simple; bh=kJRoRs5q+2oRNvZW9vHNCuFs1vPKZ8mGRsGDn0KtInw=; h=DKIM-Signature:Message-ID:Date:MIME-Version:Subject:To:From; b=A4ifsHeyAAUZdc243PerDkNFZmYw2Li50r/JUqS1T67rhcXnQ13SKttWZ2hkZuzNmBX6+YiqeAGR1Ayy5mADdjvONRJTJxnZJMOGsKqYQWjDdeMGjoC2mmadLypsJ6Vr7kBmK+VBhwW9mn16zW2q/SWqUhgg5BkdKCs1+SP1KQ4= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1703264259; 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=EBpeyV/6WTc9Cw+gkKEkEb0gZnY1OA87MBZYfJX+aUo=; b=LnUnTsW53emJZzjTccm8p3IaFcdLcs4SdviSkowpA7KTfwBGU0g7ZthKiZZwZrsJY5S+1Y gWFKuwaDxZ/Eaa8mlsVcKJeHghDi2X0L30zHi1LPRuA/DTqwWcb27NtqcQg0D8j52o4RYh j65k08TsoZ9gGYr+VuzUXN+vo+YjBKU= 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-53-RZc7GQunMwCA94NWV9-lCw-1; Fri, 22 Dec 2023 11:57:37 -0500 X-MC-Unique: RZc7GQunMwCA94NWV9-lCw-1 Received: by mail-lj1-f200.google.com with SMTP id 38308e7fff4ca-2cc678dc506so16487021fa.1 for ; Fri, 22 Dec 2023 08:57:37 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1703264255; x=1703869055; 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=EBpeyV/6WTc9Cw+gkKEkEb0gZnY1OA87MBZYfJX+aUo=; b=XB0FQZKVwBTfhH1a7b6WhQAg7P6PcghqELmCgqCtDGOqy1/hxIKvT1BEybbRVsCGGb 1c7uJgq2yqGEq/C/LKhwGufKzrgDkW8hjR/nbqsyrBVd8syVIcmwGlLFWl34MGVvCW0t 7j612TXuuYFiprtbyvTvlDx1qaYw1nKYFmh76RAIpZmYDHtBaKLJYvkgVSfSG1ISu+np j4/m2bctTVQ4RdFi73fwc4YBAq2qtZHvRYC6SBoSAS8CoqIX8VOEL34iRae5qUPd60Kb pk3EbYWzh2dlS2ZO4w3f5skH92URHhEJEDCzJBHtPDOA6OIwWtrXEtXw1n3eCbhsMT0h R4kw== X-Gm-Message-State: AOJu0YznTal+Zd6BUpO0l1YHYUoWP2PZQwaBbU1ddmrwRiytjhKrSs+a JbljJlQhkheLsTb8CPvQT/mDjU9vdho8eKWjnw86A7xtpGaOAGQTmFVKL2eP1kzwuyfJD+wpRB2 yunsxJvhHtz3NtaWljLHuMTcUvRZFIGdP5JbiRA== X-Received: by 2002:a05:6512:505:b0:50e:4f9d:d4ab with SMTP id o5-20020a056512050500b0050e4f9dd4abmr990635lfb.60.1703264255403; Fri, 22 Dec 2023 08:57:35 -0800 (PST) X-Google-Smtp-Source: AGHT+IGfL0fCs/8BeSCyxPFPRp5iRqAFiDDZ1R1AiR97zuHKoOhuGzNbWZKFOzaRgpxApPy9eU4AQw== X-Received: by 2002:a05:6512:505:b0:50e:4f9d:d4ab with SMTP id o5-20020a056512050500b0050e4f9dd4abmr990622lfb.60.1703264255045; Fri, 22 Dec 2023 08:57:35 -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 ge21-20020a170907909500b00a18c2737203sm2207730ejb.109.2023.12.22.08.57.34 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 22 Dec 2023 08:57:34 -0800 (PST) Message-ID: Date: Fri, 22 Dec 2023 17:57:34 +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> <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=-6.0 required=5.0 tests=BAYES_00,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,SPF_HELO_NONE,SPF_NONE,TXREP,T_SCC_BODY_TEXT_LINE 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 22/12/2023 12: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 > I'm interested in joining the committee. I'm leaving for the holidays now, but I'll be happy to do whatever is needed in the new year -- Cheers, Guinevere Larsen She/Her/Hers