141–150 of 206 posts
As somebody who pulled down an open source project I find this trope of FOSS losing its way for greed utterly disingenuous. People need to put food on the table, period. I’ve had people take my work and make more money from it than I have, with no attribution or credit. Then I pulled it down and got a lot of people asking why it’s no longer free, when I tell them I can sell them a license they don’t even reply. I car…
Have you made meaningfully more money from it after taking it down?
Earlier quoted context omitted.
Definitely an interesting question. Some things that may explain why -- Mongo was always AGPL and relicensed to SSPL. This had the following consequences: * Very few companies and zero large cloud companies ever attempted to run the MongoDB codebase in production as a managed service, other than MongoDB the company. * Mostly because of the above, MongoDB did not receive many code contributions that did not originate…
Were there any MongoDB cloud offerings of the AGPL version? If SSPL is effective as a poisonous pill against AWS and Co. but SSPL is not, that's a big difference in my book.
As somebody who pulled down an open source project I find this trope of FOSS losing its way for greed utterly disingenuous. People need to put food on the table, period. I’ve had people take my work and make more money from it than I have, with no attribution or credit. Then I pulled it down and got a lot of people asking why it’s no longer free, when I tell them I can sell them a license they don’t even reply. I car…
How did stopping them use it feed your family?
These aren’t hard concepts.
Why, unlike Redis and Elasticsearch and Terraform, was there no big community fork of MongoDB when it was relicensed? Cockroach, Materialize, and MariaDB were all also relicensed without massive backlash, I think. But I think that's because they had fewer users at the time. But Mongo's was the one relicense event that didn't produce so much shock that a new fork came out of it. And Mongo's stock is doing great, if th…
As somebody who pulled down an open source project I find this trope of FOSS losing its way for greed utterly disingenuous. People need to put food on the table, period. I’ve had people take my work and make more money from it than I have, with no attribution or credit. Then I pulled it down and got a lot of people asking why it’s no longer free, when I tell them I can sell them a license they don’t even reply. I car…
How did stopping them use it feed your family?
Why, unlike Redis and Elasticsearch and Terraform, was there no big community fork of MongoDB when it was relicensed? Cockroach, Materialize, and MariaDB were all also relicensed without massive backlash, I think. But I think that's because they had fewer users at the time. But Mongo's was the one relicense event that didn't produce so much shock that a new fork came out of it. And Mongo's stock is doing great, if th…
Many people who "start" with those database choices either (1) "end up" elsewhere or (2) are perfectly content with treating their database as a SaaS business expense.
Their communities have self-selected into a [profitable] niche that excludes the kinds of people (like the author of this blog post) who are both capable and motivated to maintain a fork.
The author of TFA would probably categorize MongoDB as "software I hate" (a category he touches on in the article), to put it in perspective.
Earlier quoted context omitted.
> people won't want AWS/GCP/Azure to slap a UI on top of their free open-source product and resell it If it wasn't open-source it won't be as popular as it is in the first place, Redis is also using ton of open source software or libraries for free. Not defending AWS/GCP/Azure, I actually got my software used when i was young by a large company for free (not even a mention- Still using it i think, 5M+ Play Store Down…
Redis actually has very few external dependencies compared to most modern FOSS: IIRC, it only need libc and OpenSSL (the latter only if you build TLS) on your system, and provide their forked copies of Jemalloc, LUA, fpconv, HiRedis, Linenoise and Hdr_Histogram.
for example, something like jemalloc is highly nontrivial
Earlier quoted context omitted.
Definitely an interesting question. Some things that may explain why -- Mongo was always AGPL and relicensed to SSPL. This had the following consequences: * Very few companies and zero large cloud companies ever attempted to run the MongoDB codebase in production as a managed service, other than MongoDB the company. * Mostly because of the above, MongoDB did not receive many code contributions that did not originate…
Were there any MongoDB cloud offerings of the AGPL version? If SSPL is effective as a poisonous pill against AWS and Co. but SSPL is not, that's a big difference in my book.
Earlier quoted context omitted.
(And then gitea was forked into forgejo, which is used by codeberg, iiuc)
I'm using Gitea locally. I haven't come across forgejo before. It seems to be forked on the basis of providing a fully open source solution (it states that some Gitea enterprise features are not present). Do you know what the main differences are and whether it is worth switching?
1. Gitea, Inc replaced the prior community leadership structure with one controlled by Gitea, Inc and have pivoted into being primarily about a hosted code SaaS they launched this year that didn't exist for the first 7 years of the project. They could do it because they had 2 of the 3 seats on the community stewardship organisation at the time to vote for it, but that wasn't always true. For a lot of people, Gitea's primary motivation was for the self-hosted and fully open use case, but now it's not clear that that will remain any more of a priority for Gitea Inc as it is for e.g. Gitlab
2. There were also some contributors who were interested for the sake of decentralising code forges (and not just git), and so were big into the forgefed project which was an activitypub based federation protocol. Gitea Inc were officially on board with that, but the contributors felt they weren't helpful enough to actually implementing that with missteps like letting grant funding from NLNet expire.
The contributors from groups 1 and 2, and Codeberg banded together to make Forgejo after the Gitea change.
Until the latest release (just last month) Forgejo was one way pulling all changes from Gitea, but they've diverged enough that they're now hard forks. Both have active development, but Forgejo's main unique focus is the federation stuff, while Gitea's was enhancing their CI offering. But while Gitea may have more development effort, being funded by a commercial organisation rather than volunteers and a non-profit, I think they have a long way to catch up to Gitlab in that front, so it feels like they've dropped their unique factor to try chase Gitlab.
Earlier quoted context omitted.
The hyperscalers weren't selling Terraform though, Hashicorp was losing to Terragrunt, Spacelift et al, who had decent to good offerings. I'd say Elasticsearch is still the comparison to make here for a product that clouds just resold, then again, Redis the company didn't build Redis the software and their latest marketing smells more of VC hawkery than any reasonable pitch
> Hashicorp was losing to Terragrunt, Spacelift et al, who had decent to good offerings. Would love some data in support of this statement. Not saying you're wrong necessarily, just it feels like a perception vs. reality comment potentially.
https://opentofu.org/supporters/
For more details, you could listen to: