<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Oct 13, 2015, at 2:45 PM, Philip Reames via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta content="text/html; charset=utf-8" http-equiv="Content-Type" class="">
<div text="#000000" bgcolor="#FFFFFF" class="">
+1 to the general idea of a CoC<br class="">
<br class="">
A couple of specific thoughts:<br class="">
<br class="">
1) It would have been nice for this not to appeared out of thin
air. In an ideal world, a previous update would have mentioned
ongoing thought and research in this area.<br class="">
<br class=""></div></div></blockquote><div><br class=""></div><div>Some back story here. I have gotten many requests through email and at the developer meetings about having a Code of Conduct and specifically having one for LLVM Developer Meetings. It has been discussed at many of the LLVM socials as well. I can see in hindsight this might appear to be coming out of nowhere for some, but it really is coming from a need we (the board) heard from the community. </div><div><br class=""></div><div>Thanks,</div><div>Tanya</div><div><br class=""></div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div text="#000000" bgcolor="#FFFFFF" class="">
2) Several folks have mentioned that they'd like to see this less
verbose. I disagree, but I do think that it sometimes comes across
as focusing too much on the details. It might be good to summarize
the general principals, and then list for the more legalistic bits
as notes or footnotes. Make it clear that a list isn't the *point*,
but it does help to clarify.<br class="">
<br class="">
3) I really liked the suggestion down thread of reframing
"reporting" as "asking for moderation". I think it needs to be
clear that there can be consequences, but focusing on resolving the
situation at hand seems like a better starting point for most
discussions.<br class="">
<br class="">
Philip<br class="">
<br class="">
<div class="moz-cite-prefix">On 10/12/2015 06:42 PM, Chandler
Carruth via llvm-dev wrote:<br class="">
</div>
<blockquote cite="mid:CAARZr-Mu-gjyXxNp5NDGc=1D-+cs558xWm9_cdo07fcno_j7+w@mail.gmail.com" type="cite" class="">
<div dir="ltr" class="">
<div class="">Greetings everyone,</div>
<div class=""><br class="">
</div>
<div class="">On behalf of the board of the LLVM Foundation, I’d like to
start the process of introducing a formal code of conduct for
the community.</div>
<div class=""><br class="">
</div>
<div class="">For a long time, various members of the community have been
enforcing basic reasonable and respectful behavior, but to an
outsider this may not be obvious. A public code of conduct
advertises the behavior we expect of community members and
clarifies our stance. Having this is something the board feels
very strongly about and we know many others in the community
do as well. We also think it is important that we establish
this prior to the upcoming developer meeting.</div>
<div class=""><br class="">
</div>
<div class="">When researching this for the board, I looked at a large
number of example codes of conduct from various conferences
and communities, and I kept coming back to the Django
Project’s code of conduct which I think is an extremely good
fit for the LLVM community (several other open source projects
have ended up using it as well). I have adapted it for our
community and our needs, and have a text version below.</div>
<div class=""><br class="">
</div>
<div class="">Some important considerations:</div>
<div class="">- It covers all of the different ways our community has of
interacting, not just a mailing list or the conference.</div>
<div class="">- It makes very clear the kinds of conduct that are
unacceptable, which in research has proven to be very
important for such codes of conduct to be effective in
practice.</div>
<div class="">- It has specific instructions for reporting violations and
gives those who report issues reasonable expectations for what
the response will be. Again, in my research this has been
identified as being a very important aspect to making a code
of conduct effective in practice.</div>
<div class="">- It does not try to be pedantic or have an overly complex
set of rules.</div>
<div class=""><br class="">
</div>
<div class="">We think that this strikes a good balance and would like to
propose the following document for the LLVM project. Once all
the comments are addressed, we plan to add it to the LLVM
documentation and link to it from relevant places. The
“Reporting Guidelines” will be a separate (linked) document
for folks to reference if needed. We will also start the
process of forming and organizing an advisory committee to
handle these kinds of issues.</div>
<div class=""><br class="">
</div>
<div class="">-Chandler, on behalf of the board</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">
<div class="">----</div>
<div class=""># LLVM Community Code of Conduct #</div>
<div class="">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.</div>
<div class=""><br class="">
</div>
<div class="">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.</div>
<div class=""><br class="">
</div>
<div class="">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.</div>
<div class=""><br class="">
</div>
<div class="">If you believe someone is violating the code of conduct,
we ask that you report it by emailing <a moz-do-not-send="true" href="mailto:conduct@llvm.org" class=""></a><a class="moz-txt-link-abbreviated" href="mailto:conduct@llvm.org">conduct@llvm.org</a>.
For more details please see our Reporting Guidelines.</div>
<div class=""><br class="">
</div>
<div class="">- *Be friendly and patient.*</div>
<div class=""><br class="">
</div>
<div class="">- *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, and mental and physical ability.</div>
<div class=""><br class="">
</div>
<div class="">- *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.</div>
<div class=""><br class="">
</div>
<div class="">- *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.</div>
<div class=""><br class="">
</div>
<div class="">- *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:</div>
<div class=""> - Violent threats or language directed against another
person.</div>
<div class=""> - Discriminatory jokes and language.</div>
<div class=""> - Posting sexually explicit or violent material.</div>
<div class=""> - Posting (or threatening to post) other people's
personally identifying information ("doxing").</div>
<div class=""> - Personal insults, especially those using racist or
sexist terms.</div>
<div class=""> - Unwelcome sexual attention.</div>
<div class=""> - Advocating for, or encouraging, any of the above
behavior.</div>
<div class=""> - Repeated harassment of others. In general, if someone
asks you to stop, then stop.</div>
<div class=""><br class="">
</div>
<div class="">- *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 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.</div>
<div class=""><br class="">
</div>
<div class="">## Questions? ##</div>
<div class="">If you have questions, please see feel free to contact
the LLVM Foundation Code of Conduct Advisory Committee by
emailing <a moz-do-not-send="true" href="mailto:conduct@llvm.org" class="">conduct@llvm.org</a>.</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">(This text is based on the Django Project Code of
Conduct, which is in turn based on wording from the Speak
Up! project.)</div>
<div class=""><br class="">
</div>
<div class="">----</div>
</div>
<div class=""># Reporting Guide #</div>
<div class="">
<div class="">If you believe someone is violating the code of conduct
we ask that you report it to the LLVM Foundation by emailing
<a moz-do-not-send="true" href="mailto:conduct@llvm.org" class="">conduct@llvm.org</a>.
*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.<br class="">
</div>
<div class=""><br class="">
</div>
<div class="">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.</div>
<div class=""><br class="">
</div>
<div class="">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 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 <a moz-do-not-send="true" href="mailto:conduct@llvm.org" class="">conduct@llvm.org</a> if
needed.</div>
<div class=""><br class="">
</div>
<div class="">In your report please include:</div>
<div class="">- Your contact info (so we can get in touch with you if
we need to follow up)</div>
<div class="">- Names (real, nicknames, or pseudonyms) of any
individuals involved. If there were other witnesses besides
you, please try to include them as well.</div>
<div class="">- When and where the incident occurred. Please be as
specific as possible.</div>
<div class="">- 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.</div>
<div class="">- Any extra context you believe existed for the incident.</div>
<div class="">- If you believe this incident is ongoing.</div>
<div class="">- Any other information you believe we should have.</div>
<div class=""><br class="">
</div>
<div class="">## What happens after you file a report? ##</div>
<div class="">You will receive an email from the LLVM Foundation Code
of Conduct Advisory Committee acknowledging receipt within
24 hours (and will aim for much quicker than that).</div>
<div class=""><br class="">
</div>
<div class="">The Advisory Committee will immediately meet to review
the incident and determine:</div>
<div class="">- What happened.</div>
<div class="">- Whether this event constitutes a code of conduct
violation.</div>
<div class="">- Who the bad actor was.</div>
<div class="">- Whether this is an ongoing situation, or if there is a
threat to anyone's physical safety.</div>
<div class="">- If this is determined to be an ongoing incident or a
threat to physical safety, the committee's immediate
priority will be to protect everyone involved. This means we
may delay an "official" response until we believe that the
situation has ended and that everyone is physically safe.</div>
<div class=""><br class="">
</div>
<div class="">Once the working group has a complete account of the
events they will make a decision as to how to respond.
Responses may include:</div>
<div class="">- A private reprimand from the working group to the
individual(s) involved.</div>
<div class="">- A public reprimand.</div>
<div class="">- An imposed vacation (i.e. asking someone to "take a
week off" from a mailing list or IRC).</div>
<div class="">- A permanent or temporary ban from some or all LLVM
spaces (mailing lists, IRC, etc.)</div>
<div class="">- A request for a public or private apology.</div>
<div class="">- Nothing (if we determine no violation occurred).</div>
<div class=""><br class="">
</div>
<div class="">If not resolved within one week, we'll respond within one
week to the original reporter with an explanation of why the
situation is not yet resolved.</div>
<div class=""><br class="">
</div>
<div class="">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.</div>
<div class=""><br class="">
</div>
<div class="">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.</div>
<div class=""><br class="">
</div>
<div class="">## Appealing ##</div>
<div class="">Only permanent resolutions (such as bans) may be
appealed. To appeal a decision of the working group, contact
the LLVM Foundation Board at <a moz-do-not-send="true" href="mailto:board@llvm.org" class="">board@llvm.org</a> with your
appeal and the board will review the case.</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">(This text is based on the Django Project Code of
Conduct, which is in turn based on wording from the Speak
Up! project.)</div>
</div>
</div>
<br class="">
<fieldset class="mimeAttachmentHeader"></fieldset>
<br class="">
<pre wrap="" class="">_______________________________________________
LLVM Developers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a>
<a class="moz-txt-link-freetext" href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a>
</pre>
</blockquote>
<br class="">
</div>
_______________________________________________<br class="">LLVM Developers mailing list<br class=""><a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a><br class="">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev<br class=""></div></blockquote></div><br class=""></body></html>