From: Shuah <shuah@kernel.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Bart Van Assche <bvanassche@acm.org>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
ksummit@lists.linux.dev,
tech-board-discuss@lists.linux-foundation.org,
shuah <shuah@kernel.org>
Subject: Re: [MAINTAINERS SUMMIT] Maintainers Support Group
Date: Wed, 20 Sep 2023 18:45:46 -0600 [thread overview]
Message-ID: <38893d55-337e-692d-6eb6-999ae8d515ae@kernel.org> (raw)
In-Reply-To: <20230920225441.GA12561@pendragon.ideasonboard.com>
On 9/20/23 16:54, Laurent Pinchart wrote:
> On Wed, Sep 20, 2023 at 01:52:19PM -0600, Shuah wrote:
>> On 9/19/23 17:21, Steven Rostedt wrote:
>>> On Tue, 19 Sep 2023 16:55:29 -0600 Shuah wrote:
>>>
>>>> As I replied to Ted and Randy, I think the proposal James pointed to is
>>>> where we could start and evolve that discussion to the actions such as
>>>> support group, instead of starting with a solution without looking at
>>>> the bigger picture.
>>>>
>>>> https://lore.kernel.org/ksummit/ab9cfd857e32635f626a906410ad95877a22f0db.camel@HansenPartnership.com/
>>>
>>> I saw this when James first posted it. I may have been the lone figure to
>>> do so as I had to point it out when the topic came up a second time ;-)
>>>
>>> https://lore.kernel.org/all/20230817104622.511c61b4@gandalf.local.home/
>>>
>>> I'm all for having this discussion under James topic, but this idea of a
>>> Support Group is something I've been discussing with other maintainers for
>>> some time. I believe I even mentioned it to you while on the bus in Dublin.
>>
>> Thank you. Yes. We talked about this last year at Dublin. Work of being an
>> Open source developer and especially a maintainer demands emotional labor.
>> This is definitely a risk factor for burnout.
>>
>> I happened to com across an article today about burnout risk factors and some
>> of those are faced by maintainers and developers. If you are interested, I can
>> send the link.
>
> Collecting interesting (and hopefully useful) resources is a fairly low
> effort exercise, so I'll start:
>
> "Negotiating the Nonnegotiable", by Daniel Shapiro
> https://www.penguinrandomhouse.com/books/314284/negotiating-the-nonnegotiable-by-daniel-shapiro/
Adding one I read this morning:
A Burnout Risk Checklist
Know your risk so you can prevent burnout.
https://www.psychologytoday.com/us/blog/lessons-from-a-burnt-out-psychologist/202309/a-burnout-risk-checklist
>
>> I would recommend discussion this prior to the Maintainer summit in an open
>> session to get input from developers and maintainers who aren't invited to
>> the maintainers summit myself included.
>
> I wonder if I'm stating the obvious, but trying to figure out ways to
> handle psychological problems in a group made of software developers
> seems like we will be fairly short on essential skills for this kind of
> exercise. Given the size of the affected community, I think we could
> find ways to get professional help.
>
This discussion would be for coming up with a few solutions including
the one you suggested - "find ways to get professional help".
thanks,
-- Shuah
WARNING: multiple messages have this Message-ID (diff)
From: Shuah <shuah@kernel.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Bart Van Assche <bvanassche@acm.org>,
tech-board-discuss@lists.linux-foundation.org,
James Bottomley <James.Bottomley@hansenpartnership.com>,
ksummit@lists.linux.dev, shuah <shuah@kernel.org>
Subject: Re: [Tech-board-discuss] [MAINTAINERS SUMMIT] Maintainers Support Group
Date: Wed, 20 Sep 2023 18:45:46 -0600 [thread overview]
Message-ID: <38893d55-337e-692d-6eb6-999ae8d515ae@kernel.org> (raw)
In-Reply-To: <20230920225441.GA12561@pendragon.ideasonboard.com>
On 9/20/23 16:54, Laurent Pinchart wrote:
> On Wed, Sep 20, 2023 at 01:52:19PM -0600, Shuah wrote:
>> On 9/19/23 17:21, Steven Rostedt wrote:
>>> On Tue, 19 Sep 2023 16:55:29 -0600 Shuah wrote:
>>>
>>>> As I replied to Ted and Randy, I think the proposal James pointed to is
>>>> where we could start and evolve that discussion to the actions such as
>>>> support group, instead of starting with a solution without looking at
>>>> the bigger picture.
>>>>
>>>> https://lore.kernel.org/ksummit/ab9cfd857e32635f626a906410ad95877a22f0db.camel@HansenPartnership.com/
>>>
>>> I saw this when James first posted it. I may have been the lone figure to
>>> do so as I had to point it out when the topic came up a second time ;-)
>>>
>>> https://lore.kernel.org/all/20230817104622.511c61b4@gandalf.local.home/
>>>
>>> I'm all for having this discussion under James topic, but this idea of a
>>> Support Group is something I've been discussing with other maintainers for
>>> some time. I believe I even mentioned it to you while on the bus in Dublin.
>>
>> Thank you. Yes. We talked about this last year at Dublin. Work of being an
>> Open source developer and especially a maintainer demands emotional labor.
>> This is definitely a risk factor for burnout.
>>
>> I happened to com across an article today about burnout risk factors and some
>> of those are faced by maintainers and developers. If you are interested, I can
>> send the link.
>
> Collecting interesting (and hopefully useful) resources is a fairly low
> effort exercise, so I'll start:
>
> "Negotiating the Nonnegotiable", by Daniel Shapiro
> https://www.penguinrandomhouse.com/books/314284/negotiating-the-nonnegotiable-by-daniel-shapiro/
Adding one I read this morning:
A Burnout Risk Checklist
Know your risk so you can prevent burnout.
https://www.psychologytoday.com/us/blog/lessons-from-a-burnt-out-psychologist/202309/a-burnout-risk-checklist
>
>> I would recommend discussion this prior to the Maintainer summit in an open
>> session to get input from developers and maintainers who aren't invited to
>> the maintainers summit myself included.
>
> I wonder if I'm stating the obvious, but trying to figure out ways to
> handle psychological problems in a group made of software developers
> seems like we will be fairly short on essential skills for this kind of
> exercise. Given the size of the affected community, I think we could
> find ways to get professional help.
>
This discussion would be for coming up with a few solutions including
the one you suggested - "find ways to get professional help".
thanks,
-- Shuah
next prev parent reply other threads:[~2023-09-21 0:45 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 16:10 [MAINTAINERS SUMMIT] Maintainers Support Group Steven Rostedt
2023-09-19 16:10 ` [Tech-board-discuss] " Steven Rostedt
2023-09-19 16:52 ` Shuah
2023-09-19 17:19 ` Steven Rostedt
2023-09-19 17:19 ` Steven Rostedt
2023-09-19 17:29 ` 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 20:39 ` Theodore Ts'o
2023-09-19 21:02 ` Steven Rostedt
2023-09-19 21:02 ` Steven Rostedt
2023-09-20 12:03 ` Christian Brauner
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:40 ` Shuah
2023-09-19 22:32 ` Shuah
2023-09-19 22:32 ` Shuah
2023-09-19 22:53 ` 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 17:21 ` [Tech-board-discuss] " Steven Rostedt
2023-09-19 22:55 ` Shuah
2023-09-19 22:55 ` [Tech-board-discuss] " Shuah
2023-09-19 23:21 ` Steven Rostedt
2023-09-19 23:21 ` [Tech-board-discuss] " Steven Rostedt
2023-09-20 7:06 ` Linus Walleij
2023-09-20 7:06 ` [Tech-board-discuss] " Linus Walleij
2023-09-21 7:15 ` Jonathan Cameron
2023-09-20 19:52 ` Shuah
2023-09-20 19:52 ` [Tech-board-discuss] " Shuah
2023-09-20 22:54 ` Laurent Pinchart
2023-09-20 22:54 ` [Tech-board-discuss] " Laurent Pinchart
2023-09-21 0:45 ` Shuah [this message]
2023-09-21 0:45 ` Shuah
2023-09-21 12:40 ` Linus Walleij
2023-09-21 12:40 ` [Tech-board-discuss] " Linus Walleij
2023-09-21 12:56 ` Laurent Pinchart
2023-09-21 12:56 ` [Tech-board-discuss] " Laurent Pinchart
2023-09-19 17:48 ` Dave Taht
2023-09-20 15:45 ` Mark Brown
2023-09-20 15:45 ` [Tech-board-discuss] " Mark Brown
2023-10-05 18:08 ` Jason Gunthorpe
2023-10-05 18:08 ` [Tech-board-discuss] " Jason Gunthorpe
2023-10-06 20:47 ` Linus Walleij
2023-10-06 20:47 ` [Tech-board-discuss] " 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=38893d55-337e-692d-6eb6-999ae8d515ae@kernel.org \
--to=shuah@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=bvanassche@acm.org \
--cc=ksummit@lists.linux.dev \
--cc=laurent.pinchart@ideasonboard.com \
--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 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.