From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jonathan Cameron <jic23@kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Jakub Kicinski <kuba@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
Luis Chamberlain <mcgrof@kernel.org>,
Josef Bacik <josef@toxicpanda.com>,
ksummit@lists.linux.dev, Jeff Layton <jlayton@kernel.org>,
Song Liu <song@kernel.org>
Subject: Re: [MAINTAINERS SUMMIT] Maintainer burnout
Date: Fri, 25 Aug 2023 09:05:30 +0200 [thread overview]
Message-ID: <7a692436-3643-4a12-95b2-3decb38cda89@kernel.org> (raw)
In-Reply-To: <20230824223009.5d4ad0a4@jic23-huawei>
On 24/08/2023 23:30, Jonathan Cameron wrote:
>>>> We're trying to encourage active developers to be code reviewers as well
>>>> via positive/negative scores:
>>>> https://lore.kernel.org/bpf/ZJx8sBW%2FQPOBswNF@google.com/
>>>>
>>>> It doesn't help much yet. All incoming kernel contributors assume
>>>> that it's a maintainer's job to do code reviews.
>>>> Developers just send patches and wait. It doesn't occur to them that
>>>> reviewing other patches will help them land their own.
>>>
>>> The DRI/DRM community has group maintainership that works a little
>>> bit.
>>> Essentially it boils down to ask people to review your stuff and you
>>> will review and also merge their stuff in return.
>>> Sometimes this works.
>>> Especially if you are a circle of acquaintances working full
>>> time on similar things, yay! So much support.
>>> When you are a sporadic contributor it doesn't work as well.
>>> Because you cannot always find some matching contribution to
>>> review and you feel like begging.
>>> So different solutions for different contributors may be needed.
>>
>> I've also experienced mixed results from "trading reviews". It's
>> certainly nice on paper, and it works sometimes, especially when asking
>> contributors to review patches that are directly related to their
>> business interest. I remember asking a contributor from a large company
>> to help me with reviews, to free some of my time to review their
>> patches.
>
> Personally I like to point out to our kernel teams that if a maintainer
> is ignoring you (too busy), the best thing is to help (guilt trip) them
> by reviewing anything else you can find they haven't gotten to yet.
> Added 'benefit' beyond learning more about the area is you often end
> suggesting changes for the other outstanding patches resulting a new version
> of their patches that is further down in patchwork or similar so maintainer
> tends to get to yours quicker...
I'll start responding with this to pings on LKML. I think Greg already
does for some cases.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-08-25 7:05 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 18:08 [MAINTAINERS SUMMIT] Maintainer burnout Josef Bacik
2023-08-16 20:14 ` Luis Chamberlain
2023-08-17 9:39 ` Laurent Pinchart
2023-08-17 12:36 ` Andrew Lunn
2023-08-17 15:19 ` Jakub Kicinski
2023-08-17 23:54 ` Alexei Starovoitov
2023-08-18 13:55 ` Linus Walleij
2023-08-18 15:09 ` Jakub Kicinski
2023-08-18 17:07 ` Linus Torvalds
2023-08-19 6:45 ` Leon Romanovsky
2023-08-21 15:35 ` Laurent Pinchart
2023-08-22 7:41 ` Jiri Kosina
2023-08-22 9:05 ` Hannes Reinecke
2023-08-22 10:13 ` Leon Romanovsky
2023-08-22 11:25 ` Laurent Pinchart
2023-08-21 19:23 ` Vegard Nossum
2023-08-22 4:07 ` Dave Airlie
2023-08-22 9:46 ` Jan Kara
2023-08-22 10:10 ` Christian Brauner
2023-08-22 10:20 ` Jan Kara
2023-08-22 11:29 ` Laurent Pinchart
2023-08-22 11:05 ` Leon Romanovsky
2023-08-22 11:32 ` Laurent Pinchart
2023-08-22 13:47 ` Leon Romanovsky
2023-08-22 13:30 ` Jan Kara
2023-08-29 12:54 ` Steven Rostedt
2023-09-13 9:02 ` Dan Carpenter
2023-08-21 8:50 ` Daniel Vetter
2023-08-21 15:18 ` Jakub Kicinski
2023-08-22 4:12 ` Dave Airlie
2023-08-18 15:26 ` Laurent Pinchart
2023-08-18 15:40 ` Konrad Rzeszutek Wilk
2023-08-18 18:36 ` Mark Brown
2023-08-21 16:13 ` Laurent Pinchart
2023-08-18 16:10 ` Mark Brown
2023-08-21 16:04 ` Laurent Pinchart
2023-08-24 21:30 ` Jonathan Cameron
2023-08-25 7:05 ` Krzysztof Kozlowski [this message]
2023-08-17 12:00 ` Jani Nikula
2023-08-17 12:17 ` Mark Brown
2023-08-17 12:42 ` Laurent Pinchart
2023-08-17 13:56 ` Miguel Ojeda
2023-08-17 15:03 ` Laurent Pinchart
2023-08-17 17:41 ` Miguel Ojeda
2023-08-18 15:30 ` Laurent Pinchart
2023-08-18 16:23 ` Mark Brown
2023-08-18 17:17 ` Laurent Pinchart
2023-08-18 18:00 ` Mark Brown
2023-08-17 14:46 ` Mark Brown
2023-08-17 14:22 ` Steven Rostedt
2023-08-17 15:31 ` Jani Nikula
2023-08-17 14:46 ` Steven Rostedt
2023-08-17 15:33 ` Josef Bacik
2023-08-17 17:10 ` Rodrigo Vivi
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=7a692436-3643-4a12-95b2-3decb38cda89@kernel.org \
--to=krzk@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrew@lunn.ch \
--cc=jic23@kernel.org \
--cc=jlayton@kernel.org \
--cc=josef@toxicpanda.com \
--cc=ksummit@lists.linux.dev \
--cc=kuba@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linus.walleij@linaro.org \
--cc=mcgrof@kernel.org \
--cc=song@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.