From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] [RFC] CONTRIBUTING.md: describe adoption/orphaning policy and procedure
Date: Sun, 30 Jul 2023 05:52:56 +0200 [thread overview]
Message-ID: <20230730035256.kHpaXsAZQHhdWdWX_m7v9F8qt-iB1ylIrxYgG3YsT48@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: 491 bytes --]
There is an updated pull request by classabbyamp against master on the void-packages repository
https://github.com/classabbyamp/void-packages contrib-adopt
https://github.com/void-linux/void-packages/pull/45207
[RFC] CONTRIBUTING.md: describe adoption/orphaning policy and procedure
I think it would be good to codify some of this. Open to suggestions on everything.
@void-linux/pkg-committers
A patch file from https://github.com/void-linux/void-packages/pull/45207.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-contrib-adopt-45207.patch --]
[-- Type: text/x-diff, Size: 2017 bytes --]
From 5652d299a13a0de48fdea3e02e480ffd8e73e4a0 Mon Sep 17 00:00:00 2001
From: classabbyamp <void@placeviolette.net>
Date: Sun, 23 Jul 2023 11:03:01 -0400
Subject: [PATCH] CONTRIBUTING.md: describe adoption/orphaning policy and
procedure
---
CONTRIBUTING.md | 23 +++++++++++++++++++++++
1 file changed, 23 insertions(+)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index a8f58bbb37445..471b0ed2ddc88 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -82,6 +82,29 @@ The checksum can be updated automatically with the `xgensum` helper from the [xt
$ xgensum -i <pkgname>
+### Adopting a template
+
+If a template is orphaned (maintained by `orphan@voidlinux.org`) or the current `maintainer` has not contributed to
+Void in over a year, template maintainership can be adopted by someone else. To ensure a template gets the care it needs,
+template adopters should be familiar with the package and have an established history of contributions to Void.
+Those who have contributed several updates, especially for the template in question, are good candidates for template
+maintainership.
+
+It is best to adopt a template when making another change to it. When adopting the template, add your name or username
+and email to the `maintainer` field in the template, and mention the adoption in your commit message, for example:
+
+ libfoo: update to 1.2.3, adopt.
+
+### Orphaning a template
+
+If you no longer wish to maintain a template, you can remove yourself as maintainer by setting the `maintainer` field in
+the template to `Orphaned <orphan@voidlinux.org>`. The commit message should mention this, for example:
+
+ libfoo: orphan.
+
+It is not necessary to make other changes to the template when orphaning, and incrementing the revision (triggering a
+rebuild) is not necessary either.
+
### Committing your changes
After making your changes, please check that the package builds successfully. From the top level directory of your local copy of the `void-packages` repository, run:
next prev parent reply other threads:[~2023-07-30 3:52 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
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 ` classabbyamp [this message]
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=20230730035256.kHpaXsAZQHhdWdWX_m7v9F8qt-iB1ylIrxYgG3YsT48@z \
--to=classabbyamp@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).