foosel
commented
4 years ago Just wanted to quickly say: I agree that that's a problem that should be looked into, I just don't have the time at the moment for that until 1.4.0 stable is out (hopefully very early 2020).
It would definitely have to be something that's opt-in though, simply moving any plugins currently hosted on Github over to that method could have unintended side effects. And it poses the issue of giving partial control over displayed data on a domain and website I'm legally responsible for to other people, which is also something which I'm not really comfortable with yet.
I've just gone through the plugin repository to pick the plugins I'd like, and I almost missed one due to a stale description.
To install OctoPrint-SlicerSettingsTab, I need OctoPrint-SlicerSettingsParser. The description says it's only compatible with two slicers. I use Cura, not listed, so I almost didn't install this. I checked GitHub, just in case, and the description states that it now does support Cura, though an additional step is required. It's reasonable to assume a lot of Cura users would have passed this plugin by due to this stale description.
When a plugin is on GitHub, it would be useful to generate the description by copying it from GitHub during a periodic (daily?) refresh/check for updates (appreciate that not all are on GitHub, though all the ones I've looked at have been) to automatically keep the OctoPrint Plugins data up to date.