License

[d.healey]

If you are releasing under the GNU GPL then there is no fee to pay. For anything else you'll need to talk to Christoph directly, he's a busy guy so you'll just have to wait for a response.

[Lindon]

-- yeah @Christoph-Hart is actually a hard guy to give money to...

[Christoph Hart]

@Christoph-Hart is actually a hard guy to give money to...

Actually we have a proper license agreement and a Fastspring account for the payment already in place, but I am waiting for 3.0 before sending it out to the few developers who use HISE in a commercial product, kind of gives me the incentive to speed up things :)

[ustk]

@Christoph-Hart So your motivation can count on me too ;)

[ulrik]

@Christoph-Hart Nice, I'm almost there :)

[Win Conway]

@Christoph-Hart said in License:

@Christoph-Hart is actually a hard guy to give money to...

Actually we have a proper license agreement and a Fastspring account for the payment already in place, but I am waiting for 3.0 before sending it out to the few developers who use HISE in a commercial product, kind of gives me the incentive to speed up things :)

This is great news, I have had to concentrate on other projects, but will be back on learning HISE soon.

[A Former User]

How would this work for free products with no licence but you don’t wish to release the source code?

[d.healey]

@danial If you're not releasing under the GNU GPL then you'll need to discuss licensing with Christoph.

[A Former User]

@d-healey Yes I imagined it would be considered commercial...cheers!

[d.healey]

@danial Proprietary, not commercial :)

[TNTHM]

@d-healey How does proprietary differ from commercial?

[d.healey]

@TNTHM Proprietary means closed source. Commercial means you intend to make money from it.

The HISE proprietary license is also a commercial license, not because it gives you permission to sell your plugin (you already had that with the GNU GPL) but because you have to give money to Christoph.

[TNTHM]

@d-healey when releasing a plugin under GNU GPL how do you provide the source code to the customer?

[d.healey]

@TNTHM I put mine on github and give them a link.

[TNTHM]

@d-healey that makes sense. What is the source code for a compiled plugin? Or another way to say it is: where can I find the source code for my compiled plugin?

[d.healey]

It's your HISE project folder, you probably don't want to put the binaries folder on github though because it's quite large, so add it to .gitignore.

[TNTHM]

@d-healey are compression algorithms allowed under GNU GPL. For instance, if I zip the file to make it smaller is that within the scope of the license?

Also is it required that you put all versions of xml and archives up, or is the build xml and archive sufficient?

[d.healey]

@TNTHM You need to include everything the user needs to recreate the plugin you are giving them. I don't think there are any specific rules about compression, just make sure the compression format isn't proprietary, so zip should be fine but rar wouldn't be.

[TNTHM]

@d-healey Then is it also necessary to include the hise source code along with all gems and instructions for compiling and installing? That seems like overkill but I just want to be sure I understand the full scope of what is required.

[d.healey]

@TNTHM No you don't need to include HISE because that's not part of your project. We don't need to upload all of the build tools. If we're going to upload literally EVERYTHING that is needed then you're going to want to upload an entire OS too.