4 ms·
Also, note that Google prohibits all use of SSPL just like it prohibits use of AGPL: https://opensource.google/docs/thirdparty/licenses/#agpl-affero-gpl-and-ssp
by VoxPelli 6y ago
Also, note that Google prohibits all use of SSPL just like it prohibits use of AGPL: https://opensource.google/docs/thirdparty/licenses/#agpl-affero-gpl-and-sspl-not-allowed https://opensource.google/docs/thirdparty/licenses/#agpl-aff...
It also prohibits use of Business Source Licensed software, but as source code under that license will always after at most 4 years transition to a GPL compatible license, all such code will eventually be possible to use at Google and one can easily maintain a GPL-compatible fork that merges code in as the BUSL expires, thus enabling a good exchange between BUSL and open source, whereas no such exchange is possible with SSPL, its forever stuck in a AGPL like license and most companies generally stay far far away from AGPL.