From: Richard Weinberger <richard@nod.at>
To: David Herrmann <dh.herrmann@gmail.com>,
Josh Triplett <josh@joshtriplett.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Richard Weinberger <richard.weinberger@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Djalal Harouni <tixxdz@opendz.org>,
Havoc Pennington <havoc.pennington@gmail.com>
Subject: Re: kdbus refactoring?
Date: Mon, 9 Nov 2015 09:37:19 +0100 [thread overview]
Message-ID: <56405B3F.9060508@nod.at> (raw)
In-Reply-To: <CANq1E4QmdCWMA8qJ-6ROsyfGxgLocprsurUnfwuyYBf_YoR+nw@mail.gmail.com>
Am 09.11.2015 um 09:34 schrieb David Herrmann:
> Hi
>
> On Mon, Nov 9, 2015 at 1:53 AM, Josh Triplett <josh@joshtriplett.org> 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. 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.
I agree, "behind the doors" is not true. But a mailinglist with achieves
would be nice.
IIRC last time I've asked you said that all discussion happened privately
or on IRC. Which is okay but not that transparent.
Thanks,
//richard
next prev parent reply other threads:[~2015-11-09 8:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-08 21:06 kdbus refactoring? Richard Weinberger
2015-11-08 21:35 ` Greg KH
2015-11-08 21:39 ` Richard Weinberger
2015-11-08 23:30 ` Greg KH
2015-11-09 0:53 ` Josh Triplett
2015-11-09 8:34 ` David Herrmann
2015-11-09 8:37 ` Richard Weinberger [this message]
2015-11-09 8:48 ` Peter Zijlstra
2015-11-09 8:56 ` David Herrmann
2015-11-09 9:08 ` Borislav Petkov
2015-11-09 9:14 ` Peter Zijlstra
2015-11-09 9:19 ` David Herrmann
2015-11-09 9:28 ` Richard Weinberger
2015-11-09 15:02 ` Greg KH
2015-11-09 15:55 ` Richard Weinberger
2015-11-09 8:15 ` Richard Weinberger
2015-11-09 16:51 ` Andy Lutomirski
2015-11-09 17:02 ` Måns Rullgård
2015-11-09 17:07 ` Greg KH
2015-11-09 17:14 ` Måns Rullgård
2015-11-09 17:23 ` Andy Lutomirski
2015-11-12 5:35 ` Kalle A. Sandstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56405B3F.9060508@nod.at \
--to=richard@nod.at \
--cc=dh.herrmann@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=havoc.pennington@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.weinberger@gmail.com \
--cc=tixxdz@opendz.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.