feat: Clarify documentation on how to flag packages (fix nim-lang/packages#2809) (#2814)

Signed-off-by: penguinite <penguinite@tuta.io>
This commit is contained in:
penguinite 2024-02-10 00:15:06 +01:00 committed by GitHub
parent b03a72e7be
commit aa27ab4088
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -35,7 +35,7 @@ While we really appreciate your contribution, please follow the requirements: ot
* The URL should work, a .nimble file should be present and the package should be installable
* The package should build correctly with the latest Nim release
* The package should not contain files without a license or in breach of 3rd parties licensing
* Non-mature packages should be flagged as such, especially if they perform security-critical tasks (e.g. encryption)
* Non-mature packages should be flagged as such by opening an issue here with a good explanation on how they are non-mature, especially if they perform security-critical tasks (e.g. encryption)
* If a vulnerability is found, make a patch release against the latest stable release (or more) that fixes the issue without introducing any other change.
* Tiny libraries should be avoided where possible
* Avoid having many dependencies. Use "when defined(...)" to enable optional features.