4 ms·

The AGPL3 license means that all my MIT code I distribute in a package will be considered AGPL3. So I can't combine Grafana, and my original work and improve bo

by iFire 5y ago

The AGPL3 license means that all my MIT code I distribute in a package will be considered AGPL3. So I can't combine Grafana, and my original work and improve both. This is a stated purpose of GPL3 / AGPL3. I am happy to be told I am wrong and it is possible.

aloisdg 5y ago
Yes you can. The purpose of (A)GPLv3 is that someone else cannot benefit from you work if you cant benefit from theirs. It is a matter of leveraging cooperation.
blendergeek 5y ago
It depends on what you mean by "combine". If you are releasing a Linux distro that has as one piece of software Grafana, you'll be fine. If your software is in effect an extension of Grafana, you will need to release source code under AGPLv3. https://www.gnu.org/licenses/gpl-faq.html#MereAggregation https://www.gnu.org/licenses/gpl-faq.html#MereAggregation
- iFire 5y ago
  Exactly. This is my understanding. Edited: Or pick a fork and live on it forever. Edited: Or write my own Grafana
  - devmor 5y ago
    This conflicts with everything you've said so far on this topic. I don't think you do understand.
devmor 5y ago
If you are not offering a product built on top of Grafana as a network-available service, then there is no difference between the new license and the previous GPL3 license for you whatsoever. If you are, then your obligation would change to specifically making only that work which builds on top of the Grafana code available to others for free, along with the AGPL3-licensed Grafana code. You are not required to license that code that you wrote in any way, with the caveat that others may freely use it.
- Macha 5y ago
  The previous license was Apache 2.0, not GPLv3
  - devmor 5y ago
    My mistake, regardless, Apache2.0 is GPL3 compat.
aidenn0 5y ago
IANAL, but pretty sure you can license all of your code MIT, while also making it part of an AGPLv3 system; someone else can already distrubute your MIT licensed code under AGPL3, since that would comply with the terms of the MIT license.

by iFire 5y ago

aloisdg 5y ago

Yes you can. The purpose of (A)GPLv3 is that someone else cannot benefit from you work if you cant benefit from theirs. It is a matter of leveraging cooperation.

blendergeek 5y ago

It depends on what you mean by "combine". If you are releasing a Linux distro that has as one piece of software Grafana, you'll be fine. If your software is in effect an extension of Grafana, you will need to release source code under AGPLv3. https://www.gnu.org/licenses/gpl-faq.html#MereAggregation https://www.gnu.org/licenses/gpl-faq.html#MereAggregation

iFire 5y ago
Exactly. This is my understanding. Edited: Or pick a fork and live on it forever. Edited: Or write my own Grafana
- devmor 5y ago
  This conflicts with everything you've said so far on this topic. I don't think you do understand.

devmor 5y ago

If you are not offering a product built on top of Grafana as a network-available service, then there is no difference between the new license and the previous GPL3 license for you whatsoever. If you are, then your obligation would change to specifically making only that work which builds on top of the Grafana code available to others for free, along with the AGPL3-licensed Grafana code. You are not required to license that code that you wrote in any way, with the caveat that others may freely use it.

Macha 5y ago
The previous license was Apache 2.0, not GPLv3
- devmor 5y ago
  My mistake, regardless, Apache2.0 is GPL3 compat.

aidenn0 5y ago

IANAL, but pretty sure you can license all of your code MIT, while also making it part of an AGPLv3 system; someone else can already distrubute your MIT licensed code under AGPL3, since that would comply with the terms of the MIT license.