From f4bf28773fede663cf93d98c49c5fda3b365c0de Mon Sep 17 00:00:00 2001 From: classabbyamp 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..4cbb475eaa9cf 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 +### Adopting a template + +If a template is orphaned (maintained by `orphan@voidlinux.org`) or the current `maintainer` has not contributed to +void-packages 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 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 `. 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. + ### 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: