License
-
-
You also need to include a license header at the top of every source code file.
I'm unclear about what this means.
What is a license header?
Do I need to edit each file in the source code to contain one, or do I need to add one to each folder in the source code? -
You also need to include a license header at the top of every source code file.
I'm unclear about what this means.
What is a license header?
Do I need to edit each file in the source code to contain one, or do I need to add one to each folder in the source code?its a piece of text (a comment) asserting that the code is open source and which open source license it uses and what the copyrights are.
I suggest you go to one of the open source forums and ask these questions there, though David IS an expert on this stuff..
-
@Lindon Good point. Do you have an open source forum that you can recommend?
-
@TNTHM maybe start with opensopurce.org and go from there?
HISE Development for hire.
www.channelrobot.com -
@Lindon Thank you. I appreciate it.
-
@Lindon would help if I spelt it correctly...
-
@TNTHM
Yes, you add the header at the top of every non-trivial source file. Non-trivial generally means the code in the file does something, if it's just pulling in other files or just declaring variables then you don't really need to put a notice there, but you can if you want. If you don't add license notices then the files fall under standard copyright which means users can't do anything with them and this violates the GNU GPL. It's not enough to include a generic license document because another developer may only use one or two of your source files in their project and then the license will become separate from the source code.If you take a look at the HISE source code, or any of the code in my repos you'll see headers.
And again if you take a look at the license and FAQ this is all explained. For info about license headers check the section titled "How to Apply These Terms to Your New Programs".
-
@d-healey I have been looking at headers for the files in hise and I understand now what you mean. I notice that in the header it says:
Commercial licenses for using HISE in an closed source project are available on request. Please visit the project's website to get more information about commercial licensing:
-
HISE is based on the JUCE library,
-
which must be separately licensed for closed source applications:
Are we allowed to mention the same thing with respect to our software built in hise? Can we have a clause in the header that says something to the tune of:
Commercial licenses for using [plugin name] in a closed source project are available. Email us for more information. You will also need a commercial license from Hise. You will also need a commercial license from Juce.
-
@TNTHM If it's your code, you can license it how you like.
