Hi! > > own custom one, there are two reasons for this. First, it's a standard > > that's been adopted by a number of significant scale projects. Second, > > I completely disagree that Contributor Covenant's text is any kind of > "standard". I've seen a number of CoCs, and it's not the worst (though > their homepage is... meh) but also not the best, and certainly not only.
Here are couple more: Django: https://www.djangoproject.com/conduct/ FreeBSD: https://www.freebsd.org/internal/code-of-conduct.html I think all those have several common threads: - more space spent on good conduct than bad conduct - advice on how to resolve conflicts without escalation - clear guidelines for reporting problems - specific one for the project, not a prefabricated copy Comparing this one to the Covenant one, I clearly think any of those examples is superior. Is reflects specific project, is helpful, is positive, and looks like is is written by actual people, not copied from somewhere because we need to have something. I think that if we think having CoC is important, then we should have one that is actually helpful and positive, and not a cookie-cutter one. And if it's not important enough for us to spend some time on formulating it, then maybe we don't need it that much? :) -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
