From 146ab05c76adb8158ad06a0fc2fa434d70f107a3 Mon Sep 17 00:00:00 2001 From: ptrcnull Date: Sun, 21 Jan 2024 23:42:09 +0100 Subject: [PATCH] CODINGSTYLE.md: make maintainer/contributor comment policy more lax in practice this isn't followed very thoroughly, so might as well relax the rules a little bit --- CODINGSTYLE.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/CODINGSTYLE.md b/CODINGSTYLE.md index 10641776432..505634d7c4a 100644 --- a/CODINGSTYLE.md +++ b/CODINGSTYLE.md @@ -133,7 +133,7 @@ APKBUILDs. ### Contributor Comment -* All APKBUILDs begin with one or more contributor comments (one per +* All APKBUILDs may begin with one or more contributor comments (one per line) containing a valid [RFC 5322][RFC 5322] address. For example, `# Contributor: Max Mustermann `. @@ -142,8 +142,9 @@ APKBUILDs. * All APKBUILDs contain exactly one maintainer comment containing a valid RFC 5322 address. For example, `# Maintainer: Max Mustermann `. -* In addition to a Maintainer Comment a Contributor Comment must be - present for said Maintainer. +* The Maintainer comment should immediately follow the Contributor comment(s). +* In the case of package being abandoned, the comment should still be present, + but left empty: `# Maintainer:`. ## Metadata Variables