So what to do with html5-notifier-plugin?

[Gavin Mogan]

:wave: hey ya'll

I have this plugin, one of the first I adopted, that hasn't worked for a couple years now. The APIs changed and you couldn't create popups the same anymore. I did convert it to html 5 notifications, which required https, and I decided to switch it to the SSE library instead of polling.

But as I got closer to releasing it, the less comfortable I was with the new dependency, especially since the library isn't really used outside of blueocean (see https://plugins.jenkins.io/sse-gateway/#dependencies).

Then it broke for real with tables-to-div, and nobody really complained. The one person that did decided they rather uninstall than help test a new version.

Tonight I got curious, and tried it again. Somewhere along the lines the javascript broke, but updating it to see-gateway 1.26 seemed to fix it.

So question for everyone, considering its been very broken for a while, is it better to somehow depreciate the plugin, and archive it? Do the new release with sse-gateway dependancy? Leave the PR open and make it adopt-this-plugin? Some combo of things?

Gavin

[Mark Waite]

For me, I'd rather have your help on other plugins or in other areas than have you bring back a plugin that has less than 1200 installations and a steadily decreasing installation count.

There are plugins that need conversion work to use the new UI (like the git plugin with its groovy forms) and there are high volume plugins up for adoption that would benefit from your skills.

No objections if you decide to bring it back, but I'd rather have your help on areas that help more users.

Mark Waite

 

Gavin