public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: libc-alpha <libc-alpha@sourceware.org>,
	Paul Eggert <eggert@cs.ucla.edu>,
	Joseph Myers <joseph@codesourcery.com>,
	Jakub Jelinek <jakub@redhat.com>,
	"Ryan S. Arnold" <ryan.arnold@gmail.com>,
	Alexandre Oliva <oliva@gnu.org>, Andreas Schwab <schwab@suse.de>,
	Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>,
	Nick Clifton <nickc@redhat.com>
Subject: Re: Seeking feedback for the adoption of a Code of Conduct for glibc.
Date: Tue, 7 Nov 2023 15:01:21 -0500	[thread overview]
Message-ID: <accd0541-f0cc-cc85-2941-030ce0e95b12@redhat.com> (raw)
In-Reply-To: <208c5f0b-2a90-8c06-a390-4ad010311cb3@redhat.com>

On 11/6/23 17:28, Carlos O'Donell wrote:
> It is critical that we support the growing and continued diversity of our
> community by providing in writing the expectations that we have for our
> conduct.
> 
> With both gcc [1] and binutils [2] having adopted a CoC I have created a
> glibc Code of Conduct based on the one for gcc.
> 
> Over the course of the next month (November) I would like to get feedback
> from the community about adopting a CoC.
> 
> I would like to hear from the other project stewards on this decision.
> 
> Drafts of all the documents are available on the glibc wiki:
> 
> "glibc Code of Conduct"
> https://sourceware.org/glibc/wiki/CoC/Conduct 
> 
> "glibc Code of Conduct Response Guide"
> https://sourceware.org/glibc/wiki/CoC/ResponseGuide
> 
> "glibc Code of Conduct Reporting Guide"
> https://sourceware.org/glibc/wiki/CoC/ReportingGuidelines
> 
> "glibc Code of Conduct Committee"
> https://sourceware.org/glibc/wiki/CoC/Committee
> 
> "glibc Code of Conduct FAQ"
> https://sourceware.org/glibc/wiki/CoC/FAQ
> 
> "glibc CoCC Transparency Reports"
> https://sourceware.org/glibc/wiki/CoC/TransparencyReports (empty boiler plate)
> 
> Thank you for all of your support and for reviewing these documents.
> 

I had a really good question offline about the differences between
the codes of conduct so I updated the FAQ with that question.

Updated the FAQ:
https://sourceware.org/glibc/wiki/CoC/FAQ
~~~
= How is this different from the GCC Code of Conduct? =

The glibc Code of Conduct is a copy of the GCC Code of Conduct with 
references to the GCC Steering Committee replaced with the glibc
stewards and the mailing address changed.

Aside form the straight forward replacements the code of conduct
between glibc and gcc should be identical. 
~~~

Nick,

When you wrote the binutils CoC did you intend to make it match
the gcc CoC? Were there any substantive changes?


-- 
Cheers,
Carlos.


  parent reply	other threads:[~2023-11-07 20:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-06 22:28 Carlos O'Donell
2023-11-07 11:14 ` Florian Weimer
2023-11-07 19:02   ` Carlos O'Donell
2023-11-07 20:01 ` Carlos O'Donell [this message]
2023-11-08 10:05   ` Nick Clifton
2023-11-08 19:03 ` Joseph Myers
2023-11-08 21:18   ` Carlos O'Donell
2023-11-20 21:41 ` Carlos O'Donell

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=accd0541-f0cc-cc85-2941-030ce0e95b12@redhat.com \
    --to=carlos@redhat.com \
    --cc=eggert@cs.ucla.edu \
    --cc=jakub@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=maxim.kuvyrkov@linaro.org \
    --cc=nickc@redhat.com \
    --cc=oliva@gnu.org \
    --cc=ryan.arnold@gmail.com \
    --cc=schwab@suse.de \
    /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).