Github messages for voidlinux
 help / color / mirror / Atom feed
* [PR PATCH] [RFC] CONTRIBUTING.md: describe adoption/orphaning policy and procedure
@ 2023-07-23 15:05 classabbyamp
  2023-07-23 15:10 ` [PR REVIEW] " mhmdanas
                   ` (18 more replies)
  0 siblings, 19 replies; 20+ messages in thread
From: classabbyamp @ 2023-07-23 15:05 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 486 bytes --]

There is a new 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: 1798 bytes --]

From 9332ffcddd8270bf51f2681360860ebdf9cfe7d0 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 | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index a8f58bbb37445..52ca1b18b48ff 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -82,6 +82,25 @@ 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 in a long
+time (over a year), template maintainership can be adopted by someone else. To ensure a template gets the care it needs,
+template adopters should use the package in question and have a history of contributing changes to that template (updating
+the template several times, for example).
+
+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: update to 1.2.3, orphan.
+
 ### 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:

^ permalink raw reply	[flat|nested] 20+ messages in thread
end of thread, other threads:[~2023-07-30  3:53 UTC | newest]

Thread overview: 20+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-07-23 15:05 [PR PATCH] [RFC] CONTRIBUTING.md: describe adoption/orphaning policy and procedure 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 ` [PR PATCH] [Updated] " classabbyamp
2023-07-30  3:53 ` [PR PATCH] [Merged]: " classabbyamp

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).