Earlier quoted context omitted.
I really like WTFPL as a permissive licence in these cases. Small developers and companies without layers of lawyers will read the licence, see that it says "do what the ---- you want", and use your code accordingly. Big companies with layers of lawyers will read the licence, blanch in terror, and either refuse to use the software, or contact you for alternative terms. Case in point: Google forbids use of the WTFPL.…
So i'm the one who forbid WTFPL at Google, and we forbid it mainly because it's bad for developers, believe it or not. We go over it in new googler training (and our reasoning is on the Google open source policy site we publish: https://opensource.google.com/docs/thirdparty/licenses/#wtfp... ) You are welcome to not (but if you go and look, it's completely consistent with my viewpoints and history in OSS so ...). I w…
MongoDB switches up its open source license
81–90 of 487 posts
Re: MongoDB switches up its open source license
#82Earlier quoted context omitted.
How is those going to affect China? If the old enforcement methods didn’t work with the previous sane-ish license, they certainly won’t work any better with the new monstrosity.
Now you don't have to pretend that they changed something without having any way to prove it. Now if the orchestration software is not open source, they can't use it.
There is literally no reason I’d use MongoDB anymore over any of its better FOSS competitors.
Re: MongoDB switches up its open source license
#83Earlier quoted context omitted.
> It's clear Google and Amazon (and maybe even Azure) are comfy taking OSS work, doing a ton of proprietary development on it, and leaving the companies who did all the groundwork flailing in the wind. Have you seen the degree of investment Microsoft has made lately in Open Source? It's an upside-down world where Microsoft if a bigger champion -- and funder -- of open source than a company like Google which was built…
The total cloud market is around $180B. 90% are on running Linux, and 2/3 are running on OSS. If it is not in the billions its not enough.
Re: MongoDB switches up its open source license
#84(Context: I worked on Compose/MongoHQ for a very long time. We were the first to monetize MongoDB) I'm sure people will get riled up about this, but it makes sense. Building a business on an OSS database in a world of behemoth cloud providers is really hard. It's clear Google and Amazon (and maybe even Azure) are comfy taking OSS work, doing a ton of proprietary development on it, and leaving the companies who did al…
> exploit permissive licenses to the max I feel like many people deciding to use an open source license for their project never consider the consequences of such choice. They use OSS because it's "cool" or they hope to get some free work done for them. If you pick an open source license and someone uses your code to build something else within the license boundaries, that is not a Bad Thing(tm). I have released many…
I just wanted to point out that from an Economic perspective this:
> I don't feel like Google/Amazon/etc. owe anything to anyone just because they made it and now have a lot of money.
And the ability to utilize that war chest to cannibalize the best of open source to create private differentiators raises the barrier of entry for competition. This market would naturally drift towards an oligopoly-like market equilibrium.
Like I said, I agree with your perspective on licenses. I would just also like OSS to be the great equalizer that instills innovation and disruption in the greater tech market place. But so long as tech giants can take any good new OSS, pay top dollar to recruit great engineers, and then throw them at OSS then I don't think this ideal vision will come to fruition.
Re: MongoDB switches up its open source license
#85Earlier quoted context omitted.
I had the feeling that AWS and Azure are pushing their own NoSQL solutions and don't care much about MongoDB.
Azure offers Cosmos DB advertised as a drop-in for MongoDB. I'm guessing Cosmos is Mongo in disguise, though I don't know if it really is, and/or whether MS has made a deal with Mongo or just think they can use the AGPL version. For the record: I'm not a big fan of Mongo (the DB) but I think MongoDB, Inc. raises a valid point wrt. developers doing all the hard work including community building and a million other thi…
Re: MongoDB switches up its open source license
#86Earlier quoted context omitted.
Azure offers Cosmos DB advertised as a drop-in for MongoDB. I'm guessing Cosmos is Mongo in disguise, though I don't know if it really is, and/or whether MS has made a deal with Mongo or just think they can use the AGPL version. For the record: I'm not a big fan of Mongo (the DB) but I think MongoDB, Inc. raises a valid point wrt. developers doing all the hard work including community building and a million other thi…
Did the MongoDB pay for their Linux distros? GCC? Git? How much are they paying to the FOSS projects they used to build their software for sale?
Re: MongoDB switches up its open source license
#87The license is clearly based on (A)GPL which is copyrighted by FSF, and has the following notice: "Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed." Does that mean that MongoDB is now infringing on FSF copyright of the license text itself?
BTW, check out the "What specifically is different between the GPL and this new license and what will it be called?" section of the FAQ:
https://www.mongodb.com/licensing/server-side-public-license...
Re: MongoDB switches up its open source license
#88(Context: I worked on Compose/MongoHQ for a very long time. We were the first to monetize MongoDB) I'm sure people will get riled up about this, but it makes sense. Building a business on an OSS database in a world of behemoth cloud providers is really hard. It's clear Google and Amazon (and maybe even Azure) are comfy taking OSS work, doing a ton of proprietary development on it, and leaving the companies who did al…
"I'm sure people will get riled up about this, but it makes sense. Building a business on an OSS database in a world of behemoth cloud providers is really hard. It's clear Google and Amazon (and maybe even Azure) are comfy taking OSS work, doing a ton of proprietary development on it, and leaving the companies who did all the groundwork flailing in the wind. " This is simply not true in any meaningful way. Please cit…
AGPL was a roundabout way of hinting that cloud providers should kick back some revenue and now that it didn't work the truth can come out.
Re: MongoDB switches up its open source license
#89(Context: I worked on Compose/MongoHQ for a very long time. We were the first to monetize MongoDB) I'm sure people will get riled up about this, but it makes sense. Building a business on an OSS database in a world of behemoth cloud providers is really hard. It's clear Google and Amazon (and maybe even Azure) are comfy taking OSS work, doing a ton of proprietary development on it, and leaving the companies who did al…
> exploit permissive licenses to the max I feel like many people deciding to use an open source license for their project never consider the consequences of such choice. They use OSS because it's "cool" or they hope to get some free work done for them. If you pick an open source license and someone uses your code to build something else within the license boundaries, that is not a Bad Thing(tm). I have released many…
I might say instead that the norms of open source software development -- attribution, collaboration, good faith -- are so baked in to small, high-trust communities that they might seem as though they'll be obvious to everyone. And then your software makes it way to the public and you realize that those were just assumptions and not written into the letter of agreement at any point.
I'm speaking as an outside observer on this.
Re: MongoDB switches up its open source license
#90This is just another highlight of the cloud vendors making it very difficult to build a business based on open source infrastructure software. Either you pick an infectious license (like AGPL) or you go open core. Otherwise, if your project gets popular, the cloud providers will offer it as a service, which will eat into your revenue.