Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752020AbbKIIsV (ORCPT ); Mon, 9 Nov 2015 03:48:21 -0500 Received: from bombadil.infradead.org ([198.137.202.9]:50347 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751349AbbKIIsU (ORCPT ); Mon, 9 Nov 2015 03:48:20 -0500 Date: Mon, 9 Nov 2015 09:48:13 +0100 From: Peter Zijlstra To: David Herrmann Cc: Josh Triplett , Greg KH , Richard Weinberger , Linus Torvalds , "linux-kernel@vger.kernel.org" , Djalal Harouni , Havoc Pennington Subject: Re: kdbus refactoring? Message-ID: <20151109084813.GD7520@twins.programming.kicks-ass.net> References: <20151108213526.GB942@kroah.com> <20151108233018.GA1852@kroah.com> <20151109005335.GA25322@x> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1631 Lines: 35 On Mon, Nov 09, 2015 at 09:34:37AM +0100, David Herrmann wrote: > Hi > > On Mon, Nov 9, 2015 at 1:53 AM, Josh Triplett wrote: > > Quoting Documentation/development-process/1.Intro: > [...] > >> Years of experience with the kernel development community have taught a > >> clear lesson: kernel code which is designed and developed behind closed > >> doors invariably has problems which are only revealed when the code is > >> released into the community. Sometimes these problems are severe, > >> requiring months or years of effort before the code can be brought up to > >> the kernel community's standards. > [...] > > And I've seen you specifically recommend having such conversations early > > and often. > > I think comparing kdbus to "behind closed doors" development models is > unfair. We chose to center our development around DBus, not the > kernel. And yet it will be the kernel people you ask to take your code. You don't see something funny with that? > Anybody who is interested in kdbus discussions could have > easily joined the DBus and systemd communication channels (and *many* > people did). I see little reason in cross-posting everything to LKML, > especially given that our communication is rarely mail-based. So you want to develop kernel code, but can't be arsed to do it the kernel way? Gheez, no wonder this all is going so well.. -- 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/