Re: [MAINTAINERS SUMMIT] Maintainer burnout

[Laurent Pinchart <laurent.pinchart@ideasonboard.com>]

On Sat, Aug 19, 2023 at 09:45:37AM +0300, Leon Romanovsky wrote:
> On Fri, Aug 18, 2023 at 07:07:24PM +0200, Linus Torvalds wrote:
> > On Fri, 18 Aug 2023 at 17:10, Jakub Kicinski wrote:
> > >
> > > I was wondering last time if we can do a run of short sessions
> > > where a few volunteers talk about their subsystems? Let's say
> > > 10min talking about
> > >  - current process subsystem uses
> > >  - "realities" / day to day challenges / problems
> > >  - how the subsystem is evolving the process
> > 
> > I feel like we did exactly that a few years in a row, but it was
> > probably back before covid times, and probably when it was still
> > called the "kernel summit" rather than "maintainer summit".
> 
> <...>
> 
> > I do think the whole "how to spread the pain of being a maintainer" is
> > very much the point of the maintainer summit, though, so I do think we
> > should revisit.
> 
> It is worth to try to get honest feedback from active developers/contributors/vendors
> what is their "real" excuse for not doing code review.
> 
> I saw in this thread about "have no time to do code review" answers and we
> all can relate to it, but IMHO it is just an excuse and not the real reason.
> Especially for a people who are employed by big corporations to do their
> upstream work.
> 
> From what I personally saw, the reasons can be different from truly
> no time upto toxic subsystem behavior with huge variety and gray areas
> in between.

That can be the case, but I think that the "no time" excuse is not just
an excuse. Many developers working upstream, even (or perhaps especially
?) those working for large companies, are put under intense time
pressure by their management. If we want to consider the "no time"
reason as an excuse, we should see it as a management excuse, not an
individual contributor excuse.

> It is not clear to me how to get honest answers without fear of loosing
> an ability to work with that subsystems later.

One straightforward (on paper) option is to guarantee anonymity. When I
was in university, students were given the opportunity to provide
feedback on teachers, and the feedback was aggregated into a report that
didn't contain any personal information that could be used to identify
the students.

-- 
Regards,

Laurent Pinchart