From: mhmdanas <mhmdanas@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 16:44:52 +0200 [thread overview]
Message-ID: <20230724144452.oQZjYjCvKwXX2xNx1gntjQUT4WmRAUKuHNvv-hZPo1A@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: 672 bytes --]
New review comment by mhmdanas on void-packages repository
https://github.com/void-linux/void-packages/pull/45207#discussion_r1272367559
Comment:
My take:
```suggestion
If a template is orphaned (maintained by `orphan@voidlinux.org`) or the current maintainer has not made contributions to Void in at least a year, the template can be orphaned or adopted by someone else. To ensure a template gets the care it needs, users wishing to adopt a template should be familiar with the package and have an established history of contributions to Void. Those who have contributed several updates, especially to the template in question, are good candidates for adoption.
```
next prev parent reply other threads:[~2023-07-24 14:44 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
2023-07-24 10:09 ` 0x5c
2023-07-24 14:13 ` ahesford
2023-07-24 14:44 ` mhmdanas [this message]
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=20230724144452.oQZjYjCvKwXX2xNx1gntjQUT4WmRAUKuHNvv-hZPo1A@z \
--to=mhmdanas@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).