From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: pounce: update to 2.5.
Date: Sat, 25 Sep 2021 15:04:21 +0200 [thread overview]
Message-ID: <20210925130421.4PwDo8FSQx0k8LLAdRU3eG7r-ss53I6FM6qvrPiZyO0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33110@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1460 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/33110#issuecomment-927118466
Comment:
1. Answering questions and fixing tests bolsters confidence that you are willing to spend more than 3 seconds firing a shell script to do an update. (Many of your PRs receive no response to maintainers' comments about issues with your contributions.)
2. Addressing the questions shows at least a baseline level of commitment to adhere to some contributor standards. It also tells us whether the update is actively used by the contributor, which helps inspire confidence that obvious defects in the update are more likely to have been caught. You can tell us now that "I only update things I use extensively", but none of us keep a checklist where we can note for all time "@ailiop-git is OK, we know he regularly uses the packages he updates". Do us a favor and remind us, since we tend to go through hundreds or thousands of these PRs from hundreds of different people.
Both tests and PR responsiveness become more important if updates cause breakage and need urgent action. We are less concerned about running the latest version than we are about running versions that aren't fundamentally broken. Your historical inattentiveness to issues within your PRs as well as your now combative response and "CBA" attitude do not inspire confidence that you will be available to fix a broken update should the need arise.
next prev parent reply other threads:[~2021-09-25 13:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-25 10:23 [PR PATCH] " ailiop-git
2021-09-25 10:58 ` paper42
2021-09-25 11:00 ` ailiop-git
2021-09-25 11:06 ` paper42
2021-09-25 11:09 ` ailiop-git
2021-09-25 11:25 ` paper42
2021-09-25 11:27 ` Johnnynator
2021-09-25 11:41 ` ailiop-git
2021-09-25 11:58 ` ahesford
2021-09-25 12:03 ` paper42
2021-09-25 12:14 ` ailiop-git
2021-09-25 13:04 ` ahesford [this message]
2021-09-27 11:39 ` [PR PATCH] [Merged]: " paper42
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=20210925130421.4PwDo8FSQx0k8LLAdRU3eG7r-ss53I6FM6qvrPiZyO0@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).