public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Eli Schwartz <eschwartz93@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proxy-maint PR queue resolution speed (Was: Imminent Python 3.12 switch reminder)
Date: Thu, 30 May 2024 18:11:01 -0400	[thread overview]
Message-ID: <9f979845-322e-4f22-b0a1-d5822d4f477e@gmail.com> (raw)
In-Reply-To: <20240530080956.66746a7d@Akita>


[-- Attachment #1.1.1: Type: text/plain, Size: 1819 bytes --]

On 5/30/24 11:09 AM, orbea wrote:
> This is a reoccurring theme and its driving away contributors. The PR
> queue really should be taken care of.


It is a recurring theme in the volunteer open source community that
people work on stuff as and when they have time to do so, which also
means that contributors sometimes have to wait until people are
available to merge PRs.

There are some things that can help make sure people have more time to
volunteer for free to do OSS things:

- carefully consider before adding new packages. Maybe they belong in
  GURU instead? This is something a lot of people have trouble with, I
  fear.

- review PRs, even if you're not a developer, to help polish things up
  so there is less for developers to have to sort through.

- help out in other areas of Gentoo, such as bug wrangling, release
  engineering, or fixing outstanding bugs in packages maintained by
  developers rather than their own proxy-maint packages

- or even just being a sympathetic and friendly ear when developers are
  feeling down from the stress of doing open source work


There are also some things that I personally do not think are especially
helpful:

- complaining that the community is being driven away

- responding to community members adding a *friendly* and cheerful
  comment by pearl clutching about how the community is being driven
  away

- engaging in a multi-year campaign to pressure open source developers
  into feeling guilty about not spending "enough" time, culminating in
  getting maintainer access to an xkcd 2347 "Nebraska" compliant project
  for purposes of inserting a backdoor

- unwittingly being a member of a grassroots support base for the Jia
  Tans of the world by normalizing the relevant behavior


-- 
Eli Schwartz

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 18399 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2024-05-30 22:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-28  6:24 [gentoo-dev] Imminent Python 3.12 switch reminder Michał Górny
2024-05-29  9:30 ` Martin Dummer
2024-05-30  9:34   ` Florian Schmaus
2024-05-30 15:09     ` orbea
2024-05-30 15:54       ` Michał Górny
2024-05-30 15:56         ` orbea
2024-05-30 16:00           ` Jaco Kroon
2024-05-30 16:00           ` Michał Górny
2024-05-30 22:11       ` Eli Schwartz [this message]
2024-05-31  0:21   ` Sam James

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=9f979845-322e-4f22-b0a1-d5822d4f477e@gmail.com \
    --to=eschwartz93@gmail.com \
    --cc=gentoo-dev@lists.gentoo.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