From: 0x5c <0x5c@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] [RFC] CONTRIBUTING.md: describe adoption/orphaning policy and procedure
Date: Mon, 24 Jul 2023 12:09:56 +0200 [thread overview]
Message-ID: <20230724100956.uI640DTHV7M3Pf-Ejg3dWZ0ZB6wykyYEk_en-8Mm6tE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45207@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 518 bytes --]
New review comment by 0x5c on void-packages repository
https://github.com/void-linux/void-packages/pull/45207#discussion_r1272035950
Comment:
The requirement of having contributed to a specific template multiple times might lock many packages in permanent maintainerless limbo, like those that very rarely get releases.
Might be best to not require more than usage of the template + an history of contribution to any packages, and recommend not adopting without doing another change like the next paragraph does.
next prev parent reply other threads:[~2023-07-24 10:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-23 15:05 [PR PATCH] " classabbyamp
2023-07-23 15:10 ` [PR REVIEW] " mhmdanas
2023-07-23 16:38 ` icp1994
2023-07-23 16:50 ` classabbyamp
2023-07-24 2:45 ` [PR REVIEW] " CameronNemo
2023-07-24 10:09 ` 0x5c [this message]
2023-07-24 10:09 ` 0x5c
2023-07-24 14:13 ` ahesford
2023-07-24 14:44 ` mhmdanas
2023-07-24 16:14 ` CameronNemo
2023-07-24 21:53 ` Vaelatern
2023-07-28 4:33 ` [PR PATCH] [Updated] " classabbyamp
2023-07-28 4:33 ` classabbyamp
2023-07-28 4:35 ` [PR PATCH] [Updated] " classabbyamp
2023-07-28 9:58 ` [PR REVIEW] " mhmdanas
2023-07-28 22:16 ` classabbyamp
2023-07-29 10:08 ` mhmdanas
2023-07-29 10:09 ` mhmdanas
2023-07-30 3:52 ` [PR PATCH] [Updated] " classabbyamp
2023-07-30 3:53 ` [PR PATCH] [Merged]: " classabbyamp
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=20230724100956.uI640DTHV7M3Pf-Ejg3dWZ0ZB6wykyYEk_en-8Mm6tE@z \
--to=0x5c@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).