License
-
@Christoph-Hart So your motivation can count on me too ;)
-
@Christoph-Hart Nice, I'm almost there :)
-
@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.
-
How would this work for free products with no licence but you don’t wish to release the source code?
-
@danial If you're not releasing under the GNU GPL then you'll need to discuss licensing with Christoph.
-
@d-healey Yes I imagined it would be considered commercial...cheers!
-
@danial Proprietary, not commercial :)
-
@d-healey How does proprietary differ from commercial?
-
@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.
-
@d-healey when releasing a plugin under GNU GPL how do you provide the source code to the customer?
-
@TNTHM I put mine on github and give them a link.
-
@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?
-
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.
-
@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?
-
@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
zipshould be fine butrarwouldn't be. -
@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.
-
@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.
-
@d-healey Is it necessary to disclose that Plugin A is under the GNU GPL license. If so, is it specified where we need to disclose that information?
With regards to source code under GNU GPL:
"In order for freedoms 1 and 3 (the freedom to make changes and the freedom to publish the changed versions) to be meaningful, you need to have access to the source code of the program. Therefore, accessibility of source code is a necessary condition for free software. Obfuscated “source code” is not real source code and does not count as source code."
I do not see anywhere that specifies where source code must be offered and in what capacity. Therefore, when a customer downloads the product, it is within the parameters of the GNU GPL license to attach the source code and install it in a specific location on their computer where they can access it as they see fit. Is this correct?
-
I think you should read the license and accompanying FAQ
Is it necessary to disclose that Plugin A is under the GNU GPL license. If so, is it specified where we need to disclose that information?
See the section headed How to Apply These Terms to Your New Programs and Section 0 which says
An interactive user interface displays “Appropriate Legal Notices” to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion.
The usual place to display licenses is in the installer. The user needs to be made aware of their rights and agree to the license before they install the software. You should also add a license doc, often called COPYING to the source code root folder. You also need to include a license header at the top of every source code file.
I do not see anywhere that specifies where source code must be offered and in what capacity.
See section 6. Conveying Non-Source Forms.
-
