From ddba59501415058b2fc77275f5c353983a9e73bc Mon Sep 17 00:00:00 2001 From: Matt Holt Date: Mon, 18 Jul 2016 17:07:54 -0600 Subject: [PATCH] Updated Publishing a Plugin to the Download Page (markdown) --- Publishing-a-Plugin-to-the-Download-Page.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/Publishing-a-Plugin-to-the-Download-Page.md b/Publishing-a-Plugin-to-the-Download-Page.md index b8b092a..afade5c 100644 --- a/Publishing-a-Plugin-to-the-Download-Page.md +++ b/Publishing-a-Plugin-to-the-Download-Page.md @@ -27,16 +27,20 @@ To add your package to the plugin registry, it must meet the following requireme - Packages that use or rely on free third-party services (which are only free) will be decided on a case-by-case basis. -- Packages that integrate with commercial services (including services with free plans/trials) may be decided based on sponsorship agreements. +- Packages that integrate with commercial services (including services with free plans/trials) may be decided based on sponsorship. - The functionality of a package must be unique among other registered packages and the Caddy core. This is not an app store. We follow the "improve or remove" philosophy. -- The package must not use cgo and must be cross-platform compatible. +- The package and its dependencies must not invoke cgo. + +- The package must compile cross-platform. - Package must be under test using the standard Go `testing` package rather than third-party testing dependencies. Tests should not take more than a few seconds to run. - The project license must be compatible with the main Caddy project license. +- Distribution from the Caddy website does not imply endorsement by the Caddy project or its author, maintainers, or contributors. Users assume all risks and you are responsible for updates, security, and maintaining your own code. + ### 2. Documentation