ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: ksummit@lists.linux.dev, tech-board-discuss@lists.linux-foundation.org
Subject: Re: [MAINTAINERS SUMMIT] Maintainers Support Group
Date: Wed, 20 Sep 2023 16:45:56 +0100	[thread overview]
Message-ID: <b7f6d444-a3c0-459d-a683-8ea2e160160d@sirena.org.uk> (raw)
In-Reply-To: <20230919121001.7bc610d4@gandalf.local.home>

[-- Attachment #1: Type: text/plain, Size: 2261 bytes --]

On Tue, Sep 19, 2023 at 12:10:01PM -0400, Steven Rostedt wrote:

> The problem is that there's been no replacement for the maintainer to
> release their frustration.

...

> I brought up to the TAB a suggestion of starting basically a "Maintainer's
> support group". A place a maintainer, or even a submitter can go to when
> they are feeling frustrated. This is not a replacement for the Code of
> Conduct committee. This is more of a preventive measure. Ideally, the Code
> of Conduct committee members should be very bored where there are no
> submitted reports.  That would mean our community is running in a very
> smooth way. But that's currently not the case. There's been a few cases
> that have come up where if the maintainer had someone to vent to, it could
> have prevented the violation of the Code of Conduct.

...

> When a maintainer is getting frustrated with a submitter or another
> maintainer, or even a submitter is getting frustrated with a maintainer,
> they would have a place to find a list of people that can help. They would
> pick one of the people and send an email to them with a subject of
> "[MAINTAINER SUPPORT]" (or something like that). This would let the
> supporting maintainer know that this email is about support and should be
> confidential and follow the guidelines. The email will include who and why
> they are frustrated with the other person. Again, this is *not* a Code of
> Conduct issue. This is not to point blame, just frustration. Sometimes
> people just can not work with other people. The supporting maintainer can
> be an outside POV and can possibly help with explaining why the other
> person is acting the way they are. Or the supporting maintainer can find
> another maintainer to work with this person.

I think this is a really good idea, and I do think the bit about
submitters also getting frustrated with maintainers is important here -
there's a lot of "the process isn't working well" about this stuff which
will apply just as much to submitters.  It's going to be more obvious to
us as maintainers that there's issues for maintainers, and in general
submitters have more valves for releasing frustration (eg, for a lot of
them it's easy to just walk away, though that's not true for everyone).

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2023-09-20 15:46 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
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 [this message]
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=b7f6d444-a3c0-459d-a683-8ea2e160160d@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=ksummit@lists.linux.dev \
    --cc=rostedt@goodmis.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