Re: Introducing a GDB Code Of Conduct

[Guinevere Larsen <blarsen@redhat.com>]

On 12/22/23 08:24, Andrew Burgess wrote:
> Andrew Burgess <aburgess@redhat.com> 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