public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: John Baldwin <jhb@FreeBSD.org>
To: Andrew Burgess <aburgess@redhat.com>, gdb-patches@sourceware.org
Subject: Re: Introducing a GDB Code Of Conduct
Date: Mon, 4 Dec 2023 09:50:31 -0800	[thread overview]
Message-ID: <e21e9941-6c01-42e8-8a33-66ba36cf6428@FreeBSD.org> (raw)
In-Reply-To: <87edg7nsen.fsf@redhat.com>

On 11/30/23 7:59 AM, 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.

I think the proposed CoC is a good one.

-- 
John Baldwin


  parent reply	other threads:[~2023-12-04 17:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-30 15:59 Andrew Burgess
2023-12-03  3:15 ` Kevin Buettner
2023-12-03  3:26 ` Mike Frysinger
2023-12-03  6:40   ` Eli Zaretskii
2023-12-04 15:49   ` Andrew Burgess
2023-12-04  9:27 ` Guinevere Larsen
2023-12-04 17:50 ` John Baldwin [this message]
2023-12-22 11:24 ` Andrew Burgess
2023-12-22 16:57   ` Guinevere Larsen
2023-12-22 19:39   ` Mike Frysinger
2024-04-05 20:32   ` Guinevere Larsen
2024-04-08 10:35     ` Andrew Burgess

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e21e9941-6c01-42e8-8a33-66ba36cf6428@FreeBSD.org \
    --to=jhb@freebsd.org \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).