This is the license text: https://www.mongodb.com/licensing/server-side-public-license

A few days ago, Elasticsearch and Kibana were converted from Apache 2 to SSPL, and there has been a lot of criticism (for exmaple). The biggest problem with SSPL seems to be the fact that if software licensed under it is used for an online service, you have to open source everything on the server that falls under the broadly worded “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”, which some worry could be interpreted by courts as “everything installed on the server”. The fact that it’s not OSI approved (and unlikely to be) is also a point of concern.

The article I linked (IMO quite reasonably) state that Elastic is only using this license to make the free version of their software undesirable and to force more people to buy a commercial license, but that’s a demerit to the company and not necessarily to the license.

What does the “free software, not just open source” community think of this? Does a license like this go too far, or is this the next step in forcing the open sourcing of software? Would you personally ever use this license for your IP?

    • @AgreeableLandscapeOPM
      link
      2
      edit-2
      3 years ago

      Something I’ve been thinking about: are there any fully libre server operating systems? Most Linux distros have some proprietary blobs, especially drivers, and under the strictest interpretation, that wouldn’t be compatible with the SSPL. All the more reasons for the Linux community to reject proprietary drivers honestly.

        • @AgreeableLandscapeOPM
          link
          3
          edit-2
          3 years ago

          Interesting, but now you have to wonder if the SSPL would even be allowed to be used on shared/VPS hosts since some of their software is proprietary.

          Hell, what about the BIOS of the motherboard? Microcode in the processor? The code in the micro controller than runs the power supply?

          Honestly, I like the SSPL as a philosophy, essentially forcing the entire ecosystem to be FOSS if they want to use a particular project, but it’s kind of made unusable by the fact that non-free software has infected everything, and in many cases, with no alternative.

            • @AgreeableLandscapeOPM
              link
              13 years ago

              I am sure the license is limited to a first level in the hierarchy (direct level) when running.

              Thing is, it doesn’t mention it, and it says “without limitation” before listing off software examples

                • @AgreeableLandscapeOPM
                  link
                  1
                  edit-2
                  3 years ago

                  Here’s the thing, the ultimate meaning of the license isn’t up to the authors, it’s up to the courts, and they can interpret it however they want. This was mentioned in the article I linked, which mentions that even though the authors tried to debunk worries in a FAQ, not even they know how the license would be really be interpreted, and the author’s intentions are irrelevant to judges, only the license text itself matters.

  • @koalp
    link
    1
    edit-2
    1 year ago

    deleted by creator