[PATCH] D13741: Introduce a *draft* of a code of conduct for the LLVM community and theassociated reporting guide.

[Justin Bogner via llvm-commits]

Chandler Carruth <chandlerc at gmail.com> writes:
> chandlerc created this revision.
> chandlerc added reviewers: reames, grosbach, bogner, jmolloy.
> chandlerc added a subscriber: llvm-commits.
>
> I want to emphasize that at this point these are just drafts!
>
> I also want to very strongly discourage any substantive discussion here.
> Feel free to provide normal RST and English review on the details, but
> all discussion of th econtent, substance, and even the concept of a code
> of conduct should take place on llvm-dev. I will be starting a fresh
> thread there with an in-line copy of this updated version very soon.

Some grammar and wording notes below. For the record, this LGTM.

> http://reviews.llvm.org/D13741
>
> Files:
>   docs/CodeOfConduct.rst
>   docs/ReportingGuide.rst
>   docs/index.rst
>
> Index: docs/index.rst
> ===================================================================
> --- docs/index.rst
> +++ docs/index.rst
> @@ -86,6 +86,8 @@
>     GetElementPtr
>     Frontend/PerformanceTips
>     MCJITDesignAndImplementation
> +   CodeOfConduct
> +   ReportingGuide
>  
>  :doc:`GettingStarted`
>     Discusses how to get up and running quickly with the LLVM infrastructure.
> Index: docs/ReportingGuide.rst
> ===================================================================
> --- /dev/null
> +++ docs/ReportingGuide.rst
> @@ -0,0 +1,97 @@
> +===============
> +Reporting Guide
> +===============
> +
> +.. note::
> +
> +   This document is currently a **DRAFT** document while it is being discussed
> +   by the community.
> +
> +If you believe someone is violating the :doc:`code of conduct <CodeOfConduct>`
> +we ask that you report it to the LLVM Foundation Code of Conduct Advisory
> +Committee by emailing conduct at llvm.org. **All reports will be kept
> +confidential.** In some cases we may determine that a public statement will
> +need to be made. If that's the case, the identities of all victims and
> +reporters will remain confidential unless those individuals instruct us
> +otherwise.
> +
> +If you believe anyone is in physical danger, please notify appropriate law
> +enforcement first. If you are unsure what law enforcement agency is
> +appropriate, please include this in your report and we will attempt to notify
> +them.
> +
> +If the violation occurs at an event such as a Developer Meeting, you can also
> +reach out to any of the event organizers or staff to report it. If you cannot
> +find one of the organizers, the hotel staff can locate one for you. We will
                                   ^~~~~
"event staff"

> +also post detailed contact information for specific events as part of each
> +events’ information. Event organizers and staff will be prepared to handle the
> +incident and able to help. Your report will still be kept confidential exactly
> +as above, but also feel free to (anonymously if needed) email conduct at llvm.org
> +if needed.
> +
> +In your report please include:
> +
> +* Your contact info (so we can get in touch with you if we need to follow up)
> +* Names (real, nicknames, or pseudonyms) of any individuals involved. If there
> +  were other witnesses besides you, please try to include them as well.
> +* When and where the incident occurred. Please be as specific as possible.
> +* Your account of what occurred. If there is a publicly available record (e.g.
> +  a mailing list archive or a public IRC logger) please include a link.
> +* Any extra context you believe existed for the incident.
> +* If you believe this incident is ongoing.

"Whether or not you believe this incident is ongoing"

> +* Any other information you believe we should have. What happens after you file
> +  a report? = You will receive an email from the advisory committee
> +  acknowledging receipt within 24 hours (and we will aim to respond much
> +  quicker than that).
> +
> +The advisory committee will immediately meet to review the incident and
> +determine:
> +
> +* What happened.
> +* Whether this event constitutes a code of conduct violation.
> +* Who the bad actor was.
> +* Whether this is an ongoing situation, or if there is a threat to anyone's
> +  physical safety.
> +
> +If this is determined to be an ongoing incident or a threat to physical safety,
> +the working groups' immediate priority will be to protect everyone involved.

"working group's"

> +This means we may delay an "official" response until we believe that the
> +situation has ended and that everyone is physically safe.
> +
> +Once the advisory committee has a complete account of the events they will make
> +a decision as to how to respond. Responses may include:
> +
> +* A private reprimand from the working group to the individual(s) involved.
> +* A public reprimand.
> +* An imposed vacation (i.e. asking someone to "take a week off" from a mailing
> +  list or IRC).
> +* A permanent or temporary ban from some or all LLVM spaces (mailing lists,
> +  IRC, etc.)
> +* A request for a public or private apology.
> +* Nothing (if we determine no violation occurred).
> +
> +If the situation is not resolved within one week, we'll respond within one week
> +to the original reporter with an update and explanation.
> +
> +Once we've determined our final action, we'll contact the original reporter to
> +let them know what action (if any) we'll be taking. We'll take into account
> +feedback from the reporter on the appropriateness of our response, but we don't
> +guarantee we'll act on it.

Perhaps "can't guarantee we'll act on it" is better?

> +
> +Finally, the advisory committee will make a report on the situation to the LLVM
> +Foundation board. The board may choose to make a public statement about the
> +incident.
> +
> +Appealing
> +=========
> +
> +Only permanent resolutions (such as bans) may be appealed. To appeal a decision
> +of the working group, contact the LLVM Foundation board at board at llvm.org with
> +your appeal and the board will review the case.
> +
> +
> +(This text is based on the `Django Project`_ Code of Conduct, which is in turn
> +based on wording from the `Speak Up! project`_.)
> +
> +.. _Django Project: https://www.djangoproject.com/conduct/
> +.. _Speak Up! project: http://speakup.io/coc.html
>
> Index: docs/CodeOfConduct.rst
> ===================================================================
> --- /dev/null
> +++ docs/CodeOfConduct.rst
> @@ -0,0 +1,92 @@
> +==============================
> +LLVM Community Code of Conduct
> +==============================
> +
> +.. note::
> +
> +   This document is currently a **DRAFT** document while it is being discussed
> +   by the community.
> +
> +We want to ensure that the LLVM community, while large and diverse, remains
> +welcoming and respectful to all participants. To that end, we have a few ground
> +rules that we ask people to adhere to.
> +
> +This isn’t an exhaustive list of things that you can’t do. Rather, take it in
> +the spirit in which it’s intended - a guide to make it easier to communicate
> +and participate in the community.
> +
> +This code of conduct applies to all spaces managed by the LLVM project or The
> +LLVM Foundation. This includes IRC channels, mailing lists, bug trackers, LLVM
> +events such as the developer meetings and socials, and any other forums created
> +by the project that the community uses for communication. It applies to all of
> +your communication and conduct in these spaces, including emails, chats, things
> +you say, slides, videos, posters, signs, or even t-shirts you display in these
> +spaces. In addition, violations of this code outside these spaces may affect
> +a person's ability to participate within them.
> +
> +If you believe someone is violating the code of conduct, we ask that you report
> +it by emailing conduct at llvm.org. For more details please see our
> +:doc:`Reporting Guide <ReportingGuide>`.
> +
> +* **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, colour,
> +  immigration status, social and economic class, educational level, sex, sexual
> +  orientation, gender identity and expression, age, size, family status,
> +  political belief, religion or lack thereof, and mental and 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 behavior 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 LLVM
> +  community should be respectful when dealing with other members as well as
> +  with people outside the LLVM community.
> +
> +* **Be careful in the words that you choose.** We are a community of
> +  professionals, and we conduct ourselves professionally. Be kind to others. Do
> +  not insult or put down other participants. Harassment and other exclusionary
> +  behavior 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 behavior.
> +  * 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 LLVM is no exception. It is important that
> +  we resolve disagreements and differing views constructively. Remember that
> +  we’re different. The strength of LLVM comes from its varied community, people

"we're all different"?

> +  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.
> +
> +Questions?
> +==========
> +
> +If you have questions, please feel free to contact the LLVM Foundation Code of
> +Conduct Advisory Committee by emailing conduct at llvm.org.
> +
> +
> +(This text is based on the `Django Project`_ Code of Conduct, which is in turn
> +based on wording from the `Speak Up! project`_.)
> +
> +.. _Django Project: https://www.djangoproject.com/conduct/
> +.. _Speak Up! project: http://speakup.io/coc.html
> +