ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: ksummit@lists.linux.dev
Subject: [MAINTAINER SUMMIT] resources for promoting healthy communities
Date: Wed, 17 Sep 2025 12:36:52 -0400	[thread overview]
Message-ID: <572009db624de21099e08f28604f4b8e6a472cf2.camel@HansenPartnership.com> (raw)

We talk a lot about community health and maintainer burn out but what
struck me watching Hans' talk about this:

https://www.youtube.com/watch?v=O8Q8nIzEG6c

was that he relied on his employer to help him thorough his burnout
problems.  While this reflects very creditably on Red Hat it struck me
that quite a few of us probably have employers who would be less
sympathetic to the idea that issues caused by being an open source
maintainer should become their problem, especially if they were
spilling over into internal job functions.  So I went looking for
community resources that could be called on and found, rather
distressingly given the amount that people talk about this, that there
are none.  The best I can find was the session that happened in the
Kernel Summit track:

https://lpc.events/event/17/contributions/1574/

But that was a one-off rather than a resource that anyone can call on
at any time.  So the topic I'd like to raise is what should we as a
community actually be providing to help people through burn out and
other community health issues?  We could just continue on as we are now
which is pretty much nothing official but various community members
will be happy to help (although good luck finding them listed
anywhere).  We could make the self help support more official by
providing a mailing list and possibly a wiki of volunteers specifically
for the purpose.  Or, we could even decide that this is a serious
enough problem to ask the LF if it would be amenable to providing us
with some resources to help, thinks like organizing regular sessions
like the plumbers one above and perhaps offering 1:1 video counseling
and other resources.

Regards,

James


             reply	other threads:[~2025-09-17 16:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-17 16:36 James Bottomley [this message]
2025-09-23  1:21 ` dan.j.williams
2025-09-23 17:02   ` Shuah Khan

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=572009db624de21099e08f28604f4b8e6a472cf2.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=ksummit@lists.linux.dev \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox