3 ms·
The announcement seems to say that products that include an unmodified version grafana can still be proprietary, and only modifications to grafana itself will h
by lovasoa 5y ago
The announcement seems to say that products that include an unmodified version grafana can still be proprietary, and only modifications to grafana itself will have to be published.
However, the AGPL itself is quite clear that if you distribute a larger work based on an AGPL software, the whole larger work has to be distributed under the same license.
Would you still be confident shipping a proprietary product that includes a grafana dashboard ?
- pavon 5y agoThe GPL and AGPL are clear that bundling does not constitute a derivative work, and does not require you to license the bundled works under the GPL/APL. > Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate. https://www.gnu.org/licenses/agpl-3.0.en.html#section5 https://www.gnu.org/licenses/agpl-3.0.en.html#section5 https://www.gnu.org/licenses/gpl-faq.html#MereAggregation https://www.gnu.org/licenses/gpl-faq.html#MereAggregation If you write a custom plugin for Grafana, then that plugin will likely need to be distributed under the AGPL (depending on Grafana's plugin architecture), but not your entire app. I would be completely confident in bundling in this manner. The AGPL3 and GPL3 have identical wording on this matter, and it has been a well understood aspect of the GPL for decades.
- lovasoa 5y agoYes, I understood that just distributing grafana and your app together is not a problem, that is bundling. But what if grafana is a part of your app ? If you have a grafana dashboard inside the UI of your own application, this cannot be considered bundling, can it ? The AGPL is clear that if the result of the aggregation "forms a larger product", then you are NOT covered by the bundling clause.