1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
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"
<!--% # vim:set filetype=markdown textwidth=78 joinspaces: # %-->
|
