Big thanks to MinIO, RustFS, and Garage for their contributions. That said, MinIO closing the door on open source so abruptly definitely spooked the community. But honestly, fair play to them—open source projects eventually need a path to monetization. I’ve evaluated both RustFS and Garage, and here’s the breakdown: Release Cadence: Garage feels a bit slower, while RustFS is shipping updates almost weekly. Licensing:…
MinIO is now in maintenance-mode
281–290 of 338 posts
Re: MinIO is now in maintenance-mode
#282Big thanks to MinIO, RustFS, and Garage for their contributions. That said, MinIO closing the door on open source so abruptly definitely spooked the community. But honestly, fair play to them—open source projects eventually need a path to monetization. I’ve evaluated both RustFS and Garage, and here’s the breakdown: Release Cadence: Garage feels a bit slower, while RustFS is shipping updates almost weekly. Licensing:…
Re: MinIO is now in maintenance-mode
#283Earlier quoted context omitted.
"open source projects eventually need a path to monetization" Why?
Human beings have this strange desire to be fed, have shelter and other such mundane stuff, all of those clearly less important than software in the big scheme of things, of course.
Re: MinIO is now in maintenance-mode
#284Earlier quoted context omitted.
> open source projects eventually need a path to monetization I guess I'm curious if I'm understanding what you mean here, because it seems like there's a huge number of counterexamples. GNU coreutils. The linux kernel. FreeBSD. NFS and iSCSI drivers for either of those kernels. Cgroups in the Linux kernel. If anything, it seems strange to expect to be able to monetize free-as-in-freedom software. GNU freedom number…
I don't think there's still someone actively working on the Linux kernel without receiving a salary, and this for the last two decades more or less.
Re: MinIO is now in maintenance-mode
#285Earlier quoted context omitted.
I don't think there's still someone actively working on the Linux kernel without receiving a salary, and this for the last two decades more or less.
You would be incorrect, LWN tracks statistics about contributor employers for every Linux kernel release and their latest post about that says that "(None)" (ie unpaid contributions) beat a number of large companies, including RedHat by the lines changed metric, or SUSE by the changesets metric. https://lwn.net/SubscriberLink/1046966/f957408bbdd4d388/
Re: MinIO is now in maintenance-mode
#286Earlier quoted context omitted.
You would be incorrect, LWN tracks statistics about contributor employers for every Linux kernel release and their latest post about that says that "(None)" (ie unpaid contributions) beat a number of large companies, including RedHat by the lines changed metric, or SUSE by the changesets metric. https://lwn.net/SubscriberLink/1046966/f957408bbdd4d388/
Well yes, but the vast majority of changes (~95%, by either changes or lines) seem to be from contributors supported by employers.
Re: MinIO is now in maintenance-mode
#287I think it is about 10 years old now and it is really stable.
Re: MinIO is now in maintenance-mode
#288Stallman was right. When will the developer community learn not to contribute to these projects with awful CLAs. The rug has been pulled.
Re: MinIO is now in maintenance-mode
#289Big thanks to MinIO, RustFS, and Garage for their contributions. That said, MinIO closing the door on open source so abruptly definitely spooked the community. But honestly, fair play to them—open source projects eventually need a path to monetization. I’ve evaluated both RustFS and Garage, and here’s the breakdown: Release Cadence: Garage feels a bit slower, while RustFS is shipping updates almost weekly. Licensing:…
"open source projects eventually need a path to monetization" Why?
Re: MinIO is now in maintenance-mode
#290Earlier quoted context omitted.
MinIO had a de facto CLA. MinIO required contributors to license their code to the project maintainers (only) under Apache 2. Not as bad as copyright assignment, but still asymmetric (they can relicense for commercial use, but you only get AGPL). https://github.com/minio/minio/blob/master/.github/PULL_REQU...
Isn't that standard protective boilerplate so that they cant get rugpulled themselves on a contribution, 2 years later? I thought the ASF had something similar.
The wording gives an Apache license only to MinIO, not to people who use it. So MinIO can relicense the the contributor code under a commercially viable license, but no one else can. Everyone else will only have access to the contribution under AGPL as part of the whole project.