Calling mongo open source now just dilutes what "open source" actually means. The organization even removed the submission of its license for approval by the OSI.
It's source available, and it's up to each person to decide whether that's good or bad.
I wasn't aware the licensing is more restrictive now.
There's room for a grey area, but I think that the parent's comment about how Mongo's license relates to the overwhelming majority of it's community to use it (in that, functionally, it doesn't) still pushes farther towards open source than it does proprietary with source-available.
In the application to software, Bruce Perrens most definitely did define ther term, based on the Debian Free Software Guidelines, and the Free Software Foundation's Three Freedoms definition of Free Software, in June 1997:
https://opensource.org/docs/osd
https://www.debian.org/social_contract#guidelines
https://perens.com/2017/09/26/on-usage-of-the-phrase-open-so...
The term was not previously used with regard to software, though the intelligence community have used the phrase "open sources" to refer to unclassified information.b
This is just not a true thing to say. See my other replies for examples from before 1997.
It's right that when a thread is submitted of a project falsely claiming to be open source, the HN community unfailingly tears it to shreds. We don't want the term to be cheapened into becoming meaningless. I don't see that the origins of the term are relevant.
Personally I tend to capitalise, I typically use Free and Open Source software to be more clear that I'm referring to free software as defined by the FSF, and open source as defined by the OSI. It's unfortunate that I've found this to be necessary, to close the door on obtuse misuse of these terms.
It's still better than free software, which invariably makes the uninitiated think of freeware.
Christine Peterson claims to have invented the term in 1998.
https://opensource.com/article/18/2/coining-term-open-source...
But at least this much is not true - we can see it being used, in context, at least as far back as 1996. I think people involved in this project at the time say it was a common term back then as well, but I can't find a reference for that now.
http://www.xent.com/FoRK-archive/fall96/0269.html
And they certainly don't own it - they wrote a whole article on their own website still available about how they don't own it!
https://opensource.org/pressreleases/certified-open-source.p...
And yes, Christine indeed invented the term, and folks from OSI gave it the current meaning by clearly defining it.
> I joined Caldera in November of 1995, and we certainly used "open source" broadly at that time. We were building software. I can't imagine a world where we did not use the specific phrase "open source software". And we were not alone. The term "Open Source" was used broadly by Linus Torvalds (who at the time was a student...I had dinner with Linus and his then-girlfriend Ute in Germany while he was still a student), John "Mad Dog" Hall who was a major voice in the community (he worked at COMPAQ at the time), and many, many others.
https://webcache.googleusercontent.com/search?q=cache:-i7au3...
Here's one
http://www.xent.com/FoRK-archive/fall96/0269.html
Also - even the USPTO rejected their claim as a trademark.
Rejected after they'd made the term popular.
And it was rejected because it was a simple descriptive term. You can't take ownership of a simple descriptive term.
Bottom line facts are: OSDI don't own it - that's a fact - and they didn't use it first - that's a fact.
The fact is it was barely used until the OSI introduced it as a term at which point it became popular. You seem to have a personal problem with that.
Yes it is. Just because a phrase was used once or twice in some obscure post in the past, doesn't mean that someone can't come up with it independantly.
> a common term back then as well, but I can't find a reference for that now.
Because it wasn't a common term at all. If it was, you'd be able to find thousands of examples of usage, from all over the early web and (especially) Usenet. How many examples do you actually have. Two or three?
The effort required just to get your data in a state that's clean enough to consider moving to the RDBMS you should have started with can be overwhelming.
Then you have to rewrite your queries out of their custom query language.
Is it Mongo's fault you made a mess in your database? No, of course not. And their dashboard is actually pretty nice. But you are massively locked-in.
Source: own a production Mongo DB with years of accumulated mess in it. Desperate to get off it. Paying customer of Mongo's hosting (it's one less Mongo thing to deal with, at least).
[0] There is schema support now, but it's only JSON schema and it's relatively new in the scheme [sorry] of things
It is different from the vendor lock-in that prevents one from migrating from AWS to Google Cloud because all of your code uses their APIs and libraries specifically.
However, the effect is the same, of course. You are locked in! It's not necessarily a bad thing, but this is why you must choose your poison carefully.
This is true, but it's also kind of vendor lock-in because there's a whole query language and aggregation pipeline for Mongo that's completely different to other databases. If I was using an RDBMS and was switching from MySQL to Postgres I think I would likely have a much easier time, because fundamentally it's all SQL (I know, there are differences between Postgres and MySQL, but it's a lot less, and a good ORM will smooth some of it out for you - at least initially)
I think this is basically equivalent to your example of not being able to easily move from AWS to Google Cloud because of their different APIs.
It doesn't seem like SQL-to-Mongo is impossible to implement, because there is third-party tooling for that (which I haven't tried): https://studio3t.com/knowledge-base/articles/sql-query/
I can’t conceptualize a dataset that could survive(/be performant) in a document store, but not a graph.
That's not proof that we'd have fared better if we had open-sourced it. We took exactly the opposite route of MongoDB, with very stringent schemas to ensure data quality. That required a large up-front investment in time, and that was a hard sell too. The whole world went in the opposite direction, of schemaless databases and machine learning for "eh, good enough" answers.
Still, I'll always wonder if we wouldn't have failed so spectacularly if we'd open sourced it. The idea was a pretty good one, and we wrote some remarkable software to make it happen.
In the end we never found the right use case for it. The advantages were all in maintenance rather than development, and even people who could be talked around to it wouldn't see the payoff. There were a trillion other problems, and maybe better management than me could have made it work.
- if your company makes >X revenue a year, give us some of it.
Ofc, they (FSF/OSI/DFSG) would have to relax their FOSS definition(s), but with more projects dying in this way hopefully more FOSS organisations will take heed and think about this.
Ofc, the wording of the license has to be precise enough to avoid something like fobbing off the servers to technically be controlled by subsidiaries with 0 revenue.
Ofc, the license would have to figure out how to share revenue with major contributors too.
Contributors already contribute to for-profit open source projects without themselves getting paid, so this license would make the situation strictly better for them.
Laws and definitions have to change with the changing times - the technological economy is different today than it was 20 years ago when tech companies weren't so big or able to throw their weight around. Staying true to the original spirit of FOSS and sharing, means that we have to find ways to support independent FOSS business.
The loudest arguments I hear at forcing the FOSS definition to remain static and blind to revenue, is from big tech companies or wealthy people being paid by big tech companies, because it benefits them. People working for a small FOSS companies understand the realities of competing in today's tech environment, and understand that revenue-sharing far from stifling FOSS, will allow it to flourish properly.
This would just lead to Hollywood-accounting, where a AWS-Tools subsidiary does all the software at a loss, and AWS-Cloud is just a user etc.
From that perspective they will never be an independent third party, and therefore you can specify that in a contract. So I don't see a theoretical problem to this, just a practical one of specifying this both precisely enough to be enforceable, and general enough to cover all real cases.
In Hollywood’s case, it’s pretty clear when movies are making money (same with games to a large degree), but I don’t know if there’s a way for “tool” companies to leverage that.
Unreal, though, is in a different negotiating position with the game publishers than, say, an open-source software with a new pay-us-if-you-make-money clause. Its the distinction between source-available (like Unreal Engine) and open-source which the article tries to make?
Timescale's new license is an interesting move in this direction.
Or are you describing some sort of system where the authors get the fixed share (%) of user's company revenue? I think this is not going to work very well... just imagine a big company which is not focused on computers. Or a computer startup which wants to be bought by FAANG for billions of dollars.
This license would be exactly like today's FOSS, except to force large tech companies to the negotiating table to share revenue.
For 99% of use cases, MongoDB is open source. You can see the code, you can make modifications, you can use it for free in your business, you can share your changes with others, you can integrate it into your products and services. Yeah, you can't use it if you're working at AWS, but for most people it's just fine.
For founders creating new open source companies, it's a great strategy to go the route of MongoDB. Start off open source and sell services. If you run into big enough problems with direct competitors using your own software, you can modify the license to exclude them.
This is far better than the status quo in, say, 2010, when the conventional wisdom was that if you're providing a service it shouldn't involve any open source at all.