> Note that if you self-host this, that you are bound by those code publication requirements of the AGPL 3.0 license that apply to your specific circumstance.
Dear everyone, please remember, the restrictions are on AGPL is about making changes and not upstreaming the changes. You can absolutely run it as a service, or as a networked part of your application.
For example, if you wanted to remove their branding or some message in an email or a link on a webpage from the source code, you could absolutely do that -- as long as you release the forked code under a similar license in the public sphere.
Businesses still won't touch AGPL (for now) and that's what they're going for to encourage enterprise signups (I find calling it "GPL-licensed" is a little misleading on the front page, but I get why they did it) -- but I think at some point that will probably end. I'm glad it's still going though, more chances for people to make money doing F/OSS (AGPL is free software).
Dear everyone, please remember, the restrictions are on AGPL is about making changes and not upstreaming the changes. You can absolutely run it as a service, or as a networked part of your application.
For example, if you wanted to remove their branding or some message in an email or a link on a webpage from the source code, you could absolutely do that -- as long as you release the forked code under a similar license in the public sphere.
Businesses still won't touch AGPL (for now) and that's what they're going for to encourage enterprise signups (I find calling it "GPL-licensed" is a little misleading on the front page, but I get why they did it) -- but I think at some point that will probably end. I'm glad it's still going though, more chances for people to make money doing F/OSS (AGPL is free software).