Re:Affirmation of the Open Source Definition
by dragonwriter on Thursday February 07, 2019 @04:31PM
(#19108780)
> The AGPL closed a loophole of GPL software
No, it didn't, if it closed a GPL loophole, it would have been a subsequent version of the GPL. It provided an alternative to serve slightly different interests while remaining compatible with Free Software principles and the copyleft mechanism of preventing proprietary derivative works.
> We can agree that the AGPL is the successor in spirit of the GPL
No, we can't, they are licenses maintained in parallel by the same entity. The successor in spirit to the GPL is the subsequent version of the GPL. The AGPL is a related alternative—not a successor, spiritual or otherwise—to the GPL.
> The use of cloud services to sidestep the AGPL requirements is the newest loophole
Cloud services are pretty much exactly what the AGPL is aimed at (well, remotely hosted web services; whether they are dynamically provisioned as implied by “cloud” is immaterial, both to the AGPL and to the incorrect allegation of sidestepping.) Cloud services do not enable sidestepping any intended feature of the AGPL, because they do nothing relevant to it's operation that the initial environment to which the AGPL was targeted did not.
Now, there may be things MongoDB authors want that the AGPL creators did not intend to provide, but that's not a loophole in the AGPL, but a fundamental divergence of purpose.
> The problem here is, that we're in unexplored territory.
No, we aren't.
> MongoDB is attempting something new and innovative to try and establish what the author of a piece of software expects from the users of that software.
This is true only in the trivial sense that it is true of every new (whether completely original or slightly modified from some other) license, proprietary or FOSS.
> Some might argue that the purpose is to extract money, which may or may not be true, but it is beside the point.
It may be beside the point that you want people to focus on, but neither the express fact that the intent is both to extract money and to do so by restricting other party’s freedom to use the software is precisely the point for people who care about the ethos of either the Free Software or Open Source communities (or, even for those who don't care about the ethos, but are sold on the practical benefits of the freedom provided by licenses inspired by the ethos of those communities.)
> Work licensed under the SSPL has almost all of the same freedoms AGPL works have
And a braindead body kept on life support has almost all of the same functions as a living body. But, in either case, there are rather critical differences hidden under “almost”.
> So they have every right to label it as "open source",
“open source” has a well established and understood use in software, and calling the SSPL open source conflicts with that in a way which is deceptive, and the only reason for making the claim is to commercially capitalize on that deception. Established usage in the field is one of the things looked at to determine if the kind of deception required for fraud is present, and I think a case can be made that making this deceptive representation in promotion of commercial products and services is fraudulent.
No, it didn't, if it closed a GPL loophole, it would have been a subsequent version of the GPL. It provided an alternative to serve slightly different interests while remaining compatible with Free Software principles and the copyleft mechanism of preventing proprietary derivative works.
> We can agree that the AGPL is the successor in spirit of the GPL
No, we can't, they are licenses maintained in parallel by the same entity. The successor in spirit to the GPL is the subsequent version of the GPL. The AGPL is a related alternative—not a successor, spiritual or otherwise—to the GPL.
> The use of cloud services to sidestep the AGPL requirements is the newest loophole
Cloud services are pretty much exactly what the AGPL is aimed at (well, remotely hosted web services; whether they are dynamically provisioned as implied by “cloud” is immaterial, both to the AGPL and to the incorrect allegation of sidestepping.) Cloud services do not enable sidestepping any intended feature of the AGPL, because they do nothing relevant to it's operation that the initial environment to which the AGPL was targeted did not.
Now, there may be things MongoDB authors want that the AGPL creators did not intend to provide, but that's not a loophole in the AGPL, but a fundamental divergence of purpose.
> The problem here is, that we're in unexplored territory.
No, we aren't.
> MongoDB is attempting something new and innovative to try and establish what the author of a piece of software expects from the users of that software.
This is true only in the trivial sense that it is true of every new (whether completely original or slightly modified from some other) license, proprietary or FOSS.
> Some might argue that the purpose is to extract money, which may or may not be true, but it is beside the point.
It may be beside the point that you want people to focus on, but neither the express fact that the intent is both to extract money and to do so by restricting other party’s freedom to use the software is precisely the point for people who care about the ethos of either the Free Software or Open Source communities (or, even for those who don't care about the ethos, but are sold on the practical benefits of the freedom provided by licenses inspired by the ethos of those communities.)
> Work licensed under the SSPL has almost all of the same freedoms AGPL works have
And a braindead body kept on life support has almost all of the same functions as a living body. But, in either case, there are rather critical differences hidden under “almost”.
> So they have every right to label it as "open source",
“open source” has a well established and understood use in software, and calling the SSPL open source conflicts with that in a way which is deceptive, and the only reason for making the claim is to commercially capitalize on that deception. Established usage in the field is one of the things looked at to determine if the kind of deception required for fraud is present, and I think a case can be made that making this deceptive representation in promotion of commercial products and services is fraudulent.