<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="">On May 5, 2016, at 1:21 AM, Chandler Carruth via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a>> wrote:<br class=""><div><blockquote type="cite" class=""><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Greetings all,<div class=""><br class=""></div><div class="">This has come up a few times, and I would like to resume the effort to establish an LLVM code of conduct.</div></div></div></blockquote><div><br class=""></div><div>Awesome, long overdue. Thank you for pushing this.</div><div><br class=""></div><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="">First and foremost, many thanks to Philip Reames who sat down with me several months ago and worked through a number of suggestions that I've tried to incorporate into an updated patch with the draft text: <a href="http://reviews.llvm.org/D13741" class="">http://reviews.llvm.org/D13741</a></div></div></div></blockquote><br class=""></div><div>What is the value in having a bespoke LLVM code of conduct?</div><div><br class=""></div><div>The Swift community has been using the standard "Contributor Covenant” to good effect:</div><div><a href="https://swift.org/community/#code-of-conduct" class="">https://swift.org/community/#code-of-conduct</a></div><div><a href="http://contributor-covenant.org" class="">http://contributor-covenant.org</a></div><div><br class=""></div><div>Why do we need to “innovate" here?</div><div><br class=""></div><div>-Chris</div><div><br class=""></div><br class=""></body></html>