Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756773Ab3GPCn6 (ORCPT ); Mon, 15 Jul 2013 22:43:58 -0400 Received: from void.printf.net ([89.145.121.20]:58895 "EHLO void.printf.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753349Ab3GPCn4 (ORCPT ); Mon, 15 Jul 2013 22:43:56 -0400 From: Chris Ball To: Darren Hart Cc: Sarah Sharp , Steven Rostedt , Linus Torvalds , Ingo Molnar , Guenter Roeck , Greg Kroah-Hartman , Dave Jones , Linux Kernel Mailing List , Andrew Morton , stable , ksummit-2013-discuss@lists.linuxfoundation.org, Willy Tarreau Subject: Re: [ATTEND] How to act on LKML References: <20130715174659.GC15531@xanatos> <20130715180403.GD15531@xanatos> <20130715184642.GE15531@xanatos> <20130715195316.GF15531@xanatos> <20130715204135.GH15531@xanatos> <1373926109.17876.221.camel@gandalf.local.home> <20130715223615.GI15531@xanatos> <1373932170.28142.24.camel@envy.home> Date: Tue, 16 Jul 2013 03:43:37 +0100 In-Reply-To: <1373932170.28142.24.camel@envy.home> (Darren Hart's message of "Mon, 15 Jul 2013 16:49:30 -0700") Message-ID: <864nbv9qcm.fsf@void.printf.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2338 Lines: 51 Hi, On Tue, Jul 16 2013, Darren Hart wrote: > On Mon, 2013-07-15 at 15:36 -0700, Sarah Sharp wrote: >> The people who want to work together in a civil manner should get >> together and create a "Kernel maintainer's code of conduct" that >> outlines what they expect from fellow kernel developers. The people who >> want to continue acting "unprofessionally" should document what >> behaviors set off their cursing streaks, so that others can avoid that >> behavior. Somewhere in the middle is the community behavior all >> developers can thrive in. >> >> Some people won't agree with everything in that document. The point is, >> they don't have to agree. They can read the document, figure out what >> the community expects, and figure out whether they can modify their >> behavior to match. If they are unwilling to change, they simply don't >> have to work with the developers who have signed it. >> >> Perhaps a trusted third party could take a stab at a first draft of this >> document? Greg KH? Steve Rostedt? Darren Hart? > > [..] > I do believe that someone from the intended audience of a document > should be the one to write the first draft (or they should be among the > reviewers if the authority drafts the document). For instance, I > believe I would be able to document how to work with -tip or -stable as > an individual contributor. I would not be a good candidate for writing > the "how to be a lieutenant to Linus" because I am neither Linus nor > one of his lieutenants. Here's a simple statement that I hope many kernel developers would sign up for -- I'd be happy to make it for the subsystem I maintain: * If there's something wrong with your patch, I will critique the code respectfully, without personal attacks or public humiliation. I'd like other developers to treat me this way too, but perhaps a good way to get started is to first come up with a statement of how we'd like to treat others, and then start collecting signatories to it. Does that sound like a good idea? Thanks, - Chris. -- Chris Ball -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/