Hello, Sorry for the delay in responding,
A lot has been going on including vacation, moving and the pandemic. I'm going to reply inline below. onsdag den 18. marts 2020 kl. 18.04.16 UTC+1 skrev Björn Rabenstein: > > Hello everyone, > > Two weeks later, I'd like to wrap things up here. > Thanks for all your input. > > On 04.03.20 19:45, Bjoern Rabenstein wrote: > > > > 1. Make Emil the maintainer of the current prometheus/nagios_plugins > > repository, where he can then merge in his current work in a way > > that doesn't break backwards compatibility. > > > > 2. Create a Nagios plugin repo in prometheus-community and make Emil > > the maintainer of it. > > > > 3. Leave Emil's fork where it is now and point to it from > > prometheus/nagios_plugins and from prometheus.io > > These had been the three options on the table. From the feedback I > got, there is no clearly favored option, but on the other hand, nobody > seemed to feel very strongly either. > > Therefore, let's go with the option of least change and least > friction, which is option (3). (At least in my opinion, but I'm also > the maintainer of the repo in question, so it's probably OK if I serve > as a tie breaker. :o) > > That's my ingenious two-stage plan: > > 1. Emil, once you feel that your plugin is ready for production usage, > let me know and we'll add a deprecation notice to > prometheus/nagios_plugins and link your repo from the integrations > list on https://prometheus.io . > > We are currently running it in production at Magenta ApS, so I am up for it, assuming you feel ok with it. Whatever issues may arise we'll deal with as they arise. > 2. Once Emil's plugin has run for a while in the wild without > problems, we'll set up a GitHub redirect. (Implementation detail: > AFAICS, you cannot redirect to a repository that already exist. I > guess we have to hack that by deleting Emil's repo, transfering > prometheus/nagios_plugin to him, and then let him replay his > commits on top if it. Or something like that. We'll find a way.) > Optionally, if the redirect isn't feasible or Emil's plugin works > slightly differently after all, we'll keep around > prometheus/nagios_plugin for a while longer to then archive and > ultimately junkyard it (with ample of migration warning). > > This sounds good to me, I'll let you have the call for when you think this is appropriate. > That's all. Emil, I'll wait for you to tell me your plugin is > production-ready. > > -- > Björn Rabenstein > [PGP-ID] 0x851C3DA17D748D03 > [email] [email protected] <javascript:> > -- You received this message because you are subscribed to the Google Groups "Prometheus Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-developers/b4e6c30d-019b-4fcc-acdb-ef90797717a0%40googlegroups.com.
