Likewise. The clearly stated intended consequences are well worth promoting, and any unintended consequences can be addressed with good judgement and ongoing revision. Thank you for your efforts to make sure LLVM remains friendly and inclusive.
Kate Stone k8st...@apple.com <mailto:k8st...@apple.com> Xcode Low Level Tools > On Jun 30, 2016, at 1:18 PM, Jim Grosbach via lldb-dev > <lldb-dev@lists.llvm.org> wrote: > > Thanks, Chandler, for all your work on this. I’m glad to see this moving > forward. > > -Jim > >> On Jun 30, 2016, at 11:55 AM, Chandler Carruth via llvm-dev >> <llvm-...@lists.llvm.org <mailto:llvm-...@lists.llvm.org>> wrote: >> >> Hello folks, >> >> As mentioned some time ago[1], we’ve had a long (looooooong) series of >> discussions about establishing a code-of-conduct for the LLVM project as a >> whole over on the llvm-dev thread and the http://reviews.llvm.org/D13741 >> <http://reviews.llvm.org/D13741> code review. >> >> The discussion has largely died down for some time, and towards the end >> there has been pretty wide support for the draft wording we have now. It >> isn’t perfect, and there are still some important questions around forming >> the advisory committee to handle reporting, but I think the wording is at a >> good point of compromise in a challenging area. >> >> Based on the support, I’m going to land the patch that adds the draft. I’m >> hoping this will immediately provide good advice and guidance, and I’m >> hoping to see motion on setting up a reasonable advisory committee and >> resolving any issues around reporting so we can make this an official part >> of the community. >> >> I sending this as a heads up so folks are aware, not to start a new >> discussion thread. There are existing discussion threads[2] on llvm-dev if >> folks want to join in active discussion or we can start fresh ones, but I >> would encourage people to carefully read the discussion that has already >> taken place to avoid revisiting areas that have already been heavily >> discussed. >> >> Also, many thanks to the folks who provided all their opinions on the >> mailing list threads and in person in long discussions about this topic. >> >> Thanks, >> -Chandler >> >> [1]: Prior announcements: >> http://lists.llvm.org/pipermail/llvm-dev/2015-October/091218.html >> <http://lists.llvm.org/pipermail/llvm-dev/2015-October/091218.html> >> http://lists.llvm.org/pipermail/cfe-dev/2015-October/045460.html >> <http://lists.llvm.org/pipermail/cfe-dev/2015-October/045460.html> >> http://lists.llvm.org/pipermail/lldb-dev/2015-October/008530.html >> <http://lists.llvm.org/pipermail/lldb-dev/2015-October/008530.html> >> http://lists.llvm.org/pipermail/openmp-dev/2015-October/000954.html >> <http://lists.llvm.org/pipermail/openmp-dev/2015-October/000954.html> >> >> [2]: Existing threads: >> http://lists.llvm.org/pipermail/llvm-dev/2015-October/091218.html >> <http://lists.llvm.org/pipermail/llvm-dev/2015-October/091218.html> >> http://lists.llvm.org/pipermail/llvm-dev/2016-May/099120.html >> <http://lists.llvm.org/pipermail/llvm-dev/2016-May/099120.html> >> http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20151019/307070.html >> >> <http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20151019/307070.html>_______________________________________________ >> LLVM Developers mailing list >> llvm-...@lists.llvm.org <mailto:llvm-...@lists.llvm.org> >> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > > _______________________________________________ > lldb-dev mailing list > lldb-dev@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
_______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
