From: Jiri Kosina <jkosina@suse.cz>
To: Takashi Iwai <tiwai@suse.de>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TOPIC] Guidance for subsystem maintainers
Date: Tue, 13 May 2014 16:31:49 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.00.1405131627480.16459@pobox.suse.cz> (raw)
In-Reply-To: <s5htx8tizaf.wl%tiwai@suse.de>
On Tue, 13 May 2014, Takashi Iwai wrote:
> While posting to different subsystem areas, I noticed various ways of
> responses and communications. Some picks up quick, some urges more
> reviews, sometimes a patch gets merged silently after months later,
> etc. Although the variety is one strength of OSS development, it made
> me also wonder whether we need some baseline guidance for subsystem
> maintenance in order to give a better appeal to casual developers.
>
> Is such a thing too much burden to maintainers? Or, is it just a
> bikeshedding?
I am afraid that any attempt to force any working style on maintainers is
pre-destined to fail.
As an example, there are folks who love patchwork and others wouldn't dare
to touch it with a 10m pole.
Even such a "core" thing as git is explicitly claimed optional by Linus.
Is there perhaps anything more concrete you had on mind?
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2014-05-13 14:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 13:27 Takashi Iwai
2014-05-13 14:31 ` Jiri Kosina [this message]
2014-05-13 14:55 ` Takashi Iwai
2014-05-13 14:57 ` Sarah A Sharp
2014-05-13 15:11 ` Laurent Pinchart
2014-05-13 15:32 ` Stephen Warren
2014-05-13 16:28 ` josh
2014-05-13 16:53 ` Olof Johansson
2014-05-13 18:06 ` Jiri Kosina
2014-05-13 19:02 ` Mark Brown
2014-05-16 3:18 ` Jason Cooper
2014-05-18 15:09 ` Mauro Carvalho Chehab
2014-05-20 16:06 ` Josh Triplett
2014-05-23 8:02 ` Linus Walleij
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=alpine.LNX.2.00.1405131627480.16459@pobox.suse.cz \
--to=jkosina@suse.cz \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=tiwai@suse.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox