ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    MongoDB Major Change to Licensing

    Scheduled Pinned Locked Moved Developer Discussion
    mongodbopen sourcelicensingdatabasenosql
    78 Posts 7 Posters 8.3k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • scottalanmillerS
      scottalanmiller @DustinB3403
      last edited by

      @DustinB3403 said in MongoDB Major Change to Licensing:

      Unless, I'm selling (or offering) a service to people that are not employees of the business, and then I've agreed to purchase a license or open everything up.

      The only clear exception is if you offer the service only to yourself. Once you offer it to anyone else, there is no grounds for thinking that you have an exception to the rule.

      1 Reply Last reply Reply Quote 0
      • stacksofplatesS
        stacksofplates
        last edited by

        Didn't read the whole thread but they apparently didn't learn from Redis. They will have to move back or fail. There's nothing stopping anyone from forking under the previous license and essentially copying fixes.

        This helps no one at all.

        tonyshowoffT scottalanmillerS 2 Replies Last reply Reply Quote 1
        • tonyshowoffT
          tonyshowoff @stacksofplates
          last edited by

          @stacksofplates said in MongoDB Major Change to Licensing:

          Didn't read the whole thread but they apparently didn't learn from Redis. They will have to move back or fail. There's nothing stopping anyone from forking under the previous license and essentially copying fixes.

          This helps no one at all.

          Just FYI, this is what he's talking about, a very similar license scheme they walked back on after realising it was a stupid idea, but MongoDB thinks it's great

          https://www.techrepublic.com/article/why-redis-labs-made-a-huge-mistake-when-it-changed-its-open-source-licensing-strategy/

          stacksofplatesS scottalanmillerS 2 Replies Last reply Reply Quote 1
          • stacksofplatesS
            stacksofplates
            last edited by

            Hahaha

            This storm will pass, though my former MongoDB colleague Jared Rosoff is probably correct in suggesting on Twitter that: "Even if the result of the change isn't controversial, it's hard to trust a platform that can change on a whim."

            https://www.techrepublic.com/article/why-redis-labs-made-a-huge-mistake-when-it-changed-its-open-source-licensing-strategy/

            1 Reply Last reply Reply Quote 0
            • stacksofplatesS
              stacksofplates @tonyshowoff
              last edited by

              @tonyshowoff said in MongoDB Major Change to Licensing:

              @stacksofplates said in MongoDB Major Change to Licensing:

              Didn't read the whole thread but they apparently didn't learn from Redis. They will have to move back or fail. There's nothing stopping anyone from forking under the previous license and essentially copying fixes.

              This helps no one at all.

              Just FYI, this is what he's talking about, a very similar license scheme they walked back on after realising it was a stupid idea, but MongoDB thinks it's great

              https://www.techrepublic.com/article/why-redis-labs-made-a-huge-mistake-when-it-changed-its-open-source-licensing-strategy/

              Ha you beat me to it.

              1 Reply Last reply Reply Quote 0
              • black3dynamiteB
                black3dynamite
                last edited by

                Good thing Wiki.js is phasing out MongoDB for there 2.0 release.

                scottalanmillerS 1 Reply Last reply Reply Quote 1
                • S
                  StorageNinja Vendor
                  last edited by StorageNinja

                  @scottalanmiller said in MongoDB Major Change to Licensing:

                  if you are a SaaS vendor looking at building software that uses MongoDB somewhere, you'd better get a lawyer looking over this license and how it applies to you.

                  This is becoming a bigger issue as the biggest SaaS vendors hide behind this clause more and more with incredibly proprietary forks. They offer very little to no actual core development or contribution and it goes against the previous method of GPL code getting funding.

                  It annoys me, as the legal headaches of contributing internal only use code back will block some companies from using OSS, but I see it both ways.

                  The startups who are doing a lot of the core housekeeping of NOSQL platforms are learning they can't find a business model. This is getting messier and messier.

                  scottalanmillerS 1 Reply Last reply Reply Quote 0
                  • scottalanmillerS
                    scottalanmiller @black3dynamite
                    last edited by

                    @black3dynamite said in MongoDB Major Change to Licensing:

                    Good thing Wiki.js is phasing out MongoDB for there 2.0 release.

                    No kidding.

                    1 Reply Last reply Reply Quote 0
                    • scottalanmillerS
                      scottalanmiller @stacksofplates
                      last edited by

                      @stacksofplates said in MongoDB Major Change to Licensing:

                      Didn't read the whole thread but they apparently didn't learn from Redis. They will have to move back or fail. There's nothing stopping anyone from forking under the previous license and essentially copying fixes.

                      This helps no one at all.

                      Exactly. I'm shocked that it hasn't forked already, in fact!

                      1 Reply Last reply Reply Quote 0
                      • scottalanmillerS
                        scottalanmiller @tonyshowoff
                        last edited by

                        @tonyshowoff said in MongoDB Major Change to Licensing:

                        @stacksofplates said in MongoDB Major Change to Licensing:

                        Didn't read the whole thread but they apparently didn't learn from Redis. They will have to move back or fail. There's nothing stopping anyone from forking under the previous license and essentially copying fixes.

                        This helps no one at all.

                        Just FYI, this is what he's talking about, a very similar license scheme they walked back on after realising it was a stupid idea, but MongoDB thinks it's great

                        https://www.techrepublic.com/article/why-redis-labs-made-a-huge-mistake-when-it-changed-its-open-source-licensing-strategy/

                        that one got forked FAST.

                        1 Reply Last reply Reply Quote 0
                        • scottalanmillerS
                          scottalanmiller @StorageNinja
                          last edited by

                          @StorageNinja said in MongoDB Major Change to Licensing:

                          @scottalanmiller said in MongoDB Major Change to Licensing:

                          if you are a SaaS vendor looking at building software that uses MongoDB somewhere, you'd better get a lawyer looking over this license and how it applies to you.

                          This is becoming a bigger issue as the biggest SaaS vendors hide behind this clause more and more with incredibly proprietary forks. They offer very little to no actual core development or contribution and it goes against the previous method of GPL code getting funding.

                          It annoys me, as the legal headaches of contributing internal only use code back will block some companies from using OSS, but I see it both ways.

                          The startups who are doing a lot of the core housekeeping of NOSQL platforms are learning they can't find a business model. This is getting messier and messier.

                          Partially because there are just too any vendors involved.

                          What's amazing, though, is that a move like this took a customer who was very into MongoDB and using it in projects and was literally working with MongoDB's own hosted product and now looking to avoid it like the plague.

                          So at least in this one case, they are likely losing hosted product from this. And gaining nothing. I imagine a lot of customers going through this same process.

                          1 Reply Last reply Reply Quote 1
                          • 1
                          • 2
                          • 3
                          • 4
                          • 4 / 4
                          • First post
                            Last post