[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZLDXjzbp5tJ3UjjP@casper.infradead.org>
Date: Fri, 14 Jul 2023 06:05:19 +0100
From: Matthew Wilcox <willy@...radead.org>
To: Krzysztof Kozlowski <krzk@...nel.org>
Cc: Jakub Kicinski <kuba@...nel.org>, corbet@....net,
workflows@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, gregkh@...uxfoundation.org
Subject: Re: [PATCH docs] docs: maintainer: document expectations of small
time maintainers
On Fri, Jul 14, 2023 at 06:36:41AM +0200, Krzysztof Kozlowski wrote:
> On 14/07/2023 00:34, Jakub Kicinski wrote:
> > +Responsibilities
> > +================
> > +
> > +The amount of maintenance work is usually proportional to the size
> > +and popularity of the code base. Small features and drivers should
> > +require relatively small amount of care and feeding. Nonetheless
> > +when the work does arrive (in form of patches which need review,
> > +user bug reports etc.) it has to be acted upon very promptly.
> > +Even when single driver only sees one patch a month, or a quarter,
> > +a subsystem could well have a hundred such drivers. Subsystem
> > +maintainers cannot afford to wait a long time to hear from reviewers.
> > +
> > +The exact expectations on the review time will vary by subsystem
> > +from 1 day (e.g. networking) to a week in smaller subsystems.
>
> Two weeks is the upper limit.
Indeed. People need to be able to take holiday. Maybe this is
partially covered by "multiple maintainers", but even so, it is
unreasonable to expect this kind of responsiveness.
Powered by blists - more mailing lists