Repository navigation
Proposal: a plugin exception on ocs_plugin_api so commercial plugins can stay closed source #1852
jperna7254
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi @HakanSeven12, and everyone working on the plugin API,
I built GenMate, a commercial electrical-design plugin for AutoCAD. It places devices, draws circuits, and calculates batteries and voltage drop. We're looking for a second CAD host, and Open CAD Studio is the most promising option we've found. The pace of development, the out-of-process plugin design and the headless automation (--serve, save_verified) all stand out.
The blocker is licensing. Plugins compile in ocs_plugin_api, which is GPL-3.0-only. As I read it, that means any plugin we distribute must also be GPL. Storm Sewer handles this by staying open and selling a Pro key, which is a fair model. For us, though, the design logic in the plugin is the product, so we can't publish it.
The proposal: add an additional permission under GPL-3.0 section 7 to ocs_plugin_api. It would let a plugin that talks to OCS only through the plugin API keep its own license. Everything else stays fully GPL: OCS itself, the API crate, and any changes anyone makes to them. GCC's runtime library exception is the model I have in mind. Plugins already run in their own process and communicate over IPC, so this would make the license match a separation the architecture already has.
As far as I can tell from the history, the exception would need agreement from everyone who has contributed to the crate: @HakanSeven12, @felixriestra, @schoeller, @ramox81, @KarimJerbi and @yztink.
What we'd contribute. We'd want to put work back into the plugin interface regardless. These would also benefit every other plugin:
If an exception isn't wanted, that's completely understandable.
Thanks for building this, and I'm happy to continue here or privately, whichever you prefer.
All reactions