Live data from Hacker News

MinIO Is Dead, Long Live MinIO

blog.vonng.com

91–95 of 95 posts

Re: MinIO Is Dead, Long Live MinIO

#91
post #5

It's nice that people are taking this up, and one of the main benefits of open source in the first place. I have my doubts that this will succeed if it's just one guy, but maybe it takes on new life this way and I would never discourage people from trying to add value to this world. That said I increasingly have a very strong distaste of these AI generated articles. They are long and tedious to read and it really mak…

I have no reason to trust that the fork itself is competently maintained when the author did not even bother to write the announcement.

I'm generally fully in agreement that AI writing is bad.

But this is one of the few cases where it might be acceptable.

Author is not a native speaker; in an announcement that a known project is being forked for maintenance the occasional odd phrasing and possible errors in grammar could sound unprofessional.

I wonder if in such cases a better use of AI would be to try to write it yourself and just ask a LLM to revise instead? Maybe with some directive to "just point out errors in syntax and grammar, and factual mistakes. No suggestions on style"?

Re: MinIO Is Dead, Long Live MinIO

#92
post #14
post #12

There are 3 new commits, and the only actually fixes are: Go update and revert to earlier version of console. But there are a bunch of changes to docs, CI workflows and issue templates. Which is what is the easy part of managing a fork, and I've seen a bunch of forks that ended up only updating readme-s, CI, etc. I'll have more faith in the fork when the maintainers do actual fixes.

Although, to be fair, getting too aggressive off the bat would be concerning. A clean fork that is bit for bit compatible with the last open source version is definitely an attractive proposition from a software supply chain perspective.

That's a good point. Though I'd still expect more effort from the developer to convince people that they will actively maintain the project after the first 3 months.

Re: MinIO Is Dead, Long Live MinIO

#93
post #56

Earlier quoted context omitted.

I can't see how Amazon is incentivized to avoid making any changes that break compatibility for their imitators, so long as their first party SDKs continue working. Standardized feels like it should be suffixed with "as long as Amazon doesn't ever feel like evolving the product further".

There is a lot of software that directly implements the HTTP S3 API. That API is also documented by Amazon. E.g. the last implementation I saw was by DuckDB https://github.com/duckdb/duckdb-httpfs/blob/main/src/s3fs.c...

I think my point doesn't really land. I was trying to express the idea "S3 is not a standard where AWS is the reference implementation, it is a successful commercial product with many many copy cats".

Their only real inherent commitment here is to whatever backwards-compatibility expectations are being set for their first-party SDKs. If they fulfill that but other vendors can't or won't follow suit, the outcome is gonna be different than it would be for an actual standard rather than an assumed one. There is no meaningful leverage for the third parties to exert to force a community-favored outcome if Amazon decides otherwise.

Re: MinIO Is Dead, Long Live MinIO

#94
post #11

Maybe the author isn't aware that Chainguard is going to keep patching MinIO for CVEs: https://www.chainguard.dev/unchained/secure-and-free-minio-c... You wouldn't get the other changes in this post (e.g., restoring the admin console) but that's a bit orthogonal.

They can probably merge them.

> This project is currently under maintenance and is not accepting new changes.

Re: MinIO Is Dead, Long Live MinIO

#95
post #6

Earlier quoted context omitted.

The copyright for Minio consists of: - Code written by the Minio team, which they have full ownership of and can relicense as they wish - Code written by third party contributors, where Minio required the contributors to provide Minio a BSD license to use the contributions but only published it to other people under AGPL. So the AGPL doesn't bind Minio themselves because of their licensing policy. (Which is why while…

the FSF position is that GPL is unenforceable without a single copyright owner, which is why almost all gnu projects, linux, canonical/redhat/etc projects have a CLA or something functionally similar

Linux has no CLA.

DCO is something different, and not a rugpull mechanism.

Each author retains their copyright, and is not giving away anything, just licensing their contribution according to the project license.

https://developercertificate.org/

CLAs are a corporate tool for making money off of open source.

Post reply on HN