5 ms·

Note that AGPL (Affero GPL) expands the attached strings to any kind of user-facing network interface. So if you take AGPL code and make a Service-as-a-Softwar

Note that AGPL (Affero GPL) expands the attached strings to any kind of user-facing network interface. So if you take AGPL code and make a Service-as-a-Software-Substitute with it, you're still legally obliged to provide source code to the users of your SaaSS. In fact, AGPL is so badass that not even Google [0] wants to touch it with a 10 yard stick :) [0] https://opensource.google/documentation/reference/using/agpl-policy/ https://opensource.google/documentation/reference/using/agpl...

teddyh 4y ago
> you're still legally obliged to provide source code to the users of your SaaSS. IIUC, only insofar as the software already does that (i.e. by a download link in the UI). If the software currently lacks such a link, you have no obligation to add that feature, AGPL or not.
- paskozdilar 4y ago
  Affero GPL [0] states that: > [...] if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge, through some standard or customary means of facilitating copying of software. So the way I understand it is as long as you don't modify the software, you can run the original version as a network service without providing source code. But if you do modify the program and serve it to users through a network interface, you have to include some means of copying the source code. [0] https://www.gnu.org/licenses/agpl-3.0.en.html https://www.gnu.org/licenses/agpl-3.0.en.html
  - teddyh 4y ago
    Interesting; I may have been misinformed.
kevin_thibedeau 4y ago
Only if outsiders can use the service. Internal corporate use of GPL code has zero strings. You're all one entity and no distribution has happened.
Schroedingersat 4y ago
> So if you take AGPL code and make a Service-as-a-Software-Substitute with it, you're still legally obliged to provide source code to the users of your SaaSS. So the users of the software can do whatever they want with it with no strings attached then. I don't see how this concept is so hard.
- deleted 4y ago
  [deleted]
- jay_kyburz 4y ago
  I think the concept is hard because its not clear what "users" you are talking about. The people using the software to host the SaS have strings, the users of the SaS do not. There are two groups who could be considered users.

teddyh 4y ago

> you're still legally obliged to provide source code to the users of your SaaSS. IIUC, only insofar as the software already does that (i.e. by a download link in the UI). If the software currently lacks such a link, you have no obligation to add that feature, AGPL or not.

paskozdilar 4y ago
Affero GPL [0] states that: > [...] if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge, through some standard or customary means of facilitating copying of software. So the way I understand it is as long as you don't modify the software, you can run the original version as a network service without providing source code. But if you do modify the program and serve it to users through a network interface, you have to include some means of copying the source code. [0] https://www.gnu.org/licenses/agpl-3.0.en.html https://www.gnu.org/licenses/agpl-3.0.en.html
- teddyh 4y ago
  Interesting; I may have been misinformed.

kevin_thibedeau 4y ago

Only if outsiders can use the service. Internal corporate use of GPL code has zero strings. You're all one entity and no distribution has happened.

Schroedingersat 4y ago

> So if you take AGPL code and make a Service-as-a-Software-Substitute with it, you're still legally obliged to provide source code to the users of your SaaSS. So the users of the software can do whatever they want with it with no strings attached then. I don't see how this concept is so hard.

deleted 4y ago
[deleted]
jay_kyburz 4y ago
I think the concept is hard because its not clear what "users" you are talking about. The people using the software to host the SaS have strings, the users of the SaS do not. There are two groups who could be considered users.