MongoDB Major Change to Licensing
-
The basic tenants of open source licensing has always been that you be allowed to operate the product. But the MongoDB license restricts, heavily, the ability to use the software.
This is what is unique. Before, all licenses that addressed this talked about contributing back from products that use the code not the binaries. This is a binary use restriction that is unique and a show stopper.
It also means that, for example, if you wanted to host some software for your users, and you connected it to MongoDB, that you are forced to release that code - even if you didn't write it or have rights to it! See the difficulty here?
-
@DustinB3403 said in MongoDB Major Change to Licensing:
@scottalanmiller said in MongoDB Major Change to Licensing:
@DustinB3403 said in MongoDB Major Change to Licensing:
No. . . only if I was selling a service that used MongoDB as the backend would I be forced to purchase a license or Open Source everything. If I ran a mongoDB internally and not sold it as a service I wouldn't have to contribute or open a single line of code for whatever I built internally that uses MongoDB.
You sure? "As a service" doesn't imply selling it to third parties. Software is delivered "as a service" internally, too. And it's not just selling, but using. This license is broad, very broad. So broad that I think you might be completely missing how it risks tainting literally everything.
This change specifically targets MongoDB as a service that a (not mongoDB company) is selling a service and profiting from.
No, that's not what it targets, hence the entire concern.
-
@tonyshowoff said in MongoDB Major Change to Licensing:
@DustinB3403 said in MongoDB Major Change to Licensing:
@scottalanmiller said in MongoDB Major Change to Licensing:
@DustinB3403 said in MongoDB Major Change to Licensing:
No. . . only if I was selling a service that used MongoDB as the backend would I be forced to purchase a license or Open Source everything. If I ran a mongoDB internally and not sold it as a service I wouldn't have to contribute or open a single line of code for whatever I built internally that uses MongoDB.
You sure? "As a service" doesn't imply selling it to third parties. Software is delivered "as a service" internally, too. And it's not just selling, but using. This license is broad, very broad. So broad that I think you might be completely missing how it risks tainting literally everything.
This change specifically targets MongoDB as a service that a (not mongoDB company) is selling a service and profiting from.
Intent isn't the same thing as result, especially if you scare people away with vague language
Sure, I agree wholeheartedly. But the conversation and license change is specifically businesses who are using MongoDB as a backend to whatever service they are selling to a customer.
It's targeting profitiers, not internal uses.
-
Look at it like this, imagine if Linux changed its license and said that in order to install software on Linux, you had to provide the source code back to Linux.
That means that end users, who don't make the code, would have no reasonable means and often no possibly means of running software. Because the license requires the end users to do things, not just developers working with the original code. While legal, it's effectively impossible to then use the product.
-
@DustinB3403 said in MongoDB Major Change to Licensing:
@tonyshowoff said in MongoDB Major Change to Licensing:
@DustinB3403 said in MongoDB Major Change to Licensing:
@scottalanmiller said in MongoDB Major Change to Licensing:
@DustinB3403 said in MongoDB Major Change to Licensing:
No. . . only if I was selling a service that used MongoDB as the backend would I be forced to purchase a license or Open Source everything. If I ran a mongoDB internally and not sold it as a service I wouldn't have to contribute or open a single line of code for whatever I built internally that uses MongoDB.
You sure? "As a service" doesn't imply selling it to third parties. Software is delivered "as a service" internally, too. And it's not just selling, but using. This license is broad, very broad. So broad that I think you might be completely missing how it risks tainting literally everything.
This change specifically targets MongoDB as a service that a (not mongoDB company) is selling a service and profiting from.
Intent isn't the same thing as result, especially if you scare people away with vague language
Sure, I agree wholeheartedly. But the conversation and license change is specifically businesses who are using MongoDB as a backend to whatever service they are selling to a customer.
It's targeting profitiers, not internal uses.
Let's say that's accurate, fine, but we're already moving to another key-value store in our product because of this (among other reasons but this is a good reason to never look back) and also the potential for it to get worse. What if they decided to further lock that down based on some other reason or decided to suddenly start trying to license to closed source products/services that simply use it so they can make money from that?
-
@DustinB3403 said in MongoDB Major Change to Licensing:
@tonyshowoff said in MongoDB Major Change to Licensing:
@DustinB3403 said in MongoDB Major Change to Licensing:
@scottalanmiller said in MongoDB Major Change to Licensing:
@DustinB3403 said in MongoDB Major Change to Licensing:
No. . . only if I was selling a service that used MongoDB as the backend would I be forced to purchase a license or Open Source everything. If I ran a mongoDB internally and not sold it as a service I wouldn't have to contribute or open a single line of code for whatever I built internally that uses MongoDB.
You sure? "As a service" doesn't imply selling it to third parties. Software is delivered "as a service" internally, too. And it's not just selling, but using. This license is broad, very broad. So broad that I think you might be completely missing how it risks tainting literally everything.
This change specifically targets MongoDB as a service that a (not mongoDB company) is selling a service and profiting from.
Intent isn't the same thing as result, especially if you scare people away with vague language
Sure, I agree wholeheartedly. But the conversation and license change is specifically businesses who are using MongoDB as a backend to whatever service they are selling to a customer.
It's targeting profitiers, not internal uses.
No actually, it is not and that is the prblem. They might have WANTED to do that. but they did not.
-
@DustinB3403 said in MongoDB Major Change to Licensing:
@tonyshowoff said in MongoDB Major Change to Licensing:
@DustinB3403 said in MongoDB Major Change to Licensing:
@scottalanmiller said in MongoDB Major Change to Licensing:
@DustinB3403 said in MongoDB Major Change to Licensing:
No. . . only if I was selling a service that used MongoDB as the backend would I be forced to purchase a license or Open Source everything. If I ran a mongoDB internally and not sold it as a service I wouldn't have to contribute or open a single line of code for whatever I built internally that uses MongoDB.
You sure? "As a service" doesn't imply selling it to third parties. Software is delivered "as a service" internally, too. And it's not just selling, but using. This license is broad, very broad. So broad that I think you might be completely missing how it risks tainting literally everything.
This change specifically targets MongoDB as a service that a (not mongoDB company) is selling a service and profiting from.
Intent isn't the same thing as result, especially if you scare people away with vague language
Sure, I agree wholeheartedly. But the conversation and license change is specifically businesses who are using MongoDB as a backend to whatever service they are selling to a customer.
It's targeting profitiers, not internal uses.
You just completely changed how you thought it was targeted. First it was MongoDB as a service. Not it's "all software" as a service. that's a whopping change.
-
@DustinB3403 said in MongoDB Major Change to Licensing:
It's targeting profitiers, not internal uses.
Those are one and the same. No one runs software internally if not for profit from doing so. You can't find a way to differentiate these two.
-
@JaredBusch said in MongoDB Major Change to Licensing:
@DustinB3403 said in MongoDB Major Change to Licensing:
@tonyshowoff said in MongoDB Major Change to Licensing:
@DustinB3403 said in MongoDB Major Change to Licensing:
@scottalanmiller said in MongoDB Major Change to Licensing:
@DustinB3403 said in MongoDB Major Change to Licensing:
No. . . only if I was selling a service that used MongoDB as the backend would I be forced to purchase a license or Open Source everything. If I ran a mongoDB internally and not sold it as a service I wouldn't have to contribute or open a single line of code for whatever I built internally that uses MongoDB.
You sure? "As a service" doesn't imply selling it to third parties. Software is delivered "as a service" internally, too. And it's not just selling, but using. This license is broad, very broad. So broad that I think you might be completely missing how it risks tainting literally everything.
This change specifically targets MongoDB as a service that a (not mongoDB company) is selling a service and profiting from.
Intent isn't the same thing as result, especially if you scare people away with vague language
Sure, I agree wholeheartedly. But the conversation and license change is specifically businesses who are using MongoDB as a backend to whatever service they are selling to a customer.
It's targeting profitiers, not internal uses.
No actually, it is not and that is the prblem. They might have WANTED to do that. but they did not.
Right, what their intent was is not clear, but they claim that that was their intent. But what they did isn't that, and is so far from that, that it doesn't seem plausible to believe it was their intention.
-
@tonyshowoff said in MongoDB Major Change to Licensing:
@DustinB3403 said in MongoDB Major Change to Licensing:
@tonyshowoff said in MongoDB Major Change to Licensing:
@DustinB3403 said in MongoDB Major Change to Licensing:
@scottalanmiller said in MongoDB Major Change to Licensing:
@DustinB3403 said in MongoDB Major Change to Licensing:
No. . . only if I was selling a service that used MongoDB as the backend would I be forced to purchase a license or Open Source everything. If I ran a mongoDB internally and not sold it as a service I wouldn't have to contribute or open a single line of code for whatever I built internally that uses MongoDB.
You sure? "As a service" doesn't imply selling it to third parties. Software is delivered "as a service" internally, too. And it's not just selling, but using. This license is broad, very broad. So broad that I think you might be completely missing how it risks tainting literally everything.
This change specifically targets MongoDB as a service that a (not mongoDB company) is selling a service and profiting from.
Intent isn't the same thing as result, especially if you scare people away with vague language
Sure, I agree wholeheartedly. But the conversation and license change is specifically businesses who are using MongoDB as a backend to whatever service they are selling to a customer.
It's targeting profitiers, not internal uses.
Let's say that's accurate, fine, but we're already moving to another key-value store in our product because of this (among other reasons but this is a good reason to never look back) and also the potential for it to get worse. What if they decided to further lock that down based on some other reason or decided to suddenly start trying to license to closed source products/services that simply use it so they can make money from that?
Again, I agree, but I'm stating what the license change is stating. It's targeting businesses that use MongoDB as a backend for whatever service they are selling to a third party.
Either open the source for the service you sell, or buy a license.
-
@DustinB3403 said in MongoDB Major Change to Licensing:
@tonyshowoff said in MongoDB Major Change to Licensing:
@DustinB3403 said in MongoDB Major Change to Licensing:
@tonyshowoff said in MongoDB Major Change to Licensing:
@DustinB3403 said in MongoDB Major Change to Licensing:
@scottalanmiller said in MongoDB Major Change to Licensing:
@DustinB3403 said in MongoDB Major Change to Licensing:
No. . . only if I was selling a service that used MongoDB as the backend would I be forced to purchase a license or Open Source everything. If I ran a mongoDB internally and not sold it as a service I wouldn't have to contribute or open a single line of code for whatever I built internally that uses MongoDB.
You sure? "As a service" doesn't imply selling it to third parties. Software is delivered "as a service" internally, too. And it's not just selling, but using. This license is broad, very broad. So broad that I think you might be completely missing how it risks tainting literally everything.
This change specifically targets MongoDB as a service that a (not mongoDB company) is selling a service and profiting from.
Intent isn't the same thing as result, especially if you scare people away with vague language
Sure, I agree wholeheartedly. But the conversation and license change is specifically businesses who are using MongoDB as a backend to whatever service they are selling to a customer.
It's targeting profitiers, not internal uses.
Let's say that's accurate, fine, but we're already moving to another key-value store in our product because of this (among other reasons but this is a good reason to never look back) and also the potential for it to get worse. What if they decided to further lock that down based on some other reason or decided to suddenly start trying to license to closed source products/services that simply use it so they can make money from that?
Again, I agree, but I'm stating what the license change is stating. It's targeting businesses that use MongoDB as a backend for whatever service they are selling to a third party.
Either open the source for the service you sell, or buy a license.
The first part of that sentence says "make the functionality of the program[...]available to third parties" so even API access of any sort applies
-
@scottalanmiller said in MongoDB Major Change to Licensing:
@DustinB3403 said in MongoDB Major Change to Licensing:
It's targeting profitiers, not internal uses.
Those are one and the same. No one runs software internally if not for profit from doing so. You can't find a way to differentiate these two.
Sure I can, MongoDB and my company "Dustin's Dough" have a database.
My customers aren't accessing that database. Hence no third party, hence no need to open source everything or purchase a license.
-
@DustinB3403 said in MongoDB Major Change to Licensing:
@scottalanmiller said in MongoDB Major Change to Licensing:
@DustinB3403 said in MongoDB Major Change to Licensing:
It's targeting profitiers, not internal uses.
Those are one and the same. No one runs software internally if not for profit from doing so. You can't find a way to differentiate these two.
Sure I can, MongoDB and my company "Dustin's Dough" have a database.
My customers aren't accessing that database. Hence no third party, hence no need to open source everything or purchase a license.
That's my point about vague language, again let's say that's protected and the intent, it's fairly easy to make an argument especially to non-technical arbiters or other legal-minded people that because the customer used your software and your software accesses the database, therefore your customers are.
-
@scottalanmiller said in MongoDB Major Change to Licensing:
If you make the functionality of the Program or a modified version available to third parties as a service...
Here is where things get tricky...
-
Define third parties in the IT world. This license applies to IT, not to the developers. This is new ground for licensing and really hard. Does an MSP hosting your software for you qualify as a third party? What about a colocation facility? What about a database as a service vendor? What about your IT department? What if that IT department is staffed by contractors rather than employees? I wrote last year about why internal IT was still a third party. This is a grey area requirement that could potentially sweep up nearly anyone and everyone using the product.
-
Define "as a service." What software isn't delivered to end users as a server? None. Because that's just how software is. At the end of the day, IT provides software as a service to the end users of the company. If you are a one man show, you still do this to yourself. So this is a meaningless phrase here. Everyone is caught by this portion if they want them to be.
So the question is... is there anyone, anywhere, that can use MongoDB and be confident that they can't be caught by the clause?
-
-
@tonyshowoff said in MongoDB Major Change to Licensing:
@DustinB3403 said in MongoDB Major Change to Licensing:
@scottalanmiller said in MongoDB Major Change to Licensing:
@DustinB3403 said in MongoDB Major Change to Licensing:
It's targeting profitiers, not internal uses.
Those are one and the same. No one runs software internally if not for profit from doing so. You can't find a way to differentiate these two.
Sure I can, MongoDB and my company "Dustin's Dough" have a database.
My customers aren't accessing that database. Hence no third party, hence no need to open source everything or purchase a license.
That's my point about vague language, again let's say that's protected and the intent, it's fairly easy to make an argument especially to non-technical arbiters or other legal-minded people that because the customer used your software and your software accesses the database, therefore your customers are.
Right, exactly, if you use this for your internal CRM, and your CRM helps you close sales, and closing sales makes you money, you've made money from the services of MongoDB. Now that closed source CRM you bought... legally you have to buy the company and open source their product which might cost you billions!
-
@DustinB3403 said in MongoDB Major Change to Licensing:
@scottalanmiller said in MongoDB Major Change to Licensing:
@DustinB3403 said in MongoDB Major Change to Licensing:
It's targeting profitiers, not internal uses.
Those are one and the same. No one runs software internally if not for profit from doing so. You can't find a way to differentiate these two.
Sure I can, MongoDB and my company "Dustin's Dough" have a database.
My customers aren't accessing that database. Hence no third party, hence no need to open source everything or purchase a license.
That clearly doesn't clearly protect you. And what about the internal users?
-
@tonyshowoff said in MongoDB Major Change to Licensing:
@DustinB3403 said in MongoDB Major Change to Licensing:
@scottalanmiller said in MongoDB Major Change to Licensing:
@DustinB3403 said in MongoDB Major Change to Licensing:
It's targeting profitiers, not internal uses.
Those are one and the same. No one runs software internally if not for profit from doing so. You can't find a way to differentiate these two.
Sure I can, MongoDB and my company "Dustin's Dough" have a database.
My customers aren't accessing that database. Hence no third party, hence no need to open source everything or purchase a license.
That's my point about vague language, again let's say that's protected and the intent, it's fairly easy to make an argument especially to non-technical arbiters or other legal-minded people that because the customer used your software and your software accesses the database, therefore your customers are.
What?
This seems pretty straightforward to me. If you have a service of some kind that you sell directly to a third party (not mongoDB and not for internal purposes) then either purchase a license or open source the entire service.
Yes it's insane.
But nothing here states that if you offer a service, and use it internally and no paying customer is accessing, then there is no need to open source anything or purchase a license.
-
@scottalanmiller said in MongoDB Major Change to Licensing:
@DustinB3403 said in MongoDB Major Change to Licensing:
@scottalanmiller said in MongoDB Major Change to Licensing:
@DustinB3403 said in MongoDB Major Change to Licensing:
It's targeting profitiers, not internal uses.
Those are one and the same. No one runs software internally if not for profit from doing so. You can't find a way to differentiate these two.
Sure I can, MongoDB and my company "Dustin's Dough" have a database.
My customers aren't accessing that database. Hence no third party, hence no need to open source everything or purchase a license.
That clearly doesn't clearly protect you. And what about the internal users?
Internal users aren't paying customers! FFS!
@JaredBusch get in here.
-
@DustinB3403 said in MongoDB Major Change to Licensing:
@tonyshowoff said in MongoDB Major Change to Licensing:
@DustinB3403 said in MongoDB Major Change to Licensing:
@tonyshowoff said in MongoDB Major Change to Licensing:
@DustinB3403 said in MongoDB Major Change to Licensing:
@scottalanmiller said in MongoDB Major Change to Licensing:
@DustinB3403 said in MongoDB Major Change to Licensing:
No. . . only if I was selling a service that used MongoDB as the backend would I be forced to purchase a license or Open Source everything. If I ran a mongoDB internally and not sold it as a service I wouldn't have to contribute or open a single line of code for whatever I built internally that uses MongoDB.
You sure? "As a service" doesn't imply selling it to third parties. Software is delivered "as a service" internally, too. And it's not just selling, but using. This license is broad, very broad. So broad that I think you might be completely missing how it risks tainting literally everything.
This change specifically targets MongoDB as a service that a (not mongoDB company) is selling a service and profiting from.
Intent isn't the same thing as result, especially if you scare people away with vague language
Sure, I agree wholeheartedly. But the conversation and license change is specifically businesses who are using MongoDB as a backend to whatever service they are selling to a customer.
It's targeting profitiers, not internal uses.
Let's say that's accurate, fine, but we're already moving to another key-value store in our product because of this (among other reasons but this is a good reason to never look back) and also the potential for it to get worse. What if they decided to further lock that down based on some other reason or decided to suddenly start trying to license to closed source products/services that simply use it so they can make money from that?
Again, I agree, but I'm stating what the license change is stating. It's targeting businesses that use MongoDB as a backend for whatever service they are selling to a third party.
Either open the source for the service you sell, or buy a license.
Yes, we get the requirement. It's always "buy a license." We aren't saying they offer no means of using their product. It's that they offer no reasonable one and that everyone should consider abandoning MongoDB completely as this is so limiting.
-
@DustinB3403 said in MongoDB Major Change to Licensing:
@scottalanmiller said in MongoDB Major Change to Licensing:
@DustinB3403 said in MongoDB Major Change to Licensing:
@scottalanmiller said in MongoDB Major Change to Licensing:
@DustinB3403 said in MongoDB Major Change to Licensing:
It's targeting profitiers, not internal uses.
Those are one and the same. No one runs software internally if not for profit from doing so. You can't find a way to differentiate these two.
Sure I can, MongoDB and my company "Dustin's Dough" have a database.
My customers aren't accessing that database. Hence no third party, hence no need to open source everything or purchase a license.
That clearly doesn't clearly protect you. And what about the internal users?
Internal users aren't paying customers! FFS!
@JaredBusch get in here.
Sometimes not, sometimes they are, but why does that matter? The license doesn't say paying customers, you said that. But it's not a factor here.
Nearly all internal users are paying customers in real businesses, how could they not be?
