4 ms·

I don't get what you're saying. Why would a self-hoster care about the code publication requirements of the AGPL? It's an OSS project, the end user doesn't care

I don't get what you're saying. Why would a self-hoster care about the code publication requirements of the AGPL? It's an OSS project, the end user doesn't care if the code has to be redistributed, they're not profiting from it remaining closed.

tiffanyh 2y ago
It's not uncommon for people to link their core product into their CRM (for billing and usage). Which could in turn "infect" your core offering to now become AGPL (and now you're having to release your core product IP to the public).
- g15jv2dp 2y ago
  Two services talking to each other doesn't mean that they have to use the same licence or that AGPL "infects" the other.
  - tiffanyh 2y ago
    It’s a risk most companies don’t want to chance.
    - azemetre 2y ago
      I mean GitHub was literally built off of Git (GPL) and they had zero issues being acquired for $7.5billion.
      - tiffanyh 2y ago
        Massive difference exist between GPLv2 (Git) vs AGPLv3 (Twenty). You're comparing apples and oranges. Google documents well why they forbid AGPL https://opensource.google/documentation/reference/using/agpl-policy https://opensource.google/documentation/reference/using/agpl...
        azemetre 2y ago
        I don't think that's fair, Google is a monopoly with anticompetitive practices. Why is it a shocker that they would forbid AGPL? They want to have their fiefdoms while charging exorbitant rents. They can't compete fairly. Also there are plenty of profitable software with AGPL licenses, some even get acquired by public companies [1]. [1] https://www.rapid7.com/about/press-releases/rapid7-acquires-digital-forensics-and-incident-response-open-source-project-velociraptor/ https://www.rapid7.com/about/press-releases/rapid7-acquires-...
  - altairprime 2y ago
    Incorrect. For example, the relevant paragraph from the Google doc linked elsethread: > any product or service that depends on AGPL-licensed code, or includes anything copied or derived from AGPL-licensed code, may be subject to the virality of the AGPL license. This viral effect requires that the complete corresponding source code of the product or service be released to the world under the AGPL license. This is triggered if the product or service can be accessed over a remote network interface, so it does not even require that the product or service is actually distributed.
    - g15jv2dp 2y ago
      Just because someone wrote they in a google doc, doesn't mean that it is true.
    - Propelloni 2y ago
      What the OP is talking about is an aggregate, ie. two distinct pieces of software talking to each other over an interface, which is explicitly "non-viral", cf. AGPL v3 § 5. That being said, the AGPL v3 is on the more arduous side of things, so it's easier to avoid them completely in a business context.
      - altairprime 2y ago
        Sure, that seems like a reasonable interpretation to me. However, I don’t have any specific recommendation against AGPL v3. Accounting is just one specific field where licensing virality could have particularly complex implications.
kube-system 2y ago
At larger organizations, a significant amount of the custom code in CRM systems are proprietary business rules... e.g. pricing calculations, business rules regarding the fine details of internal and personnel operations, etc. It's not uncommon for them to contain information that is covered under NDA, which would be a non-starter for redistribution.

tiffanyh 2y ago

It's not uncommon for people to link their core product into their CRM (for billing and usage). Which could in turn "infect" your core offering to now become AGPL (and now you're having to release your core product IP to the public).

g15jv2dp 2y ago
Two services talking to each other doesn't mean that they have to use the same licence or that AGPL "infects" the other.
- tiffanyh 2y ago
  It’s a risk most companies don’t want to chance.
  - azemetre 2y ago
    I mean GitHub was literally built off of Git (GPL) and they had zero issues being acquired for $7.5billion.
    - tiffanyh 2y ago
      Massive difference exist between GPLv2 (Git) vs AGPLv3 (Twenty). You're comparing apples and oranges. Google documents well why they forbid AGPL https://opensource.google/documentation/reference/using/agpl-policy https://opensource.google/documentation/reference/using/agpl...
      - azemetre 2y ago
        I don't think that's fair, Google is a monopoly with anticompetitive practices. Why is it a shocker that they would forbid AGPL? They want to have their fiefdoms while charging exorbitant rents. They can't compete fairly. Also there are plenty of profitable software with AGPL licenses, some even get acquired by public companies [1]. [1] https://www.rapid7.com/about/press-releases/rapid7-acquires-digital-forensics-and-incident-response-open-source-project-velociraptor/ https://www.rapid7.com/about/press-releases/rapid7-acquires-...
- altairprime 2y ago
  Incorrect. For example, the relevant paragraph from the Google doc linked elsethread: > any product or service that depends on AGPL-licensed code, or includes anything copied or derived from AGPL-licensed code, may be subject to the virality of the AGPL license. This viral effect requires that the complete corresponding source code of the product or service be released to the world under the AGPL license. This is triggered if the product or service can be accessed over a remote network interface, so it does not even require that the product or service is actually distributed.
  - g15jv2dp 2y ago
    Just because someone wrote they in a google doc, doesn't mean that it is true.
  - Propelloni 2y ago
    What the OP is talking about is an aggregate, ie. two distinct pieces of software talking to each other over an interface, which is explicitly "non-viral", cf. AGPL v3 § 5. That being said, the AGPL v3 is on the more arduous side of things, so it's easier to avoid them completely in a business context.
    - altairprime 2y ago
      Sure, that seems like a reasonable interpretation to me. However, I don’t have any specific recommendation against AGPL v3. Accounting is just one specific field where licensing virality could have particularly complex implications.

kube-system 2y ago

At larger organizations, a significant amount of the custom code in CRM systems are proprietary business rules... e.g. pricing calculations, business rules regarding the fine details of internal and personnel operations, etc. It's not uncommon for them to contain information that is covered under NDA, which would be a non-starter for redistribution.