I’ve already built and released a plugin called Discourse Workflow
This may cause confusion on Meta and this looks like a pull request to core, so users of my plugin will face two very similar entries in Admin Plugins which apparently do different things.
Thanks!
Im sorry but naming will stay. I would recommend that you don’t use “Discourse X” for your non official plugins, that would avoid a lot of clashes. Use your own namespace “merefield-discourse-workflows”.
discourse- denotes the platform and I’m already namespaced with merefield, so I will continue to use the same repo name format all plugin developers have used here for years.
However, there may be an opportunity here to differentiate whilst making the label even more appropriate.
In the meantime, thanks in advance for the extra traffic 
It’s not like you can install this on another platform.
that doesnt make it a good choice, just because many people did it
Im just telling you we can’t name our products based on any of the hundreds themes/plugins in the wild, that seems easy to understand. So really adopting a different name scheme seems the smart choice for you 
Of course it is a good choice!
Yes that’s why they are prefixed by … discourse- !
Even if you don’t read many of the topics here, a simple search would have revealed the existence of and very much significant ongoing and recent work on this plugin.
I am now faced with potentially not only rebranding this plugin, but also renaming copy, routes, classes, tables etc.
Perhaps my code tools will make that easier, but thank you anyway for the extra and otherwise unnecessary work!
To keep this professional that is my last comment on the matter.
My first comment was : Im sorry.
Im just not renaming, and you are free to keep it that way, not much more I can say/do.
One thing I could do is move it to workflows and not discourse-workflows as it’s a core plugin. It’s a minor thing, but I can do that.
