public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: Introducing a GDB Code Of Conduct
Date: Fri, 22 Dec 2023 11:24:52 +0000	[thread overview]
Message-ID: <878r5mzdh7.fsf@redhat.com> (raw)
In-Reply-To: <87edg7nsen.fsf@redhat.com>

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


  parent reply	other threads:[~2023-12-22 11:24 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
2023-12-22 11:24 ` Andrew Burgess [this message]
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=878r5mzdh7.fsf@redhat.com \
    --to=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).