For clarification purposes, the monitoring-plugins project team has essentially forked the project. Nagios Enterprises owns the nagios-plugins project. The monitoring-plugins team changed the name and location of the repo. Nagios Enterprises has rebased with a new team using the same urls and repo locations the project has always used.
Further evidence of the fork can be found on the git repos for the monitoring-plugins site:
My apologies for any disruption this has caused. It is my opinion that no action needs to be taken at the moment. When a new release from either project is ready, they should end up in their respective packages: nagios-plugins should remain nagios-plugins, while monitoring-plugins should be packaged under a different name (monitoring-plugins perhaps?).
For clarification purposes, the monitoring-plugins project team has essentially forked the project. Nagios Enterprises owns the nagios-plugins project. The monitoring-plugins team changed the name and location of the repo. Nagios Enterprises has rebased with a new team using the same urls and repo locations the project has always used.
Further evidence of the fork can be found on the git repos for the monitoring-plugins site:
https:/ /www.monitoring -plugins. org/repositorie s/site/ diff/web/ input/doc/ faq/control. md?id=58af77e91 9ee68d1cba1b5dc e3e745003d7d6d6 7
My apologies for any disruption this has caused. It is my opinion that no action needs to be taken at the moment. When a new release from either project is ready, they should end up in their respective packages: nagios-plugins should remain nagios-plugins, while monitoring-plugins should be packaged under a different name (monitoring-plugins perhaps?).