Selling a HISE-based Plugin under GPLv3 – Compliance Questions
-
Hi everyone,
I am planning to release a plugin created with HISE under the GPLv3 license, and I also intend to sell it commercially. I want to make sure I fully comply with the GPL requirements.
My plan is to export my HISE project (including the .hip file, scripts, images, presets, and any necessary assets) and upload everything to a public GitHub repository, along with a GPLv3 LICENSE file.
Would this be enough to satisfy the GPL conditions, even if I am selling the compiled plugin?
Is there anything else I need to include or prepare when releasing a paid product based on HISE under GPL?
Thanks a lot for your help and clarification! -
@voxuer1 said in Selling a HISE-based Plugin under GPLv3 – Compliance Questions:
Would this be enough to satisfy the GPL conditions, even if I am selling the compiled plugin?
I wouldn't upload the .hip because it's not text based and can't be tracked by git. Upload the .xml instead.
The basic rule is that anyone you provide the binary (compiled plugin) to must also get access to the "source code". Source code in our case is basically the HISE project, whatever is required in order to rebuild the plugin as provided by you.
-
@d-healey ok, thank you, that helps
