2 ms·

You don’t need to distribute anything if you didn’t change anything. You’re using something available somewhere else already. Vitality comes from the way you c

You don’t need to distribute anything if you didn’t change anything. You’re using something available somewhere else already. Vitality comes from the way you combine this AGPL code with other code and how you can’t change the license of modified Plausible CE, or the thing you build using Plausible CE. If you modify Plausible, you distribute the modified version. If you build something using Plausible, you distribute the thing, and with AGPL license. That’s it.

Wowfunhappy 2y ago
By including Plausible in a bigger website, doesn't that website become a derivative work of Plausible? If not, why is this situation different from an app that links a GPL'd library?
- bayindirh 2y ago
  According to the docs [0], Plausible CE is installed as a Docker image, running in its set of containers, as an independent service from your site, which you only add the tracking snippet. This doesn't make your site as a derivative of Plausible, but you're installing Plausible as a different tool, independent from your site. Like installing a GPL binary doesn't make all BSD licensed binaries switch to GPL license on your system, running an AGPL licensed service on your server which communicates with your site doesn't make your site AGPL automatically, because you're not deriving Plausible, but you're installing and using it. Now, if you want to build a service/website by directly modifying the Plausible CE source code, you have to open that derivative codebase with AGPL, only if you're redistributing the modified code (i.e. making the modified website available to other people). If you modified the code, but you're not distributing it (i.e. Only you're using it yourself), you can keep it to yourself. [0]: https://github.com/plausible/community-edition/ https://github.com/plausible/community-edition/

Wowfunhappy 2y ago

By including Plausible in a bigger website, doesn't that website become a derivative work of Plausible? If not, why is this situation different from an app that links a GPL'd library?

bayindirh 2y ago
According to the docs [0], Plausible CE is installed as a Docker image, running in its set of containers, as an independent service from your site, which you only add the tracking snippet. This doesn't make your site as a derivative of Plausible, but you're installing Plausible as a different tool, independent from your site. Like installing a GPL binary doesn't make all BSD licensed binaries switch to GPL license on your system, running an AGPL licensed service on your server which communicates with your site doesn't make your site AGPL automatically, because you're not deriving Plausible, but you're installing and using it. Now, if you want to build a service/website by directly modifying the Plausible CE source code, you have to open that derivative codebase with AGPL, only if you're redistributing the modified code (i.e. making the modified website available to other people). If you modified the code, but you're not distributing it (i.e. Only you're using it yourself), you can keep it to yourself. [0]: https://github.com/plausible/community-edition/ https://github.com/plausible/community-edition/