18 ms·
MongoDB removed from RHEL 8 beta due to license
- hardwaresofton 8y agoSomewhat orthogonal but I wonder if this is one of those times where people in forums like these can see further ahead than the usual stock market actors can? $MDB seems to be unaffected by this news (and the DocumentDB news as well). Maybe I've overestimating, but this looks like it will be a blow to accessibility of Mongo -- or maybe it will only be RHEL since they're focused on commercial applications? [EDIT] - I was incorrect/didn't look closely enough, the DocumentDB annoucement seems to be correlated with a 20%+ dip around January 8th.
- cmsj 8y agoIf RHEL is dropping something for license reasons, you can be pretty sure that others will too: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915537#15 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915537#15
- avar 8y agoIt looks like it is, but is there any official word that the SSPL is proprietary? As far as I know MongoDB claims it isn't, and it hasn't been reviewed officially by either the FSF or the OSI. Is it in license purgatory?
- choeger 8y agoI don't know if it can be called free. But section 13 of the SSPL is certainly incompatible to RHEL's distribution model, or any other linux distribution I know of. In particular it requires you to license "the Corresponding Source for all programs that you use to make the Program or modified version available as a service" under the SSPL. That naturally includes the linux kernel which is licensed under the GPL - and cannot be simply relicensed.
- fuzzy2 8y agoBut they don't make it available as a service. They distribute binaries and perhaps source code.
- avar 8y agoFree software must be free for all its users. The most common example of this is a license that restrict fields of endeavor. E.g. I could make a license exactly like the GPL except with a clause saying fuzzy2 on HN can't use my software without paying me. Even though RedHat and Debian aren't fuzzy2 on HN, and 99.99...% (or 100%) of their users aren't that user either, they'd still refuse to distribute it. That license would be non-free.
- mikekchar 8y agoI think the parent was commenting that since Red Hat did not offer a service, there is no legal restriction in distributing the code. In other words, if Red Hat decided to change its stance on distributing only free software, they could do so legally. I'm glad they didn't, but I think the parent is correct. Edit: Usually don't complain about down votes, but I'd be happy to hear why the parent is incorrect if I've got it wrong. Are they not legally able to distribute for some reason? Re-Edit: I read the initial query incorrectly. Yes, the parent's post is unrelated to the query. Sorry!
- marcosdumay 8y agoThere is plenty of non-free software that a distro can legally distribute. They still usually don't, because it would break the automatically trouble-free property of their distribution. If users have to check the license of software before using them, there is little point in packaging all of it together and automatically installing, so there is little point on making a distro at all.
- jabl 8y agoSeems redhat lawyers have reviewed it, here's the announcement wrt fedora: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/IQIOBOGWJ247JGKX2WD6N27TZNZZNM6C/ https://lists.fedoraproject.org/archives/list/devel@lists.fe...
- vbezhenar 8y agoIf I understood that message correctly, it seems that Debian decided to remove MongoDB from its main repository as well: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915537#15 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915537#15
- mikekchar 8y agoIt's really not clear to me as he kind of backtracked in the next message by saying that he was writing under the role in the FTP team, rather than as Project Leader of Debian. My interpretation of that is that it is his opinion, but not a statement of policy. I'd be pretty surprised if they allow SSPL in Debian, but I don't think this is the statement that disallows it.
- tinus_hn 8y agoThe FTP team performs a license check before a package is moved into the archive, so they do get to decide what goes in and what doesn’t.
- deleted 8y ago[deleted]
- geofft 8y agoThe FTP team is the body that ordinarily makes binding policy decisions about licenses in Debian. It's not typically the project leader's job, so I read this statement as saying "despite the .signature, I'm speaking in my role as a member of the FTP team, not the project leader overruling the FTP team."
- dankohn1 8y agoBruce Perens feels “it manifests a lot of ignorance about Open Source and utter contempt for our community.” https://opensource.org/LicenseReview122018 https://opensource.org/LicenseReview122018
- withhighprod 8y agoYea without such ignorance, you got bullied by big brothers: AWS and Alibaba
- latk 8y agoThat Perens quote refers specifically to Sunil Deshpande's article about the SSPL and Open Source, not to the SSPL itself. But it's not far off either way… The reaction on the OSI's license-review list is more varied. Lawrence Rosen and Ken Mitchell argue that the license should be approved. Everyone else is criticizing that it clearly violates the spirit of Open Source software (no discrimination against fields of endeavour!), and that the license is too broad and too vague in the critical section (Rosen agrees with the latter part). Carlo Piana points out that the goal of the license seems to be to create so much legal uncertainty that any serious user would be forced to buy a proprietary license from MongoDB.
- dankohn1 8y agoThanks for the insightful summary.
- kemitchell 8y agoI also criticize the way SSPL was drafted. The legal talent they have can do far better. The choice to patch AGPL cuffed them. Here's me announcing an attempt at a plain-language, SSPL-style license from scratch: https://writing.kemitchell.com/2019/01/12/Shared-Component-License.html https://writing.kemitchell.com/2019/01/12/Shared-Component-L... The latest license text is at: https://github.com/kemitchell/shared-component-license https://github.com/kemitchell/shared-component-license
- hannob 8y agoAnyone surprised? Of course you can choose a non-free license for your code, but it comes with consequences. One of them is that Linux distributions that value free licenses will no longer act as your distributor.
- viach 8y agoThis comment sounds like RHEL's license is more 'free' than Mongo's, which is not the case, imho.
- ergo14 8y agoReally? It's so non-free that you have CentOS.
- bubblethink 8y agoYes, but as a customer of RH, you are not allowed to distribute RH's binaries, or they will terminate your contract. That is also against the spirit of the GPL, although not necessarily the letter. You can take the source, remove the branding, recompile, and redistribute, which is similar to what CentOS does/used to. However, the GPL allows the former too. i.e., You can straight up distribute the binaries under GPL.
- timdierks 8y agoThis is simply not true: it's explicitly not the intent of the GPL, and furthermore the GPL is clearly a contract which explicitly spells out its intent, not a vague document whose spirit needs to be interpreted.
- bubblethink 8y agoIt is explicit in the freedoms it grants you, one of which being the freedom to distribute copies. The intent is pretty clear. The RH workaround to that is that if you exercise this freedom, they will not do business with you in the future. You got to exercise your freedom, but only once. The GPL doesn't have recourse for that.
- preinheimer 8y agoThis seems like a non-issue to me...? The installation instructions I've always followed for MongoDB start with importing a key, and adding their official repo to my source list. I'm a debian user, but their redhat installation instructions are similar: https://docs.mongodb.com/manual/tutorial/install-mongodb-on-red-hat/ https://docs.mongodb.com/manual/tutorial/install-mongodb-on-... I guess it will be a small speed bump for people experimenting their first time, but I've never had any concerns about using a vendor provided source for packages (third party provided ones are a different story.)
- pilif 8y ago> The installation instructions I've always followed for MongoDB start with importing a key, and adding their official repo to my source list. Going with the maintainer's repo means that you trust the maintainer with providing security updates for the version you have installed or you trust them with providing a useable upgrade path. If you go with a distro package, you will get both the benefits of security updates for the lifetime of the OS itself and the benefits of the underlying software not changing. Of course it also means that you don't get new features for the lifetime of the OS. So depending on your target usage of MongoDB, you either would want to go with the OS packages (if MongoDB is just a dependency of a dependency and you don't really care about its functionality aside of it being there) or with the vendor packages (if you're directly depending on MongoDB and you're willing to keep up to date with feature releases). But even then, sometimes a vendor's official response to a security problem is "run apt-get upgrade to update to the latest major release" at a time when you really don't have the time to read the release notes and adopt your software to the changes in the new version. Other vendors still provide maintenance for older releases, so it really depends on the vendor, whereas if you go with the OS packages, none of this matters. Also, in this particular case, there's also the licensing issue to consider. I don't know whether it's safe for a company offering some service and/or application over the web to use current versions of MongoDB without paying for a license.
- iqy 8y ago>Going with the maintainer's repo means that you trust the maintainer with providing security updates for the version you have installed or you trust them with providing a useable upgrade path. Why should that be a problem if you use the official repo, handled by MongoDB themselves?
- giancarlostoro 8y agoIt seems[0] the new MongoDB license is basically non-free and it would make no sense to include it in RHEL8. I hope Debian and other distros follow suit as a result if they come in agreement. It's sad that the license change all resorts to greed basically, as if Oracle took over MongoDB. If I were to ever use a NoSQL database for a new project I'd aim for MIT / 2-clause BSD based projects instead. PostgreSQL has no issue being BSD-like licensed (all this time I thought it was BSD or MIT, turns out it's a similar license instead). It saddens me RethinkDB couldn't compete more with MongoDB. [0]: https://news.ycombinator.com/item?id=18919728 https://news.ycombinator.com/item?id=18919728
- hannob 8y ago> It's sad that the license change all resorts to greed basically, as if Oracle took over MongoDB. It's essentially "we convinced the stock market that our company tripled in value over the course of a year, and now we have to tell them what business model is behind this value growth" [1]. [1] https://finance.yahoo.com/quote/MDB/?guccounter=1 https://finance.yahoo.com/quote/MDB/?guccounter=1
- iqy 8y agoIf the new MongoDB licence is non-free, the chances that Debian will include that software in their repos are nil.
- vbezhenar 8y agoAFAIK there's non-free repo in Debian. Not sure how they compared to main repo in terms of maintaining.
- Twirrim 8y agoI think Debian would keep it around, probably, but it'll be punted out of the main repos and in to the ones designated for non-free software. Impact on the end user will likely be minimal. They'll still be able to apt-get install it as before.
- ploxiln 8y agoThey will probably keep the last version before the license change for a while, and probably add minor community-sourced patches. The next version of ubuntu will include mongdb version "3.6.9+really3.6.8+90~g8e540c0b6d" which you can see means "last commit before the license change"
- sascha_sl 8y agoMongoDB is the reason I don't contribute (outside of work) to any copyleft project that asks for copyright assignment anymore.
- nathell 8y agoCare to elaborate?
- mbreese 8y agoIf you have a project that accepts code from outside contributors, you can only re-license the project iff you have a copyright assignment from all of the outside contributors. This is because by default, new code from an outside contributor is only granted to the original project under the original license and the copyright is owned by the contributor. If the company managing the project wants to change the license, they would need to contact each contributor and get a new license (unlikely), or remove the code from the project (equally unlikely). However, if the company only accepts patches or code that also includes a copyright assignment, the company can change the license to whatever they want without any input from their contributors.
- quotemstr 8y agoEh. I still trust the FSF to get this basically right.
- jillesvangurp 8y agoIt's a fair point to make: mandatory copyright transfer in combination with copyleft means the copyright holder can at any moment decide to change the license. Not retroactively of course, but you'd be left with the choice to fork, to buy a license, or abandon the product. None of those are great options for anyone serious about making a contribution. Copyleft can work great but it works better if the copyright stays with the original authors. This makes it impractical to re-license because you need all copyright holders to agree to that, which in the case of most OSS projects is virtually impossible. Imagine tracking down everyone who ever contributed to Linux. Not going to happen. And as Oracle has learned the hard way, forking is what happens if you mess up. Copyleft serves users of the software. IMHO the long term success of OSS projects requires a diverse community of contributors. If a project has value, people and companies will step up to keep it going. Companies don't last forever and their fortunes or priorities might change. Having copyright transfers basically means one company calls all the shots and if it suffers, their software and its wider community suffers. This dis-incentivizes externals to contribute; weakens the community; and can become a problem for projects being long term sustainable or indeed profitable as most of the burden of maintenance is for the sole copyright holder. Of course it's not too late for MongoDB to swallow their pride and fix this PR disaster. Lets be frank, all this negative news around their product has got to be unpleasant for them and their shareholders. At least, I doubt that they expected or wanted this to happen and I think they should be bracing for more bad news when e.g. some of their big accounts start eyeing competing products because of this mess. The fix is obvious: move the other way and go with a business and customer friendly license (Apache 2.0 seems to be popular for this) combined with closed source components/add ons for commercial customers.
- pytyper2 8y agoGood, Mongo is rarely the right database.
- TimMurnaghan 8y agoAbsolutely. My characterization of Mongo is that it's the back end choice of front end developers. The only possible justification for it could be time to MVP (and that's being kind). It's bad for all of the reasons that back-end people make back-end choices - non-functional requirements like operability, clustering, etc. Hopefully this is the start of it being removed from any infrastructure uses. I spun up an openstack instance the other day and was horrified to find Mongo in there.
- pytyper2 8y agoThe only time it was recommended to me was by a new NodeJS developer, I then explained ACID concepts around multiple transactions, they were floored. This was about 4 years ago, maybe mongo has matured?
- merlynn 8y agoMichael from MongoDB here... Yep - MongoDB has continued to mature. Modern MongoDB supports multi-document ACID transactions if that's what you're asking. More information here - https://www.mongodb.com/blog/post/mongodb-multi-document-acid-transactions-general-availability https://www.mongodb.com/blog/post/mongodb-multi-document-aci...
- threeseed 8y agoActually the NFRs are one of the best parts of MongoDB. It is by far one of the easiest databases to administer, clustering is orders of magnitude easer than say PostgreSQL and it can be the fastest database by far for certain use cases e.g. cell level updates. Can you be more specific about what in particular is deficient ? And if you look at their customers most of them aren't using it for front end work. Likewise I find it to be quite popular in the Data Analytics/Science space as a store of analytical features and for 360 entity views.
- manishsharan 8y agoIs any OSS project working on MongoDB API layer for FoundationDB ?
- jsty 8y agoThe document layer offers this: https://www.foundationdb.org/blog/announcing-document-layer/ https://www.foundationdb.org/blog/announcing-document-layer/
- ehayes 8y agoIt's a little ironic because Red Hat invested in MongoDB several times: https://www.crunchbase.com/organization/red-hat/investments/investments_list https://www.crunchbase.com/organization/red-hat/investments/...
- amenod 8y agoI am really torn about this news. On one hand MongoDB's change of license is a clear attempt to discriminate against a set of users, so it is clearly non-free. On the other hand I know it is really difficult to make a sustainable business by developing an opensource product, especially since there are companies (like Amazon) who will take successful opensource projects and offer them as a service, or simply offer a compatible service (which is what Amazon did now). Discriminating against such uses doesn't seem wrong to me since they clearly harm the creators and maintainers in their effort to actually make some income from the project. There is a really limited set of options for opensource companies and I have yet to see an opensource product that would bring their creators enough money to sustain it on aything else than their goodwill. RedHat doesn't count, because they packaged other people's opensource and sold the package to enterprise. They did contribute back and even started and maintained some of the projects (which makes them "good guys" in my eyes), but any other opensource project will have difficulties replicating that success. EDIT: I would really appreciate discussion instead of (down)votes.
- kstrauser 8y agoPostgreSQL is used much more widely than MongoDB, and has a much freer license. Lots of people make money developing and supporting PostgreSQL. I also content that MongoDB built their project on top of a mountain of Free Software. It rings a little hollow to me when they complain that others are making money from using their software, when the MongoDB team is also making money from using others' software. Last I checked, they weren't a major contributor to the Linux kernel, or GNU, or GCC, or Emacs/Vim, or...
- threeseed 8y ago> Last I checked, they weren't a major contributor to the Linux kernel, or GNU, or GCC, or Emacs/Vim MongoDB only needs the Linux kernel/GNU/GCC when it's running or compiling on Linux. On OSX and Windows it uses other toolchains. And your point goes against the entire spirit of open source. No one should be forced to contribute back to open source less they be criticised by the community.
- nwmcsween 8y agoThis is rich coming from Redhat that does shady things with subscription license agreements and open-source software.
- jhall1468 8y agoNothing Redhat does is shady. There's nothing wrong with license agreements for closed source software, or even license-agreements that support open source software. The latter is how open source companies make money.
- nwmcsween 8y agoThe license agreements restrict use of the work on top of the GPL, same as mongo does..
- jhall1468 8y agoNo, the Mongo license explicitly forbids cloud providers from using the software without open sourcing the entire stack. Unless you have an example of Red Hat doing the same, I'd retract the statement.
- nwmcsween 8y agoAnd the Redhat service license restricts redistribution of the binaries and modifications or you get blacklisted and cannot get any updates
- withhighprod 8y agoShould we blame AWS for this?
- zzzcpan 8y agoMongoDB, Redis, CockroachDB and anyone else interested should join efforts with Kyle and adopt his similar to SSPL, but neutral and cleaner copyleft Shared Component License [1]. This should help clear up any confusion people have and avoid providing excuses for removing packages due to the license. [1] https://github.com/kemitchell/shared-component-license https://github.com/kemitchell/shared-component-license
- yarrel 8y agoThat's not a free software license though.
- kemitchell 8y agoI'm not sure what reason you have in mind. FSF and OSI are split on "private changes": whether a copyleft license can require distribution of changes. OSI approved Plan 9, RPL, and Open Watcom, all of which require this in at least some scenarios. FSF rejects those license. I don't understand why FSF takes that position. More on that: https://writing.kemitchell.com/2018/09/17/Private-Changes.html https://writing.kemitchell.com/2018/09/17/Private-Changes.ht...
- kemitchell 8y agoThanks for this mention! However, folks should be aware that it's very early days for that form. I only published my draft this week. I'm receiving first feedback now. Several commits to master per day. That being said, I strongly recommend that folks interested in the license watch the repo, release-only if they prefer. I will tag prereleases.
- rjkennedy98 8y agoDoesn't Red Hat have a huge financial stake in MongoDB? Seems weird to do this if that's the case.
- nnq 8y ago...why would almost anyone using MongoDB care at all if it's included in a distro's set of default packages?! Don't we all always install software from repositories hosted by third parties? As long as the Mongo devs keep supporting RHEL, I'd see no problem for actual direct users of it. And SSPL sounds like a pretty good and sensible thing.
- nolok 8y agoIt may or may not matter for Ubuntu or Debian or most other distros, but the kind of users/companies/customers that insist on using RHEL very much care about it. The whole point of using RHEL is that it has full support, why pay the premium for it if you then include non supported gears into it anyway.
- tracker1 8y agoRedis is still there, didn't they do something similar?
- dvirsky 8y agoNo, just a few modules changes license (and were removed from distros). Redis itself remains BSD.
- zachruss92 8y agoI'm not super surprised that RHEL removed Mongo because of the licensing change. I don't completely understand why people getting upset about the licensing, however. As far as I know, MongoDB is still open source. If you are a hosting provider offering "MongoDB as a Service" the provider then needs to pay a licensing fee to Mongo. This seems ok to me, with the logic that MongoDB is a business that needs to make money. I am not an expert in licensing, but how is this any different than paying for a license of RHEL vs using CentOS? I'm genuinely curious as to how this is against open source beliefs.
- deleted 8y ago[deleted]
- e1ven 8y agoIt is not generally considered Open Source. The new license was rejected by the OSI, which is generally regarded as the defacto arbitrator of if something is OSS or not. It was also rejected by Red Hat and Debian as being not open source. There are various issues with the license, including the scope of what they considered tainted. You could read the mailing list archives on the subject, or there appears to be a summary at https://opensource.stackexchange.com/a/7523 https://opensource.stackexchange.com/a/7523 The newly submitted v2 of the license hasn't resolved (m)any of the problems that the OSI has raised, and isn't expected to be approved either.
- kemitchell 8y agoOSI has not rejected SSPL, v1 or v2. Mongo substituted for v2 in review, and v2 is still in debate. To my knowledge, OSI has never affirmatively rejected a license. A proposal to change its process to include rejection, which came up during SSPL review, remains pending.
- matthewmacleod 8y agoAs far as I know, MongoDB is still open source. If you are a hosting provider offering "MongoDB as a Service" the provider then needs to pay a licensing fee to Mongo. To me, those are two contradictory statements. The software is not open-source if its license restricts the purposes for which it can be used, QED.
- karolist 8y agoMongoDB is a strange company. I've downloaded their Compass software to visualise some throwaway JSON I had loaded in Mongo, gave my real email and here's the emails I was sent before I blocked their marketing account (allegedly someone named Alena) day 0 "Regarding your interest in MongoDB" day +1 "Alena with MongoDB in reply to your interest" day +3 "Alena with MongoDB making sure you're all set" day +7 "Alena from MongoDB reaching out" day +10 "Checking in from MongoDB" At which point I was completely speechless about this dumb spammy marketing attempt and just blocked the sender. Really guys? "I want to touch base with you again to see if we could provide you with additional information regarding our enterprise edition of MongoDB that you downloaded. Are you available to set up a call to learn more?" What the hell is that I never downloaded "enterprise MongoDB", it was Compass. I will never use anything from MongoDB, thanks Alena.
- stingraycharles 8y agoThis is a common practice, it's called "Drip Marketing", "Nurturing" or a few more other variations. It's completely automated, and it sounds like some template / tagging gone wrong. Lots of companies do it, and it's fairly effective.
- crb002 8y agoMDB stock is tanking. Hilarious knowing that some of the institutional investors are forcing MDB down the throats of their IT staff. https://fintel.io/so/us/mdb https://fintel.io/so/us/mdb
- gandutraveler 8y agoOff topic . But since we are talking about DBs. What's the default go-to choice of DB now a days?
- kemitchell 8y agoI recently published a sketch of a plain-language license generalizing the SSPL approach. Feedback of all kinds welcome! https://github.com/kemitchell/shared-component-license https://github.com/kemitchell/shared-component-license At a minimum, I think my language can make the issues clearer. Folks don't want to wade 12 sections deep into AGPLv3, much less a path to AGPLv3. I can't blame them.