# Potential Upcoming Plugin Name Clash - "Workflow" **URL:** \ **Category:** Development\ **Created:** [May 13, 2026, 10:40am UTC](https://meta.discourse.org/t/potential-upcoming-plugin-name-clash-workflow/402854 "2026-05-13T10:40:47Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)\ **Post date:** [May 13, 2026, 10:40am UTC](https://meta.discourse.org/t/potential-upcoming-plugin-name-clash-workflow/402854/1 "2026-05-13T10:40:48Z")
[https://github.com/discourse/discourse/pull/39704](https://github.com/discourse/discourse/pull/39704) I’ve already built and released a plugin called Discourse Workflow > [@Process Manager left\_right\_arrow - formerly "Discourse Workflow"](https://meta.discourse.org/t/discourse-workflow/347110): > > information_sourceSummary A process management plugin for Discourse that moves work through configurable steps with actions, list filters, charts, swim-lane views, and Kanban boards.hammer_and_wrench[Repository Link](https://github.com/merefield/discourse-process-manager)[https://github.com/merefield/discourse-process-manager](https://github.com/merefield/discourse-process-manager)open_bookInstall Guide [How to install plugins in Discourse](https://meta.discourse.org/t/install-plugins-in-discourse/19157) Enjoying this plugin? Please star it on [GitHub](https://github.com/merefield/discourse-workflow)! pray 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! ---
**Author:** ![j.jaffeux](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/j.jaffeux/32/60297_2.png) [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)\ **Post date:** [May 16, 2026, 4:59pm UTC](https://meta.discourse.org/t/potential-upcoming-plugin-name-clash-workflow/402854/4 "2026-05-16T16:59:08Z")
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”. ---
**Author:** ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)\ **Post date:** [May 16, 2026, 8:21pm UTC](https://meta.discourse.org/t/potential-upcoming-plugin-name-clash-workflow/402854/5 "2026-05-16T20:21:50Z")
`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 😉 ---
**Author:** ![j.jaffeux](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/j.jaffeux/32/60297_2.png) [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)\ **Post date:** [May 17, 2026, 8:28am UTC](https://meta.discourse.org/t/potential-upcoming-plugin-name-clash-workflow/402854/7 "2026-05-17T08:28:33Z")
> [@merefield](#): > > `discourse-` denotes the platform It’s not like you can install this on another platform. > [@merefield](#): > > all plugin developers have used here for years that doesnt make it a good choice, just because many people did it > [@merefield](#): > > 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 😉 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 🤷‍♂️ ---
**Author:** ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)\ **Post date:** [May 17, 2026, 9:38am UTC](https://meta.discourse.org/t/potential-upcoming-plugin-name-clash-workflow/402854/9 "2026-05-17T09:38:02Z")
> [@j.jaffeux](#): > > that doesnt make it a good choice, just because many people did it Of course it is a good choice! > [@j.jaffeux](#): > > It’s not like you can install this on another platform. 👍 Yes that’s why they are prefixed by … `discourse-` ! > [@j.jaffeux](#): > > we can’t name our products based on any of the hundreds themes/plugins in the wild 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. ![image](https://global.discourse-cdn.com/meta/original/4X/7/4/0/740ba9934b0ab527fe6addd6aa2bd76feffa7c24.png) 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. ---
**Author:** ![j.jaffeux](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/j.jaffeux/32/60297_2.png) [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)\ **Post date:** [May 17, 2026, 9:53am UTC](https://meta.discourse.org/t/potential-upcoming-plugin-name-clash-workflow/402854/10 "2026-05-17T09:53:11Z")
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. ---
**Author:** ![j.jaffeux](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/j.jaffeux/32/60297_2.png) [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)\ **Post date:** [May 17, 2026, 9:53am UTC](https://meta.discourse.org/t/potential-upcoming-plugin-name-clash-workflow/402854/11 "2026-05-17T09:53:15Z")
---
**Author:** ![j.jaffeux](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/j.jaffeux/32/60297_2.png) [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)\ **Post date:** [May 17, 2026, 3:55pm UTC](https://meta.discourse.org/t/potential-upcoming-plugin-name-clash-workflow/402854/12 "2026-05-17T15:55:45Z")
---
**Author:** ![j.jaffeux](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/j.jaffeux/32/60297_2.png) [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)\ **Post date:** [May 17, 2026, 4:00pm UTC](https://meta.discourse.org/t/potential-upcoming-plugin-name-clash-workflow/402854/14 "2026-05-17T16:00:28Z")
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.