Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752125AbbKIAxs (ORCPT ); Sun, 8 Nov 2015 19:53:48 -0500 Received: from relay4-d.mail.gandi.net ([217.70.183.196]:47566 "EHLO relay4-d.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751556AbbKIAxp (ORCPT ); Sun, 8 Nov 2015 19:53:45 -0500 X-Originating-IP: 50.39.163.18 Date: Sun, 8 Nov 2015 16:53:37 -0800 From: Josh Triplett To: Greg KH Cc: Richard Weinberger , Linus Torvalds , "linux-kernel@vger.kernel.org" , David Herrmann , Djalal Harouni , Havoc Pennington Subject: Re: kdbus refactoring? Message-ID: <20151109005335.GA25322@x> References: <20151108213526.GB942@kroah.com> <20151108233018.GA1852@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151108233018.GA1852@kroah.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2821 Lines: 60 On Sun, Nov 08, 2015 at 03:30:18PM -0800, Greg KH wrote: > On Sun, Nov 08, 2015 at 10:39:43PM +0100, Richard Weinberger wrote: > > On Sun, Nov 8, 2015 at 10:35 PM, Greg KH wrote: > > > On Sun, Nov 08, 2015 at 10:06:31PM +0100, Richard Weinberger wrote: > > >> Hi all, > > >> > > >> after reading on the removal of kdbus from Rawhide[1] I've searched > > >> the mailinglist archives for more details but didn't find anything. > > >> So, what are your plans? > > >> > > >> [1] https://lists.fedoraproject.org/pipermail/kernel/2015-October/006011.html > > > > > > As that link said, based on the result of the code being in Rawhide, it > > > is now being reworked / redesigned. The result will be posted for > > > review "when it's ready". > > > > If you rework/redesign something you have to know what you want to change. > > That's why I was asking for the plan... > > Since when do people post "plans" or "design documents" on lkml without > real code? Quoting Documentation/development-process/1.Intro: > Section 3 covers early-stage project planning, with an emphasis on > involving the development community as soon as possible. Quoting Documentation/development-process/3.Early-stage: > When planning a kernel development project, it makes great sense to hold > discussions with the community before launching into implementation. [...] > - It's entirely possible that other developers have thought about the > problem; they may have ideas for a better solution, and may be willing > to help in the creation of that solution. > > 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. [...] > If possible, posting your plans during the early stages can only be > helpful. Describe the problem being solved and any plans that have been > made on how the implementation will be done. Any information you can > provide can help the development community provide useful input on the > project. And I've seen you specifically recommend having such conversations early and often. That same document also warns about the discouraging possibility of receiving "little or no reaction" for a variety of reasons, but somehow I don't think kdbus will encounter that problem. :) - Josh Triplett -- 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/