[License-review] Approval: Server Side Public License, Version 1 (SSPL v1)

Kyle Mitchell kyle at kemitchell.com
Thu Oct 18 18:32:16 UTC 2018


On 2018-10-18 11:10, Stefano Zacchiroli wrote:
> Heya, SSPL reads:
>
> > If you make the functionality *of the Program or* a modified version
> > available to third parties as a service, you must make the Service
> > Source Code available via network download to everyone at no charge,
> > under the terms of this License.
>
> in contrast, AGPL:
>
> > if you *modify the Program*, your modified version must prominently
> > offer all users interacting with it remotely through a computer
> > network
>
> so SSPL triggers on mere use, rather than on modification (+ use). This
> point hasn't seen much discussion in this thread yet, but it seems to me
> to be both a major difference with the status quo and a potential
> blocker in view of OSD §6 (or, more generally, Freedom 0).
>
> This looks like a more significant differentiation point between AGPL
> and SSPL, rather than the stated motivation that it is unclear what is
> the reach of AGPL copyleft provision.

Provision of a network service without modification is
constructive distribution under OSL and NPOSL.

Modification without provision of a network service triggers
under private-licenses/patches-back licenses that OSI
approved for dual licensors in the early 2000s.  The list to
review is Plan 9 (Lucent),  Watcom (Sybase), and RPL
(Technical Pursuit).

-- 
Kyle Mitchell, attorney // Oakland // (510) 712 - 0933



More information about the License-review mailing list