News for hackers. Stuff that matters.
Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by nopzor on Tuesday April 20, 2021 @04:36PM (#26881266)
you realize that if you contribute to a company apache project without a CLA, they can change the license out from under you to _any_ license that they want, right?

[note: am co-founder/ceo of grafana labs]

Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by jrochkind1 on Tuesday April 20, 2021 @07:27PM (#26883356)
How do you figure?

The way I've understood it is part of the point of CLA's is to allow license changes, and that without them no license changes are possible to community projects. Because all the contributors own the copyright to the code they contributed, which they licensed under the existing license. To change the license you'd need to contact all the contributors and get permission (so okay, not impossible, just infeasible). The CLA is getting that permission in advance, to let some controlling body change copyright later.

Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by nopzor on Tuesday April 20, 2021 @09:44PM (#26884458)
anyone can change the license of apache software, without any permission. the right to do so is built into the apache license.
Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by dec0dedab0de on Wednesday April 21, 2021 @09:50AM (#26889660)
I thought the point of CLA's in general is to stop contributors from revoking their license, or claiming the entire program is a collaborative work and that they have joint copyright over all of it. I don't think either has ever happened in open source, but I believe is possible, at least in the US.