workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: workflows@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: Docs for base maintainer expectations?
Date: Mon, 10 Jul 2023 20:06:56 +0100	[thread overview]
Message-ID: <20230710-snowboard-bannister-7ed66c8d742b@spud> (raw)
In-Reply-To: <20230710115239.3f9e2c24@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]

Hey Jakub,

On Mon, Jul 10, 2023 at 11:52:39AM -0700, Jakub Kicinski wrote:
> do we have any docs describing what's expected from folks stepping up
> to maintain (small-ish) parts of the kernel like a driver or a protocol?
> 
> Experienced developers / maintainers differ like the beautiful
> snowflakes that we are, but outsiders have much less familiarity 
> with the landscape, and frankly sometimes much less interest in
> participating once they code lands.
> 
> Which makes we wonder if a simple list of responsibilities would be
> useful as a baseline.

> I haven't spotted anything in Docs/process but
> perhaps someone has a local version for their subsystem?

Given I figure you did this on with a -rc1 based tree, which would mean
that what I wrote probably does not fit the bill, but I tried to do
something along these lines with
https://docs.kernel.org/process/maintainer-soc.html
for which my target audience was people picking up maintenance of
DT/soc drivers, which I hope there'll be a few of in RISC-V land soon...

I suggested adding things to it, like putting the trees in linux-next
etc, but review feedback suggested that was unsuited to a subsystem
specific document.

Thanks,
Conor.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-07-10 19:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-10 18:52 Jakub Kicinski
2023-07-10 19:06 ` Conor Dooley [this message]
2023-07-10 19:22   ` Jakub Kicinski
2023-07-10 19:39     ` Conor Dooley
2023-07-10 20:46       ` Jakub Kicinski
2023-07-11 13:52 ` Jonathan Corbet

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=20230710-snowboard-bannister-7ed66c8d742b@spud \
    --to=conor@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=workflows@vger.kernel.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