public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Gomathi Anandan <ganandan@redhat.com>
To: Nick Clifton <nickc@redhat.com>
Cc: binutils@sourceware.org, markobri@redhat.com
Subject: Re: Binutils Code of Conduct
Date: Fri, 29 Sep 2023 08:52:58 -0400	[thread overview]
Message-ID: <CAJt7tnc+-fvUCei5xLht5+53M4bZReaJoete0tQ-7082_bw5QA@mail.gmail.com> (raw)
In-Reply-To: <877cockjm6.fsf@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 6653 bytes --]

Nick,

Thank you for working on this. It IS a great first step in making the
binutils community more inclusive.

Gomathi



On Tue, Sep 26, 2023 at 12:03 PM Nick Clifton <nickc@redhat.com> wrote:

> Hi Guys,
>
>   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.
>
> Cheers
>   Nick
>
> -------------------------------------------------------------------------
>
>                 GNU Binutils Code of Conduct
>
> Like the free software community as a whole, the GNU Binutils community
> is made up of a mixture of professionals and volunteers from all over
> the world, working on every aspect of the project - including
> mentorship, teaching, and connecting people.
>
> Diversity is a huge strength, but it can also lead to communication
> issues and unhappiness.  To that end, we have a few ground rules that we
> ask people to adhere to.  This code applies equally to leaders,
> maintainers, and those seeking help and guidance.
>
> This isn't an exhaustive list of things that you can or can't do.
> Rather, take it in the spirit in which it's intended - a guide to make
> it easier to enrich all of us, the project, and the broader communities
> in which we participate.
>
> This code of conduct applies to all spaces managed by the GNU Binutils
> project.  This includes the mailing lists, the issue tracker, events,
> and any other forums created by the project team which the community
> uses for communication.  In addition, violations of this code outside
> these spaces (though still in the context of the GNU Binutils) may
> affect a person's ability to participate within them.
>
> The rules are:
>
>   * Be friendly and patient.
>
>   * Be welcoming.
>
>     We strive to be a community that welcomes and supports people of all
>     backgrounds and identities.  This includes, but is not limited to,
>     members of any race, ethnicity, culture, national origin, color,
>     immigration status, social and economic class, educational level,
>     sex, sexual orientation, gender identity and expression, age, size,
>     family status, political belief, religion, and mental or physical
>     ability.
>
>   * Be considerate.
>
>     Your work will be used by other people, and you in turn will depend
>     on the work of others.  Any decision you take will affect users and
>     colleagues, and you should take those consequences into account when
>     making decisions.  Remember that we're a world-wide community, so you
>     might not be communicating in someone else's primary language.
>
>   * Be respectful.
>
>     Not all of us will agree all the time, but disagreement is no excuse
>     for poor behaviour and poor manners.  We might all experience some
>     frustration now and then, but we cannot allow that frustration to turn
>     into a personal attack.  It's important to remember that a community
>     where people feel uncomfortable or threatened is not a productive
>     one.  Members of the community should be respectful when dealing with
>     other members as well as with people outside the community.
>
>   * Be kind to others and be careful in the words that you choose.
>
>     Do not insult or put down other participants.  Harassment and other
>     exclusionary behaviour aren't acceptable.  This includes, but is not
>     limited to:
>
>       - Violent threats or language directed against another person.
>       - Discriminatory jokes and language.
>       - Posting sexually explicit or violent material.
>       - Posting (or threatening to post) other people's personally
>         identifying information ("doxing").
>       - Personal insults, especially those using racist or sexist terms.
>       - Unwelcome sexual attention.
>       - Advocating for, or encouraging, any of the above behaviour.
>       - Repeated harassment of others.  In general, if someone asks you
>         to stop, then stop.
>
>     When we disagree, try to understand why.  Disagreements, both social
>     and technical, happen all the time and the GNU Binutils community is
>     no exception.  It is important that we resolve disagreements and
>     differing views constructively.  One of the strengths of the free
>     software movement is its varied community, with people from a wide
>     range of backgrounds.  Different people have different perspectives
>     on issues.  Being unable to understand why someone holds a viewpoint
>     doesn't mean that they're wrong.  Don't forget that it is human to
>     err and blaming each other doesn't get us anywhere.  Instead, focus
>     on helping to resolve issues and learning from mistakes.
>
>     See the GNU Kind Communications Guidelines for more guidance on
>     constructive interactions:
>       https://www.gnu.org/philosophy/kind-communication.en.html
>
>
> If you believe someone is violating the code of conduct, we ask that you
> report it by emailing binutils-conduct@sourceware.org  For more details
> please see our Reporting Guidelines.
>
>   Code of Conduct Committee
>
> The Code of Conduct Committee, and the formal reporting and response
> procedures, are not yet fully established.  For the time being,
> emailing binutils-conduct@sourceware.org will go to some of the GNU
> Binutils maintainers.  If you are interested in serving on the CoC
> committee, or would like to suggest someone who you think would be a
> good candidate, please email binutils-conduct@sourceware.org .
>
>   Questions?
>
> If you have questions, please see the FAQ. If that doesn't answer your
> questions, feel free to contact us.
>
>   Creative Commons License
>
> This work is licensed under a Creative Commons Attribution-ShareAlike
> 4.0 International License.
>
> Text derived from the Django project Code of Conduct, used under the
> Creative Commons Attribution license and the GCC Code of Conduct, also
> under the same license.
>
>

      parent reply	other threads:[~2023-09-29 12:53 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
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 [this message]

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=CAJt7tnc+-fvUCei5xLht5+53M4bZReaJoete0tQ-7082_bw5QA@mail.gmail.com \
    --to=ganandan@redhat.com \
    --cc=binutils@sourceware.org \
    --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).