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/fork.md | 62 +++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 62 insertions(+) create mode 100644 web/input/doc/faq/fork.md (limited to 'web/input/doc/faq/fork.md') diff --git a/web/input/doc/faq/fork.md b/web/input/doc/faq/fork.md new file mode 100644 index 0000000..5057b80 --- /dev/null +++ b/web/input/doc/faq/fork.md @@ -0,0 +1,62 @@ +title: Did you fork? +parent: FAQ +--- + +# Did you fork the Nagios Plugins? + +TL;DR: No. They forked us. + +Long answer: + +Initially, there was a Nagios Plugins project. Today, there is both a [Nagios +Plugins][nagios-plugins] project and a [Monitoring Plugins][monitoring-plugins] +project. The answer to the question of who forked whom probably isn't +immediately obvious, especially for those who weren't involved in the mess. +It'll depend on how exactly you define a "fork", and it may not be all that +important anyway. + +However, because you asked, here's our view on the happenings. + +Originally, there was a Nagios Plugins project that was maintained by us; +i.e., a [team][team] of volunteers not affiliated with [Nagios +Enterprises][enterprises]. In 2011, we transferred the `nagios-plugins.org` +domain to Nagios Enterprises on their request. This transfer was coupled with +an [agreement][agreement] that we would continue to run the project +independently. Early in 2014, Nagios Enterprises copied most of our web site +and changed the DNS records to point to their web space instead, which then +served a slightly modified version of our site including the tarballs we +created. This was done without prior notice. Presumably, their +[reasoning][reasoning] for this move was that they weren't happy with us +[mentioning Icinga and Shinken][mentioning] on our home page. + +So, today there are two projects: + +One driven by the team that lost its domain, but that did the actual +maintenance work in the past, and that continues to maintain the same project +with the same infrastructure (e.g., the GitHub [repositories][repositories] +and [trackers][trackers], the [mailing lists][support], and the [automated +test builds][tests]) under the new name. + +The other project is driven by the company that controls the domain. + +So, if you ask us (as you did by definition when reading this): They clearly +forked us, not vice versa. We just see two differences to a "typical" fork +which makes this case less obvious: + +1. The project that has been forked didn't own its domain name. +2. The project that performed the fork did so without showing any previous + development activities. + +[nagios-plugins]: http://www.nagios-plugins.org/ "Nagios Plugins" +[monitoring-plugins]: index.html "Monitoring Plugins" +[team]: team.html "Monitoring Plugins Development Team" +[enterprises]: http://www.nagios.com/about/company "Nagios Enterprises" +[agreement]: news/domain-transfer.html "Domain Transfer Agreement" +[reasoning]: archive/devel/2014-January/009420.html "Reasoning of Nagios Enterprises" +[mentioning]: archive/devel/2014-January/009428.html "Response to Nagios Enterprises" +[repositories]: https://github.com/monitoring-plugins/repositories "GitHub Repositories" +[trackers]: https://github.com/monitoring-plugins/monitoring-plugins/issues "GitHub Issue Tracker" +[support]: support.html#mailing-lists "Mailing Lists" +[tests]: tests.html "Test Results" + + -- cgit v1.2.3-74-g34f1