Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90186 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 85481 invoked from network); 6 Jan 2016 06:12:53 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Jan 2016 06:12:53 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.45 as permitted sender) X-PHP-List-Original-Sender: smalyshev@gmail.com X-Host-Fingerprint: 209.85.192.45 mail-qg0-f45.google.com Received: from [209.85.192.45] ([209.85.192.45:34186] helo=mail-qg0-f45.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 99/5A-21755-360BC865 for ; Wed, 06 Jan 2016 01:12:51 -0500 Received: by mail-qg0-f45.google.com with SMTP id 6so217845292qgy.1 for ; Tue, 05 Jan 2016 22:12:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=kOkBbhsz3wD8TeYqJURKO2pI2/Fwhu/3OfdBXMmJy8g=; b=bSYSncT87aI5Gq5Ny0FDHaFGxuFxGsgNOP8ztQsZ5HZ6A2WkgDGA+lWuiJHoQs48Fi DSUL2sKG8TDiW4vF8rorslmfnW9ZWSrsgfPvIgxNVJn6vIsooOmDYs5rQjDmp2qTf5XK tzjbKJlmutipsuEaEK16SMSqeHQUt+rPuTNHgsg6ynjY3jP8MtPnB3wqeNWINQ49Rmq/ 9H2eCfeJePQbbQBtCAqeHO2Za+QES/un5XzBF2QLMSUBuBIdjK1Et3W1GyAt1k+PyL6M kEgNHmNX0HBkPYvVkM/avaNaLjzVdb9JScuZKqKs6NVpKzyRHzX7QD341FH5VIKanqTI Ud8Q== X-Received: by 10.141.1.2 with SMTP id c2mr137108218qhd.9.1452060768807; Tue, 05 Jan 2016 22:12:48 -0800 (PST) MIME-Version: 1.0 Received: by 10.55.189.2 with HTTP; Tue, 5 Jan 2016 22:12:29 -0800 (PST) In-Reply-To: <568C9ED7.30504@gmail.com> References: <568C9ED7.30504@gmail.com> Date: Tue, 5 Jan 2016 22:12:29 -0800 Message-ID: To: Anthony Ferrara , "internals@lists.php.net" Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] Re: [RFC] [Draft] Adopt Code of Conduct From: smalyshev@gmail.com (Stas Malyshev) 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? :)