Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LICENSE is quite unspecific: unclear licensing conditions and no copyright holders named #5777

Closed
juliangilbey opened this issue Jan 13, 2021 · 12 comments
Assignees
Labels
Breaking Change Issues is has a change that will break something in the next release. Bug A bug in an icon glyph or a first-party library.

Comments

@juliangilbey
Copy link

The new license wording is:

# Icons: Apache 2.0 (https://www.apache.org/licenses/LICENSE-2.0)
Some of the icons are redistributed under the Apache 2.0 license. All other
icons are either redistributed under their respective licenses or are
distributed under the Apache 2.0 license.

This means that it is entirely unclear what the actual licensing conditions for any individual icon are, and there does not seem to be any way to find out this information. The LICENSE file also does not specify who the copyright holders are. We have a much older version of MaterialDesign in Debian, but without a clearer license, it will not be possible to update beyond v5.5.55.

Would it be possible to improve the LICENSE file?

Thanks!

@juliangilbey juliangilbey added the Bug A bug in an icon glyph or a first-party library. label Jan 13, 2021
@mririgoyen
Copy link
Collaborator

We are discussing this internally. Our LICENSE was written with the help of legal counsel and worded this way intentionally due to the inclusion of several brand icons. I will update this issue when we know more.

@mririgoyen mririgoyen self-assigned this Jan 13, 2021
@juliangilbey
Copy link
Author

Oh wow, thank you so much!

@mririgoyen mririgoyen added this to the Next Major - 6.0.xx milestone Jan 13, 2021
@mririgoyen mririgoyen added the Breaking Change Issues is has a change that will break something in the next release. label Jan 13, 2021
@petergardfjall
Copy link

petergardfjall commented Feb 17, 2021

Any update on this?

All other icons are either redistributed under their respective licenses

How would one know which icons this statement refers to?

@hoyce
Copy link

hoyce commented Aug 20, 2021

Any update on this issue?

We have the same problem. We are interested in using this icon library but we cannot figure out which license correspond to which icon/icons.

It would be good if all icons have the same license or if you could hover an icon and clearly see its specific license.

@mririgoyen
Copy link
Collaborator

We cannot release all icons under the same license because brands are the outliers.

All icons, as long as it isn't some company or product's logo, are released under Apache 2. Steer clear or brand icons, and you're good.

We're working internally on cataloging all brand icons we currently have with the intent on removing most. The others will have appropriate license information included in our v6 release. It's time consuming and we're all volunteers but we are definitely still working on it.

@hoyce
Copy link

hoyce commented Aug 20, 2021

Thanks for your quick response! I understand that you are all volunteers and I really appreciate your work.
Although, it is important for us to fully understand the licensing due to the fact that we don't want to violate any license.

Looking forward to the v6 and keep up the good work!

@juliangilbey
Copy link
Author

Thanks @goyney, that's very much appreciated!

Thinking about my Debian colleagues who are packaging this amazing font, it would be really helpful if you were able to have two separate fonts, one fully "free" and the other with restrictive licensing. But I realise that may well be too much work. Just a thought!

@mririgoyen
Copy link
Collaborator

mririgoyen commented Aug 20, 2021

Honestly, if anything, this is just making a better case for us to completely remove all brand icons. There's still some pushback into do so by other contributors on that front, but we will have some renewed conversations about how we plan to tackle this in the coming days.

@mririgoyen
Copy link
Collaborator

Thanks @goyney, that's very much appreciated!

Thinking about my Debian colleagues who are packaging this amazing font, it would be really helpful if you were able to have two separate fonts, one fully "free" and the other with restrictive licensing. But I realise that may well be too much work. Just a thought!

This likely won't happen any time soon. As I stated previously, steer clear of the brand icons and you're fine. You must only abide by the license of the icons you choose to use.

We're going to try and build a database of what brand icons we have and what each icon's license is to include in our distributed LICENSE file, but that won't happen for some time as we need to build some backend infrastructure to support that extra data. Even with all that data, all icons will still be released together. So as I stated above, steer clear of brand icons, and then you can safely assume Apache 2.0.

@juliangilbey
Copy link
Author

Thanks @goyney. Yes, I realise it won't happen any time soon, and we really appreciate the amazing work you're doing!

Unfortunately for my colleagues, though, they can only package for Debian main (and all of Debian's derivatives such as Ubuntu) those icons which have open-source type licenses. So they will have to strip the non-free icons from the fonts before packaging them. It's not ideal, as it will be slightly different from what you have released, but a benefit is that they will know they can use every icon available without having to check the license of every icon they want to use.

We look forward to the detailed per-icon LICENSE file. When you do get to that point, if you can make it (easily) machine parseable, that would be fantastic.

Best wishes, Julian

@mririgoyen mririgoyen removed this from the Releasing Soon - 6.1.64 milestone Aug 30, 2021
@mririgoyen
Copy link
Collaborator

An update to this: We've deprecated all brand icons. They will be removed from this library in v8. Our license will then simply be Apache 2.0.

See the announcement here: #6602

Because we have a plan that won't come to fruition for about a year, I'm going to close this one. Please follow the announcement for updates as we get closer to this change.

@juliangilbey
Copy link
Author

Amazing, thanks!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Breaking Change Issues is has a change that will break something in the next release. Bug A bug in an icon glyph or a first-party library.
Projects
None yet
Development

No branches or pull requests

4 participants