Comment 75 for bug 1273484

(In reply to J Chapin from comment #63)
> To me, it seems obvious that the nagios-plugins should point to
> monitor-plugins. Since the code for each project started out a 1:1 copy, the
> *only* thing that both matters, and separates the two projects is the
> developers. Luckily, that makes it easy, since *all* the developers appear
> to be working on monitor-plugins, it's clear, to me, at least, that
> nagios-plugins is a fork -- and making a bad faith effort to deliberately
> confuse the user base.

This is clearly not true, everyone is missing the point that Nagios Enterprises owned the nagios-plugins project from the beginning, and had a team in place to manage it.

That team changed, but the project is still owned by Nagios Enterprises. This is even clearly represented by the following change made to the monitoring plugin's site on 2014-01-14 as depicted at the following URL:

You can see on the left (before they made the change), it clearly stated:
Nagios Enterprises owns the Nagios Plugins project, hence the
domain names of the site belong to Nagios Enterprises. However, the Nagios
Plugins Development Team are responsible for the running of the
project. This means that decisions about the web site and the development of
code related to the project are handled independently by the team.

Nagios Enterprises owns the Nagios Plugins project, and the owner of the project gets to choose who is on the team.

This is how it should be, and I would expect the community to understand that it is Nagios Enterprises responsibility as the project owner to take appropriate actions if the team is not acting in the best interest of the project, which they did.

Let me put this in different terms, removing Nagios, with an analogy;


If you owned a project that extended the capabilities, of the programming language Python to add additional functionality. You created it, nurtured it, and then let a team of developers maintain it because they offered to, and at the time seemed fully capable.

Now, some time passes, and you come to realize that, the team you had in place, wasn't going down the path you had intended, starting to divert people to not use Python (which was what your project was all about, extending Python), but instead they were promoting the use of other PHP, Ruby, Java, etc.

When you ask the team to make the appropriate changes, they refuse. Additionally, you realize, that they are using a domain they registered 10 months earlier, with a strikingly similar name to your project.

As the project owner, what would you do?

I would change the team, get the project back on the intended path, so all of the people who rely on the project get what they expect when they download the project/package.