From 85e20768b6d5dde3b55dd2d27565bfe98aad37fa Mon Sep 17 00:00:00 2001 From: David Harris Date: Fri, 14 Apr 2023 17:41:33 +0100 Subject: [PATCH] docs: adds license guidance to publishing criteria (#64984) * initial commit * Update publishing-and-signing-criteria.md * typo * typo --- .../plugins/publishing-and-signing-criteria.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/docs/sources/developers/plugins/publishing-and-signing-criteria.md b/docs/sources/developers/plugins/publishing-and-signing-criteria.md index 277ba504c2f..8cc7742ea17 100644 --- a/docs/sources/developers/plugins/publishing-and-signing-criteria.md +++ b/docs/sources/developers/plugins/publishing-and-signing-criteria.md @@ -23,6 +23,19 @@ Grafana plugins must adhere to the following criteria when being reviewed for pu - Should not access the filesystem - Should not access environment variables +## Plugin licensing + +Plugins must be licensed under one of the following AGPL compliant licenses for publishing to the catalog: + +- AGPL-3.0 +- Apache-2.0 +- BSD +- GPL-3.0 +- LGPL-3.0 +- MIT + +If contributing a plugin on behalf of an organization, be sure to seek guidance from your legal team. + ## Commercial - Usage of 3rd party software or dependencies within the plugin must be licensed for the intended use. For example, using open source dependencies must be credited/licensed; embedding logos or trademarks;