Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Fri, 14 Jul 2023 10:22:18 -0700
From:   Jakub Kicinski <kuba@kernel.org>
To:     Thorsten Leemhuis <linux@leemhuis.info>
Cc:     corbet@lwn.net, workflows@vger.kernel.org,
        linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
        gregkh@linuxfoundation.org
Subject: Re: [PATCH docs] docs: maintainer: document expectations of small
 time maintainers
Message-ID: <20230714102218.687ee2ea@kernel.org>
In-Reply-To: <f61a12c6-9587-9cb4-122e-dc3a74e58bd1@leemhuis.info>
References: <20230713223432.1501133-1-kuba@kernel.org>
        <f61a12c6-9587-9cb4-122e-dc3a74e58bd1@leemhuis.info>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Fri, 14 Jul 2023 08:24:38 +0200 Thorsten Leemhuis wrote:
> Also: It's totally normal that commercial vendor contribute basic
> drivers with known problems and missing features (some of which will
> never be implemented). The latter will be considered a "bug" for quite a
> few users that read this. Those suddenly thus might becomes something
> they now "must" fix, which leads to questions: how fast? just in
> mainline, or in stable, too?

If we try to fend off anyone who doesn't understand common meaning 
of words the document will be very long and painful to read.

> All this also opens questions like "what counts as bug report" -- I'd
> assume users that find and read this will expect that a report in
> bugzilla.kernel.org is one maintainers "must" respond to. But I assume
> you only meant bugs reports by mail or in trackers the MAINTAINERS file
> mentions?

I don't want to be too prescriptive, subsystems will vary.

> And overall I don't really like the way how handling of regressions is
> described in that section, as they afaics are expected to be handled
> with a higher priority than bugs.

Me neither, FWIW. I tried a couple of times to weave that information
in but I can't come up with a way of doing that without breaking the
logical flow. Could just be me. Edit to what I sent to Krzysztof would
be appreciated if you have one in mind.