From: Sarah Sharp <sarah.a.sharp@linux.intel.com>
To: Rob Landley <rob@landley.net>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [RFC 5/7] Docs: Expectations for bug reporters and maintainers
Date: Thu, 18 Apr 2013 16:52:45 -0700 [thread overview]
Message-ID: <20130418235245.GA3565@xanatos> (raw)
In-Reply-To: <1366242580.18069.116@driftwood>
On Wed, Apr 17, 2013 at 06:49:40PM -0500, Rob Landley wrote:
> On 04/17/2013 01:23:28 PM, Sarah Sharp wrote:
> >On Tue, Apr 16, 2013 at 09:15:06PM -0500, Rob Landley wrote:
> >> On 04/15/2013 12:33:34 PM, Sarah Sharp wrote:
> >> >Outline how often it's polite to ping kernel maintainers about
> >> >bugs, and
> >> >suggest that kernel maintainers should respond to bugs in 1 to 5
> >> >business days.
> >>
> >> Is there anything in here about the four-level nature of modern
> >> maintainership?
> >>
> >> Patches go from the developer, to the maintainer, to one of Linus's
> >> lieutenants, to Linus himself. If you submit a patch to a maintainer
> >> they owe you a response. The lieutenant (subsystem maintainer) owes
> >> that maintainer a response, and Linus (the project's architect) owes
> >> the lieutenant a response.
> >
> >Do we want to go into this much detail in a document meant for
> >frustrated bug reporters? Or perhaps we should create a separate
> >document about the kernel maintainer hierarchy and reference it here?
>
> My point was that you have to contact the right person to
> semi-reliably get a response, but you're right. That's more about
> getting patches in than getting problems reproduced and diagnosed.
No worries! I think it's really useful for patch submitters to get
their work to the right maintainers as well. That description just
doesn't belong here. :)
> >This file is about bug reporting, not submitting patches.
> ...
> >TLDR version: Yes, it would be nice if bug reporters could go up the
> >hierarchy, but they don't have an easy way to know which subsystem
> >maintainers to contact. Perhaps a new line in MAINTAINERS for the
> >subsystem maintainer would be helpful?
>
> It seemed related at the time (general interacting with the
> kernel developers), but I guess not.
Ok. Do you think the new line in MAINTAINERS would be useful as a
separate patch? Possibly if it came from the subsystem maintainers
themselves?
> Eh, this has gone undocumented for a full decade and nobody but me's
> cared.
I think it's less "nobody but me's cared" and more "no one with
knowledge of the community is willing to write basic documentation that
is needed". People care, just not the ones with enough expertise to
write docs.
I do care about good documentation, so I suspect you'll be getting
more patches from me in the future. :)
Any other feedback on this patchset? If not, are you going to send
it to Linus for 3.10 or should I?
Sarah Sharp
next prev parent reply other threads:[~2013-04-18 23:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 17:33 [RFC 0/7] Update REPORTING-BUGS Sarah Sharp
2013-04-15 17:33 ` [RFC 1/7] Trivial: docs: Remove six-space indentation in REPORTING-BUGS Sarah Sharp
2013-04-15 17:33 ` [RFC 2/7] Docs: Step-by-step directions for reporting bugs Sarah Sharp
2013-04-15 17:33 ` [RFC 3/7] Docs: Add "Gather info" section to REPORTING-BUGS Sarah Sharp
2013-04-15 17:33 ` [RFC 4/7] Docs: Add info on supported kernels " Sarah Sharp
2013-04-17 0:24 ` Rob Landley
2013-04-15 17:33 ` [RFC 5/7] Docs: Expectations for bug reporters and maintainers Sarah Sharp
2013-04-17 2:15 ` Rob Landley
2013-04-17 18:23 ` Sarah Sharp
2013-04-17 23:49 ` Rob Landley
2013-04-18 23:52 ` Sarah Sharp [this message]
2013-04-20 6:24 ` Rob Landley
2013-04-19 6:08 ` Greg KH
2013-05-01 15:26 ` Mark Brown
2013-04-15 17:33 ` [RFC 6/7] Docs: Add a tips section to REPORTING-BUGS Sarah Sharp
2013-04-15 17:33 ` [RFC 7/7] Docs: Move ref to Frohwalt Egerer to end of REPORTING-BUGS Sarah Sharp
2013-04-15 21:40 ` [RFC 0/7] Update REPORTING-BUGS Linus Torvalds
2013-04-16 1:47 ` Theodore Ts'o
2013-04-16 21:58 ` Sarah Sharp
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=20130418235245.GA3565@xanatos \
--to=sarah.a.sharp@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox