Our great sponsors
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
foundation
☁️♮🏛 This repo contains several documents related to the operation of the CNCF. File non-technical issues related to CNCF here.
I asked about this on Github: https://github.com/minio/minio/issues/12142
They claim that there are no external contributions for which they don't have permission to relicense. They might have removed them over the last few months or contacted the contributors.
Considering this is company with a decent amount of funding [1], I'd expect them to have done their homework.
[1] https://www.crunchbase.com/organization/minio-inc
https://github.com/cncf/foundation/blob/master/allowed-third...
I haven't read the details, or ever seen this policy before (I'm new to both projects) but it was summarized by one of our counterparts at the Linux Foundation here:
https://twitter.com/cra/status/1384859663615864833
Tl;dr: licenses must be approved for use, and the CNCF has this list of allowed licenses, AGPL is not on it. The CNCF is in the business of distributing permissively-licensed software is the short version I guess. I don't understand, I don't work on the legal side, I am a dev and I support end users.
It seems if your Apache 2.0 licensed project needs to modify and distribute as modified Grafana, which it seems likely we will need to do at some point, then you cannot distribute them together. Chris says they are going to work something out, but when a component has made a decision to re-license with a restrictive-copyleft license such as AGPL, I don't know what there is that can be done.
Maybe the CNCF adopts AGPL too, (which would mean that then all those "viral-GPL" FUD-spreaders will have been right...) that seems counter-productive if that is the outcome.