# Choosing a License for Examples and Libraries

**URL:** <https://forum.juce.com/t/choosing-a-license-for-examples-and-libraries/35583>\
**Category:** Commercial / Licences\
**Created:** [October 7, 2019, 2:11pm UTC](https://forum.juce.com/t/choosing-a-license-for-examples-and-libraries/35583 "2019-10-07T14:11:55Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![arunoda](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/arunoda/32/7194_2.png) [@arunoda](https://forum.juce.com/u/arunoda)\
**Post date:** [October 7, 2019, 2:11pm UTC](https://forum.juce.com/t/choosing-a-license-for-examples-and-libraries/35583/1 "2019-10-07T14:11:55Z")

</div>

> I searched the forum and I couldn’t find a direct answer for this.  
> If there’s an older discussion, share that with me please.

Recently I started to learn audio programming(& DSP) in parallel with a local Audio Eng. course.  
In the coming months, I’d like to share my experience with [Blog posts](https://iohacks.io/) and [some projects](https://github.com/iohacks) on GitHub.

I’d like to use MIT (or similar) license for those examples. In those code, I’ll use some Juce classes and methods.  
Since Juce is not opensource, I wonder that’s possible or not?

I can submit [my examples](https://github.com/iohacks/JuceAutoParams) without any Juce library code.  
(So, In order to use these examples, someone has to download and subscribe to Juce.)

---

<div class="post-metadata">

**Author:** ![mcmartin](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/mcmartin/32/7432_2.png) [@mcmartin](https://forum.juce.com/u/mcmartin)\
**Post date:** [October 7, 2019, 6:16pm UTC](https://forum.juce.com/t/choosing-a-license-for-examples-and-libraries/35583/2 "2019-10-07T18:16:32Z")

</div>

> [@arunoda](#):
>
> Since Juce is not opensource, I wonder that’s possible or not?

There is a main public repository containing all the JUCE source code and its history maintained by ROLI here: [GitHub - juce-framework/JUCE: JUCE is an open-source cross-platform C++ application framework for desktop and mobile applications, including VST, VST3, AU, AUv3, LV2 and AAX audio plug-ins.](https://github.com/WeAreROLI/JUCE). Then there are [hundreds of forks](https://github.com/WeAreROLI/JUCE/network/members). Finally, the JUCE code is also licensed under the GPLv3.

JUCE is open-source!

---

<div class="post-metadata">

**Author:** ![bgporter](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/bgporter/32/12710_2.png) [@bgporter](https://forum.juce.com/u/bgporter)\
**Post date:** [October 7, 2019, 6:28pm UTC](https://forum.juce.com/t/choosing-a-license-for-examples-and-libraries/35583/3 "2019-10-07T18:28:58Z")

</div>

You may find this page helpful – there’s some coverage of more permissive licenses like MIT and how they are compatible with GPL-licensed code:

> <https://softwareengineering.stackexchange.com/questions/204410/how-are-gpl-compatible-licenses-like-mit-usable-in-gpl-programs-without-being-su>

(I’m not a lawyer, but I did a lot of research on this topic when making the same decision about releasing code for blog posts, etc. and decided that the MIT license was the best fit for us.)

---

<div class="post-metadata">

**Author:** ![arunoda](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/arunoda/32/7194_2.png) [@arunoda](https://forum.juce.com/u/arunoda)\
**Post date:** [October 7, 2019, 11:21pm UTC](https://forum.juce.com/t/choosing-a-license-for-examples-and-libraries/35583/4 "2019-10-07T23:21:10Z")

</div>

Thanks I didn’t know about this.

---

<div class="post-metadata">

**Author:** ![arunoda](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/arunoda/32/7194_2.png) [@arunoda](https://forum.juce.com/u/arunoda)\
**Post date:** [October 7, 2019, 11:24pm UTC](https://forum.juce.com/t/choosing-a-license-for-examples-and-libraries/35583/5 "2019-10-07T23:24:02Z")

</div>

Thanks @bgporter.  
I’m bit confused now with this:

> Once your business hits the Revenue Limit for your JUCE license, you will either have to upgrade your JUCE license or release your Applications under the [GNU General Public License v.3](https://www.gnu.org/licenses/gpl-3.0.en.html), which means, among other things, that your code can be freely copied and distributed.

Anyway, I’ll keep it as MIT for now and move on.
