public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: Nick Clifton <nickc@redhat.com>, binutils@sourceware.org
Cc: ganandan@redhat.com, markobri@redhat.com
Subject: Re: Binutils Code of Conduct
Date: Thu, 28 Sep 2023 16:27:20 -0400	[thread overview]
Message-ID: <0bafa825-2033-2b17-de12-4e99bd334e61@redhat.com> (raw)
In-Reply-To: <877cockjm6.fsf@redhat.com>

On 9/26/23 12:02, Nick Clifton via Binutils wrote:
>   We are going to have a Code of Conduct for the GNU Binutils.
> 
>   Rather than reinvent the wheel however, I have decided to take GCC's
>   code of conduct and tweak it for us.  The revised text is attached
>   below.
> 
>   If you have any strong objections to this please let me know as soon
>   as possible, as I plan to put the text up on the binutils web page and
>   wiki by the end of the week.
> 
>   If you are interested in volunteering to be on the Code Of Conduct
>   committee, please let me know directly, or email
>   binutils-conduct@sourceware.org.  In the meantime my boss Mark O'Brian
>   has volunteered to be on the committee so we will be starting off with
>   at least one person.

Thanks for working on this Nick.

I've been thinking of exactly the same thing for glibc:
https://sourceware.org/glibc/wiki/conduct

Should this go on the binutils wiki?

I'd be happy to volunteer to be on the CoCC for binutils.

If we adopt something like this for all of the GNU Toolchain projects we can probably
work together to process and respond to CoCC issues across the communities.

There is quite a bit we can learn from downstream distributions too like Gentoo,
Debian, Fedora etc.

-- 
Cheers,
Carlos.


  parent reply	other threads:[~2023-09-28 20:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-26 16:02 Nick Clifton
2023-09-28 19:27 ` Alexandre Oliva
2023-09-28 20:42   ` Carlos O'Donell
2023-09-28 23:12     ` Alexandre Oliva
2023-09-28 23:35   ` Mark Wielaard
2023-09-29 13:39   ` Nick Clifton
2023-09-29 15:03     ` Matt Rice
2023-09-29 17:30     ` Alexandre Oliva
2023-09-28 20:27 ` Carlos O'Donell [this message]
2023-10-03  9:54   ` Richard Earnshaw (lists)
2023-10-03 10:36     ` Nick Clifton
2023-10-03 17:52     ` Tom Tromey
2023-09-29 12:52 ` Gomathi Anandan

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=0bafa825-2033-2b17-de12-4e99bd334e61@redhat.com \
    --to=carlos@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=ganandan@redhat.com \
    --cc=markobri@redhat.com \
    --cc=nickc@redhat.com \
    /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).