From 0f0a943d5429cf8db0f7f6cc9bc2679ed9329901 Mon Sep 17 00:00:00 2001 From: Holger Weiss Date: Tue, 14 Jan 2014 22:58:44 +0100 Subject: Rename Nagios Plugins to Monitoring Plugins This is a first step of replacing the name "Nagios Plugins" with "Monitoring Plugins" where appriopriate. Some news items and FAQ entries are also created or updated. More to come. --- web/input/doc/faq/reuse.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) (limited to 'web/input/doc/faq/reuse.md') diff --git a/web/input/doc/faq/reuse.md b/web/input/doc/faq/reuse.md index 6c8e7b0..f7fe8a6 100644 --- a/web/input/doc/faq/reuse.md +++ b/web/input/doc/faq/reuse.md @@ -2,21 +2,21 @@ title: Code reuse parent: FAQ --- -# Can I use Nagios Plugins in my project? +# Can I reuse Monitoring Plugins code? Firstly, there is a distinction between a Nagios plugin and plugins from the -Nagios Plugins project. +Monitoring Plugins project. Although Nagios (the system) is licensed under the GPL, plugins are executed in their own environment, so they [do not fall][aggregation] under the "viral" aspect of the GPL. Therefore, any plugin written for use by Nagios can be under any license the copyright holder selects. -However, the plugins contained within the Nagios Plugins project are +However, the plugins contained within the Monitoring Plugins project are distributed under the [GPL][gpl]. If you distribute an application that -includes the Nagios Plugins (modified or not), you are required to distribute -a copy of the source code for the plugins under the terms of the GPL, -regardless of the licensing for the rest of the application. +includes the Monitoring Plugins (modified or not), you are required to +distribute a copy of the source code for the plugins under the terms of the +GPL, regardless of the licensing for the rest of the application. If you write a plugin which is a derivative work from code of the Nagios Plugins project, then your plugin must also be licensed under the GPL, -- cgit v1.2.3-74-g34f1