[llvm-dev] Resuming the discussion of establishing an LLVM code of conduct
Bill Kelly via llvm-dev
llvm-dev at lists.llvm.org
Thu May 5 23:06:30 PDT 2016
Chris Lattner via llvm-dev wrote:
> What is the value in having a bespoke LLVM code of conduct?
> The Swift community has been using the standard "Contributor Covenant”
> to good effect:
> Why do we need to “innovate" here?
Was it not the very behavior of the *author* of said "Contributor Covenant"
that has provided a definitive example of wielding a code of conduct as
a weapon to police wrongthink? Speech that occurred, one might add, in a
discussion on social media completely unrelated to the programming project?
[ https://github.com/opal/opal/issues/941 ]
Would not such an incident give one pause?
Would not one be inclined to put on the brakes, having seen the author's
How in the fiduciary melonfarming troutdangle does one not, having seen
those cards laid bare, say: "Whoa. Thanks for illustrating how you intend
this to function. We'll shop somewhere else."
Personally I'm pleased the Ruby maintainers did decide to innovate, and
that they managed to arrive at something arguably more elegant, and
certainly more concise:
More information about the llvm-dev