workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Jakub Kicinski <kuba@kernel.org>, workflows@vger.kernel.org
Cc: linux-doc@vger.kernel.org
Subject: Re: Docs for base maintainer expectations?
Date: Tue, 11 Jul 2023 07:52:14 -0600	[thread overview]
Message-ID: <875y6q8sj5.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230710115239.3f9e2c24@kernel.org>

Jakub Kicinski <kuba@kernel.org> writes:

> 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?

I think that would be good to have.  We often complain about a lack of
maintainers, but we have nothing to point to telling people how they can
step up and do that.

I've tried to fill in some pieces with the documents on merging and
such, but we're missing the introduction.

Thanks,

jon

      parent reply	other threads:[~2023-07-11 13:52 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
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 [this message]

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=875y6q8sj5.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --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