From: Krzysztof Kozlowski <krzk@kernel.org>
To: Linux regressions mailing list <regressions@lists.linux.dev>,
Jakub Kicinski <kuba@kernel.org>
Cc: corbet@lwn.net, workflows@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
gregkh@linuxfoundation.org, Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH docs] docs: maintainer: document expectations of small time maintainers
Date: Mon, 17 Jul 2023 09:49:09 +0200 [thread overview]
Message-ID: <895ed8ae-e93f-b296-330e-356cda698de2@kernel.org> (raw)
In-Reply-To: <bb8c6476-283c-3bc6-710b-5a8602ccd40e@leemhuis.info>
On 15/07/2023 12:31, Linux regression tracking (Thorsten Leemhuis) wrote:
> [CCing other people in the thread]
> How about something like this:
>
> ```
> Bug reports
> -----------
>
> Maintainers must ensure severe problems in their code reported to them
> are resolved in a timely manner: security vulnerabilities, regressions,
> compilation errors, data loss, kernel crashes, and bugs of similar scope.
>
> Maintainers furthermore should respond to reports about other kind of
> bugs as well, if the report is of reasonable quality or indicates a
> problem that might be severe -- especially if they have *Supported*
> status of the codebase in the MAINTAINERS file.
I like mentioning the "Supported" part. We should be a bit more
understanding to all folks who are not paid to do this.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-07-17 7:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 22:34 [PATCH docs] docs: maintainer: document expectations of small time maintainers Jakub Kicinski
2023-07-14 4:36 ` Krzysztof Kozlowski
2023-07-14 5:05 ` Matthew Wilcox
2023-07-14 17:10 ` Jakub Kicinski
2023-07-15 10:31 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-17 7:49 ` Krzysztof Kozlowski [this message]
2023-07-17 14:37 ` Greg KH
2023-07-18 15:37 ` Jakub Kicinski
2023-07-18 16:02 ` Thorsten Leemhuis
2023-07-17 7:44 ` Krzysztof Kozlowski
2023-07-14 6:24 ` Thorsten Leemhuis
2023-07-14 17:22 ` Jakub Kicinski
2023-07-14 17:59 ` Mark Brown
2023-07-14 18:34 ` Jakub Kicinski
2023-07-14 20:02 ` Mark Brown
2023-07-15 6:38 ` Greg KH
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=895ed8ae-e93f-b296-330e-356cda698de2@kernel.org \
--to=krzk@kernel.org \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--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 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.