charm license requirements with multi-licensed payloads

Hi folks, Our big data charms (apache licensed) deploy Hadoop (apache licensed). Hadoop supports various compression codecs, with one of the more popular being lzo. lzo is GPLv2 licensed and therefore not distributed with Hadoop. As a charm author, what is my licensing obligation if I want my

Re: charm license requirements with multi-licensed payloads

Hey Kevin, When you write a charm and include a copyright file, what you are licensing are the lines of code that you write in the charm, not the software itself. You may choose any license you want. If you want to specify the license each piece of software uses, you can do so in the README

Re: charm license requirements with multi-licensed payloads

Thanks, José! I was curious about this too. A follow-up on this question: I have a Charm repo that includes Charms from different sources with patches. Some of these Charms are licensed differently, some require copyleft and some don't. Now, I do it

Re: charm license requirements with multi-licensed payloads

That is right. When you do a patch and include it inside a charm, what you are doing is a contribution to the pre-existing code, hence inheriting the license from another charm. If it doesn't have a license and it's been released, I would assume a public domain license until a license is