ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Shuah <shuah@kernel.org>, Steven Rostedt <rostedt@goodmis.org>,
	 ksummit@lists.linux.dev,
	tech-board-discuss@lists.linux-foundation.org
Subject: Re: [Tech-board-discuss] [MAINTAINERS SUMMIT] Maintainers Support Group
Date: Tue, 19 Sep 2023 13:54:49 -0400	[thread overview]
Message-ID: <f5b4f69056a5ec104fc58e55137912495caf11d4.camel@HansenPartnership.com> (raw)
In-Reply-To: <371cb5d1-9997-a03b-4848-550ac8658021@kernel.org>

On Tue, 2023-09-19 at 10:52 -0600, Shuah wrote:
> Hi Steve,
> 
> On 9/19/23 10:10, Steven Rostedt wrote:
> > There has been several topics brought up already about maintainer
> > burnout.  A while back, I was talking with another maintainer that
> > basically told me that they were ready to quit being a maintainer
> > because it's not fun anymore. There's a lot of requirements and
> > basically have to deal with crap from submitters. The Code of
> > Conduct has been successful in helping to keep a more civil
> > environment, but all the focus has mainly been around telling
> > maintainers how to behave.
> 
> As a member of the CoC, I respectfully disagree with the statement
> "but all the focus has mainly been around telling maintainers how to
> behave." This impression might have been the result of one
> unfortunate incident that took place last year. is only part of what
> CoC has been doing.

If it helps, I proposed a more generic version of a maintainer stress
session here:

https://lore.kernel.org/ksummit/ab9cfd857e32635f626a906410ad95877a22f0db.camel@HansenPartnership.com/

It doesn't mention the code of conduct at all.  I really think
focussing on stress coping rather than pointing fingers at the alleged
stress inducers would be the way to move forwards on this.  Although it
might be helpful to have a non judgmental listening session about what
everyone thinks the major stress inducers are.

James




  parent reply	other threads:[~2023-09-19 17:54 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-19 16:10 Steven Rostedt
2023-09-19 16:52 ` [Tech-board-discuss] " Shuah
2023-09-19 17:19   ` Steven Rostedt
2023-09-19 17:29     ` Steven Rostedt
2023-09-19 17:54   ` James Bottomley [this message]
2023-09-19 21:26     ` Shuah
2023-09-19 20:39   ` Theodore Ts'o
2023-09-19 21:02     ` Steven Rostedt
2023-09-20 12:03       ` Christian Brauner
2023-09-19 22:01     ` Theodore Ts'o
2023-09-19 22:07       ` Randy Dunlap
2023-09-19 22:40         ` Shuah
2023-09-19 22:32     ` Shuah
2023-09-19 22:53       ` Shuah
2023-09-19 17:03 ` Bart Van Assche
2023-09-19 17:21   ` Steven Rostedt
2023-09-19 22:55     ` Shuah
2023-09-19 23:21       ` Steven Rostedt
2023-09-20  7:06         ` Linus Walleij
2023-09-21  7:15           ` Jonathan Cameron
2023-09-20 19:52         ` Shuah
2023-09-20 22:54           ` Laurent Pinchart
2023-09-21  0:45             ` Shuah
2023-09-21 12:40             ` Linus Walleij
2023-09-21 12:56               ` Laurent Pinchart
2023-09-20 15:45 ` Mark Brown
2023-10-05 18:08   ` Jason Gunthorpe
2023-10-06 20:47     ` Linus Walleij

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=f5b4f69056a5ec104fc58e55137912495caf11d4.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=ksummit@lists.linux.dev \
    --cc=rostedt@goodmis.org \
    --cc=shuah@kernel.org \
    --cc=tech-board-discuss@lists.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox