From: Dave Taht <dave.taht@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: tech-board-discuss@lists.linux-foundation.org, ksummit@lists.linux.dev
Subject: Re: [Tech-board-discuss] [MAINTAINERS SUMMIT] Maintainers Support Group
Date: Tue, 19 Sep 2023 10:48:52 -0700 [thread overview]
Message-ID: <CAA93jw7nPh3N0my-sVV=4jB0kKeGR1DsUjAu8WJYX6niHgW75Q@mail.gmail.com> (raw)
In-Reply-To: <20230919121001.7bc610d4@gandalf.local.home>
[-- Attachment #1: Type: text/plain, Size: 2152 bytes --]
When I read the title of this thread:
I thought that AWESOME, someone might pay for sufficient health insurance
that a maintainer could afford to pay a therapist to listen to their
problems.
So if there could be some sort of maintainer health therapy plan where
someone could blow their stack, anonymized, + a black couch to vent on + an
endless supply of tranks and ADD meds, and/or get a service animal like a
tribble for comfort, I´d be all for it. Sometimes I do think expressing
yourself in an uncivil way gets results that being nice doesn´t.
I am personally feeling rather battered and bruised lately, with the
onslaught of new embedded users of code I last worked on 7 years ago[1],
and how it has been mis-represented by marketing folk to them, only to find
out in test, it did not solve anything, configured how the marketing folk
mis-described it. I am deluged these past 6 months with seemingly endless
requests - from low level staff at some really big corps (I am not going to
name names) - to somehow jump in, for free, and fix it NOW, when the core
tech , required patient, incremental, development across the whole stack,
driver support especially, and years of testing.
If there is any one thing I wish the linux community could resume doing, is
to somehow cut the time from development to deployment down from the
present day 7-10 years to something reasonable, like 2. I remember when we
used to stress to external users the need to work with the community, in
embedded, back in the 00s, at least.
A means for the community to somehow represent itself better, and have
someone more tactful, equipped with a flame-proof suit, able to explain
issues of available funding and time consistently, and well, would be nice,
also.
[1] I am responding to my deluge as best I can.
https://docs.google.com/document/d/1tTYBPeaRdCO9AGTGQCpoiuLORQzN_bG3TAkEolJPh28/edit#heading=h.vbbnfu73wlpp
[2] This is as close as I have come to blowing my stack in a while. Is it a
safe space for it? :) I originally used another word in this email for
"marketing-folk", that I figure is now prohibited speech.
[-- Attachment #2: Type: text/html, Size: 2465 bytes --]
next prev parent reply other threads:[~2023-09-19 17:48 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 16:10 [Tech-board-discuss] [MAINTAINERS SUMMIT] Maintainers Support Group Steven Rostedt
2023-09-19 16:52 ` 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
[not found] ` <dbeb5ad9-fa6d-4633-a160-6a0f8ed6bd51@acm.org>
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-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-19 17:48 ` Dave Taht [this message]
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='CAA93jw7nPh3N0my-sVV=4jB0kKeGR1DsUjAu8WJYX6niHgW75Q@mail.gmail.com' \
--to=dave.taht@gmail.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).