The issue of forks of official Discourse repositories still being marked as official has been raised. pfaffman discovered this when they installed a client-forked version of discourse-rss-polling, and the plugin was still marked as official. sam acknowledged it as a bug and suggested a simple fix to ensure the plugin comes from the discourse org in GitHub to be marked official. However, sam also mentioned that a more thorough solution would require additional services.
A simpler fix specific to the Docker Manager plugin was proposed, which would involve running an extra Git command to detect forked plugins. nbianca has since implemented the fork indicator in a pull request (https://github.com/discourse/docker_manager/pull/96). sam has slated this feature for the next release, which is expected within the next 6 months. The community is also welcome to contribute to the Docker Manager plugin.
A client forked discourse-rss-polling and I installed that.
But it looks like I still have the official version installed:
I’ll leave as an exercise seeing that the commit listed isn’t one in the repo. When I mouse-over the plugin, I can see that it links to the forked repo.
This caught me out recently too. The checkmark definitely misled me for a while and I did all kinds of unnecessary testing before I spotted the repo in the app.yml.
Simplest fix here is specific to the docker manager plugin. I am not sure how I feel about running an extra git command or to go hunting for git remotes on every plugin, every time we boot.
But docker manager plugin could do that extra work and put a big red icon on official plugins that appear to be forked.
I will slot for the next release, so it will happen over the next 6 months or so.
pr-welcome as well if anyone wants to fiddle with docker manager.