From 4a6e353398705289813f11964f85ba86aa643f29 Mon Sep 17 00:00:00 2001 From: Joshua Strobl Date: Thu, 23 Feb 2017 00:00:21 +0200 Subject: [PATCH] See about fixing nested list items on Package Inclusion Policy doc. --- packaging/package-inclusion-policy/en.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/packaging/package-inclusion-policy/en.md b/packaging/package-inclusion-policy/en.md index ea0d7b2..30b1461 100644 --- a/packaging/package-inclusion-policy/en.md +++ b/packaging/package-inclusion-policy/en.md @@ -13,8 +13,8 @@ This policy sets forth the criteria for a package to be accepted for inclusion i 2-Distro Rule. - Projects with no tags/tarballs which lack traction, may be frozen until a suitable release is made. Tagging releases is an indicator for good release engineering practices. - Typically, we prefer **stable** tagged releases. However, this may be waived if: - - The software has significant traction (i.e. prerelease) - - A bug fix only exists beyond the latest stable release for a git source + - The software has significant traction (i.e. prerelease) + - A bug fix only exists beyond the latest stable release for a git source - Value Add: - A web wrapper which **adds value**, such as Discord, with the global push-to-talk shortcut, is eligible for inclusion. - A web page wrapper, that adds **no further value** other than “convenient desktop shortcut” or “tray icon”, is **NOT** eligible for inclusion. Web browsers already support desktop notifications.