Live data from Hacker News

MinIO is now in maintenance-mode

github.com

291–300 of 338 posts

Re: MinIO is now in maintenance-mode

#291
post #273

Earlier 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...

This wording was added in the template in August 2023. What's the licensing situation for community contributions before then?

Presumably they've either gotten explicit permission after the fact, rewritten in the commerical product, or the contribution was too minor to be a concern. I don't think they could have put the amount of though needed to ensure they benefit from contributions in a way no one else can, and then also be unaware of license issues with any possible AGPL only contributions.

Re: MinIO is now in maintenance-mode

#292
post #132

There is https://github.com/seaweedfs/seaweedfs I haver not used it but will be likely a good minio alternative for people who want to run a server and don't use minio just as s3 client.

This is Chris and I am the creator of SeaweedFS. I am starting to work full time on SeaweedFS now. Just create issues on SeaweedFS if any. Recently SeaweedFS is moving fast and added a lot more features, such as: * Server Side Encryption: SSE-S3, SSE-KMS, SSE-C * Object Versioning * Object Lock & Retention * IAM integration * a lot of integration tests Also, SeaweedFS performance is the best in almost all categories…

Congratulations on earning that opportunity!

Thank you for your work. I was in a position where I had to choose between minio and seaweed FS and though seaweed FS was better in every way the lack of an includes dashboard or UI accessibility was a huge factor for me back then. I don't expect or even want you to make any roadmap changes but just wanted to let you know of a possible pain point.

Re: MinIO is now in maintenance-mode

#293

Earlier quoted context omitted.

What if a company change license, drop the project or goes bankrupt? You shouldn't expect guarantee of any kind.

> What if a company change license, drop the project or goes bankrupt? You can always fork the project, then the questions of sponsorships still remains. Recently Ghostty is a non profit, which means that it is guaranteed not to turn into a for profit and rugpull like what MinIO has done.

That doesn't guarantee the devs stay motivated either.

In the end open source allows motivated people to take over the project if you aren't willing to do it yourself but projects can also die of lack of motivated/paid resources.

Re: MinIO is now in maintenance-mode

#294

Earlier quoted context omitted.

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.

Requiring AGPL on the contribution would also prevent a rugpull. MinIO went beyond that. 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.

Ah I didnt realize there were 2 different licenses at play, yeah that's a little sus.

Re: MinIO is now in maintenance-mode

#295

Earlier quoted context omitted.

> ... it can be forked without any potential license change in the future ... It is useful to remember that one may fork at the commit before a license change.

It is also useful to remember that MinIO has historically held to an absurd interpretation of the AGPL -- that it spreads (again, according to them) to software that communicates with MinIO via the REST API/CLI. I assume forks, and software that uses them will be held to the same requirements.

I thought that literally was the point of AGPL. If not, what's the difference between it and GPL3?

Re: MinIO is now in maintenance-mode

#297

So why exactly did they close source, what were they losing by having AGPL? I thought AGPL + selling private licenses to corps was a fantastic method of getting some income for an open source offering.

The moves they have been making seem to be similar to what one would see if the VC money was getting tight or alternatively they were bought out by a Private Equity firm.

Similar to the way Broadcom did with VMware hiking prices astronomically for their largest clients, and basically killing the SME offering.

Re: MinIO is now in maintenance-mode

#298

Earlier quoted context omitted.

"open source projects eventually need a path to monetization" Why?

I believe that, at the end of the day, open source enthusiasts still need to make a living.

God forbid a passion project stay just a passion project. You don't see this monetization perspective in the hobbyist 3D printing community or airbrushing communities. This is directly a result of how much OSS is framed as a "time sink" instead of enjoyable hobby. I don't like this narrative, and don't think its healthy.

Re: MinIO is now in maintenance-mode

#299
post #88

Earlier quoted context omitted.

Sad to see these same people were behind GlusterFS.

Well, maybe they are using that experience to build something better this time around? One can hope...

Sure but trying to close source what has been opensource for a decade or trying to reduce features is very strange. I thought those people had higher standards.

Re: MinIO is now in maintenance-mode

#300
post #243

Earlier 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 think, if anything, in this age of AI coding we should see a resurgence in true open-source projects where people are writing code how they feel like writing it and tossing it out into the world. The quality will be a mixed bag! and that's okay. No warranty expressed or implied. As the quality rises and the cost of AI coding drops - and it will, this phase of $500/mo for Cursor is not going to last - I think we'll…

[deleted]
Post reply on HN