diff options
Diffstat (limited to 'web/input/doc/faq/fork.md')
-rw-r--r-- | web/input/doc/faq/fork.md | 62 |
1 files changed, 62 insertions, 0 deletions
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 @@ | |||
1 | title: Did you fork? | ||
2 | parent: FAQ | ||
3 | --- | ||
4 | |||
5 | # Did you fork the Nagios Plugins? | ||
6 | |||
7 | TL;DR: No. They forked us. | ||
8 | |||
9 | Long answer: | ||
10 | |||
11 | Initially, there was a Nagios Plugins project. Today, there is both a [Nagios | ||
12 | Plugins][nagios-plugins] project and a [Monitoring Plugins][monitoring-plugins] | ||
13 | project. The answer to the question of who forked whom probably isn't | ||
14 | immediately obvious, especially for those who weren't involved in the mess. | ||
15 | It'll depend on how exactly you define a "fork", and it may not be all that | ||
16 | important anyway. | ||
17 | |||
18 | However, because you asked, here's our view on the happenings. | ||
19 | |||
20 | Originally, there was a Nagios Plugins project that was maintained by us; | ||
21 | i.e., a [team][team] of volunteers not affiliated with [Nagios | ||
22 | Enterprises][enterprises]. In 2011, we transferred the `nagios-plugins.org` | ||
23 | domain to Nagios Enterprises on their request. This transfer was coupled with | ||
24 | an [agreement][agreement] that we would continue to run the project | ||
25 | independently. Early in 2014, Nagios Enterprises copied most of our web site | ||
26 | and changed the DNS records to point to their web space instead, which then | ||
27 | served a slightly modified version of our site including the tarballs we | ||
28 | created. This was done without prior notice. Presumably, their | ||
29 | [reasoning][reasoning] for this move was that they weren't happy with us | ||
30 | [mentioning Icinga and Shinken][mentioning] on our home page. | ||
31 | |||
32 | So, today there are two projects: | ||
33 | |||
34 | One driven by the team that lost its domain, but that did the actual | ||
35 | maintenance work in the past, and that continues to maintain the same project | ||
36 | with the same infrastructure (e.g., the GitHub [repositories][repositories] | ||
37 | and [trackers][trackers], the [mailing lists][support], and the [automated | ||
38 | test builds][tests]) under the new name. | ||
39 | |||
40 | The other project is driven by the company that controls the domain. | ||
41 | |||
42 | So, if you ask us (as you did by definition when reading this): They clearly | ||
43 | forked us, not vice versa. We just see two differences to a "typical" fork | ||
44 | which makes this case less obvious: | ||
45 | |||
46 | 1. The project that has been forked didn't own its domain name. | ||
47 | 2. The project that performed the fork did so without showing any previous | ||
48 | development activities. | ||
49 | |||
50 | [nagios-plugins]: http://www.nagios-plugins.org/ "Nagios Plugins" | ||
51 | [monitoring-plugins]: index.html "Monitoring Plugins" | ||
52 | [team]: team.html "Monitoring Plugins Development Team" | ||
53 | [enterprises]: http://www.nagios.com/about/company "Nagios Enterprises" | ||
54 | [agreement]: news/domain-transfer.html "Domain Transfer Agreement" | ||
55 | [reasoning]: archive/devel/2014-January/009420.html "Reasoning of Nagios Enterprises" | ||
56 | [mentioning]: archive/devel/2014-January/009428.html "Response to Nagios Enterprises" | ||
57 | [repositories]: https://github.com/monitoring-plugins/repositories "GitHub Repositories" | ||
58 | [trackers]: https://github.com/monitoring-plugins/monitoring-plugins/issues "GitHub Issue Tracker" | ||
59 | [support]: support.html#mailing-lists "Mailing Lists" | ||
60 | [tests]: tests.html "Test Results" | ||
61 | |||
62 | <!--% # vim:set filetype=markdown textwidth=78 joinspaces: # %--> | ||