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
This commit is contained in:
ptrcnull 2024-01-21 23:42:09 +01:00 committed by Natanael Copa
parent 1f7d7bb3ee
commit 146ab05c76

View file

@ -133,7 +133,7 @@ APKBUILDs.
### Contributor Comment ### 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, line) containing a valid [RFC 5322][RFC 5322] address. For example,
`# Contributor: Max Mustermann <max@example.org>`. `# Contributor: Max Mustermann <max@example.org>`.
@ -142,8 +142,9 @@ APKBUILDs.
* All APKBUILDs contain exactly one maintainer comment containing a * All APKBUILDs contain exactly one maintainer comment containing a
valid RFC 5322 address. For example, `# Maintainer: Max Mustermann valid RFC 5322 address. For example, `# Maintainer: Max Mustermann
<max@example.org>`. <max@example.org>`.
* In addition to a Maintainer Comment a Contributor Comment must be * The Maintainer comment should immediately follow the Contributor comment(s).
present for said Maintainer. * In the case of package being abandoned, the comment should still be present,
but left empty: `# Maintainer:`.
## Metadata Variables ## Metadata Variables