From aa27ab4088ef38a6dd7cb436141b4aba5ead0794 Mon Sep 17 00:00:00 2001 From: penguinite <147942000+penguinite@users.noreply.github.com> Date: Sat, 10 Feb 2024 00:15:06 +0100 Subject: [PATCH] feat: Clarify documentation on how to flag packages (fix nim-lang/packages#2809) (#2814) Signed-off-by: penguinite --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 8962906..79f4352 100644 --- a/README.md +++ b/README.md @@ -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.