From b36c25f3427984e0c8ea46078e9bbfac27e8dd0f Mon Sep 17 00:00:00 2001 From: Jeff Gehlbach Date: Tue, 30 Apr 2024 12:12:58 -0400 Subject: [PATCH] Updated Plugin Certification Program (markdown) --- Plugin-Certification-Program.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Plugin-Certification-Program.md b/Plugin-Certification-Program.md index cf189d4..869549f 100644 --- a/Plugin-Certification-Program.md +++ b/Plugin-Certification-Program.md @@ -31,6 +31,8 @@ By investing in a catalog where all plugin maintainers can list their creations, #### License To qualify for certification, a plugin must be available under an [OSI-approved open-source license](https://opensource.org/licenses/). NetBox plugins tend to import classes from the `netbox.api` and `netbox.plugins` namespaces, making a license that is compatible with the Apache License version 2.0 a practical requirement. +A copy of the plugin's license must be included at the top level of the plugin's source repository, in a file named `LICENSE.md`, `LICENSE.txt`, or `LICENSE`. The same license must be designated in the plugin's PyPI package entry. + Among licenses characterized by OSI as “popular / strong community”, the practical choices are, in rough order of recent popularity: - [MIT License](https://opensource.org/license/mit/)