From: Linus Walleij <linus.walleij@linaro.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Mark Brown <broonie@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
ksummit@lists.linux.dev,
tech-board-discuss@lists.linux-foundation.org
Subject: Re: [MAINTAINERS SUMMIT] Maintainers Support Group
Date: Fri, 6 Oct 2023 22:47:48 +0200 [thread overview]
Message-ID: <CACRpkdafk6bFTNUN=HJ-5j_BvNWXgRGh-NCHt6pibT+YNfHtDg@mail.gmail.com> (raw)
In-Reply-To: <20231005180833.GA975221@nvidia.com>
On Thu, Oct 5, 2023 at 8:08 PM Jason Gunthorpe <jgg@nvidia.com> wrote:
> It would be nice to stop talking about this in terms of sides and
> focus on the submitter/maintainer relationship as a whole. The issues
> I'm aware of are not CoC violations, but nevertheless they have upset
> people. There are a whole host of behaviors sumitters/maintainers can
> choose to do that range hurtful to non-productive.
(...)
> I don't want to be a downer but I've chatted with a enough people now
> to say that things seem to be getting worse - it *feels* worse to
> participate these days. eg I just finished a nice big series for
> something outside the areas I maintain and I'm dreading the process of
> merging it :\ Then I think: I wonder if people feel the same way about
> my areas? No idea, nobody says.
What are these things?
I've had the same feeling and I can think of some that would give me
the same fear and feel like a newbie contributor once again. Mostly
I think it's good for me to feel like that, but that is maybe not universally
true.
One thing I clearly noticed are increased barriers to entry for
newcomers, for project size, "professionalism", etc leading to
endless patch reviews with increasingly nitty review comments,
leading to perfect-is-the-enemy-of-good situations with all the best
intentions from all sides.
Linus Walleij
prev parent reply other threads:[~2023-10-06 20:48 UTC|newest]
Thread overview: 28+ 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: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
2023-10-05 18:08 ` Jason Gunthorpe
2023-10-06 20:47 ` Linus Walleij [this message]
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='CACRpkdafk6bFTNUN=HJ-5j_BvNWXgRGh-NCHt6pibT+YNfHtDg@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=broonie@kernel.org \
--cc=jgg@nvidia.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).