From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id D34F04FF8 for ; Fri, 5 Oct 2018 13:09:13 +0000 (UTC) Received: from perceval.ideasonboard.com (perceval.ideasonboard.com [213.167.242.64]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 4E6797C3 for ; Fri, 5 Oct 2018 13:09:13 +0000 (UTC) From: Laurent Pinchart To: Jani Nikula Date: Fri, 05 Oct 2018 16:09:28 +0300 Message-ID: <2785765.n23bRQE9Qy@avalon> In-Reply-To: <875zygpn10.fsf@intel.com> References: <2795844.PlkHHhbf7z@avalon> <875zygpn10.fsf@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Cc: ksummit-discuss@lists.linuxfoundation.org Subject: Re: [Ksummit-discuss] New CoC and Brendan Eich List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi Jani, On Friday, 5 October 2018 15:59:23 EEST Jani Nikula wrote: > On Fri, 05 Oct 2018, Laurent Pinchart wrote: > > There are valid reasons for software to fork, I don't see why there > > could be valid reasons for codes of conduct to fork. > > Perhaps you're missing a "not" in there? Yes, sorry, proof-reading your own e-mails work equally as well as reviewing your own patches :-) > Some of the valid reasons to *not* fork codes of conduct are similar to > why you shouldn't roll your own licenses. First, people don't want to > keep reading and interpreting different texts for different projects, > wondering what this means for them. Just read the familiar label and you > know what's in the box. Second, as a community you can share the > experiences and best practices with other projects using the same text. No disagreement there, but that's not limited to codes of conduct or licenses. Forking generates pain in general, but sometimes still makes sense when carefully done. > I'm not saying we should stick to Contributor Covenant at all cost, I'm > saying pick a suitable tried and tested code of conduct, and stick with > it. That would have my preference as well, provided such a code of conduct exists (and we would add a FAQ to clarify grey areas regardless of which standard code of conduct we would select). -- Regards, Laurent Pinchart