linux-kernel - Re: kdbus refactoring?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20151109005335.GA25322@x>
Date:	Sun, 8 Nov 2015 16:53:37 -0800
From:	Josh Triplett <josh@...htriplett.org>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	Richard Weinberger <richard.weinberger@...il.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	David Herrmann <dh.herrmann@...il.com>,
	Djalal Harouni <tixxdz@...ndz.org>,
	Havoc Pennington <havoc.pennington@...il.com>
Subject: Re: kdbus refactoring?

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 <gregkh@...uxfoundation.org> 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/