Intriguing. 's new seems to ask pretty much the same thing as the , just in a louder voice:

They've already had to smash out a quick v2.0, to fix the Section 13 demand that software used in a service using -licensed code be licensed under SSPL, making it incompatible with every other license:

This has a far wider scope than the AGPL:

> all programs that you use to make the Program or modified version available as a service, including, without limitation, management software, user interfaces, application program interfaces, automation software, monitoring software, backup software, storage software and hosting software, all such that a user could run an instance of the service using the Service Source Code you make available.

The AGPL stays within the US legal definition of a derivative work. This is way way broader, not just louder.

@strypey If I recallbcorrectly, they seen to be equal, except that #AGPL avoids license ploriferation of the other one.

@adfeno @strypey If they were equal, MongoDB would have stayed with the AGPL, which they were using before switching to their own.

@clacke that's assuming that Mongodb understand the , and that making the language in a license more aggressive doesn't necessarily making it any easier to enforce. Given the changes they've already had to make to their vanity license, to fix problems that stood out like dog's balls in v1.0 even to a non-lawyer like me, I'm not convinced they understand either of these things.

@strypey @adfeno What confuses me is that Heather Meeker is hardly new at this, and hardly an outsider. She was part of the MPLv2 drafting team, yet comes up with this and the Commons Clause.

I think there is an intense level of desperation among open source VCs, and a feeling that Something Must Be Done. Even a competent person may want this so much to be something good, and otherwise the SSPL is a test balloon, the second test balloon, to find out where the limits are and what the way forward might look like. No better way to get a good answer than to post the wrong answer on the internet. It certainly triggered a lot of discussion, not the least of which the discussions at CopyleftConf.
@strypey I don't really see MongoDB having a future unless they change the license or a fork appears. Being jetisoned from Debian is pretty catastrophic. Maybe the financiers behind MongoDB are even willing to risk losing MongoDB itself as long as whatever other projects they're involved in can learn of a way to eke out a few more percent of captured revenue.
Sign in to participate in the conversation
Mastodon - NZOSS

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!