Skip to content
0:00 / 0:00

#minio#s3#opensourcelicensing

MinIO, we won't miss you.

Rawkode Academy

28K subscribers • 3 videos on Hallway

YouTube
  • Recommended by 1 person: 1 in engineering communities.
  • May be out of date. The tools, versions or practices it shows have likely moved on.
  • An opinion. It argues one side of a question engineers disagree on.

Beginner. No background in the topic needed.

9.7K views11 months ago1 recommendation

Databases and dataTools and practiceNoSQL and document databasesOpen sourceThe tech industry

An explanation of the community backlash against MinIO's licensing changes, feature gating, and the transition of its community edition to maintenance mode.

MinIO just announced maintenance mode for their community edition — and honestly? Good riddance. This isn't about open source companies needing to make money. That's valid. This is about how MinIO systematically destroyed community trust through silent license changes, aggressive legal theatrics, gutted features behind a $96K paywall, and locking GitHub threads when people pushed back. From the quiet AGPL switch in 2019 to the Weka fiasco to abandoning Docker images during a critical CVE - the pattern is clear: shoot first, ask questions never. A billion Docker downloads. Years of community goodwill. All gone. If you're still on MinIO, it's time to look at SeaweedFS. Adam's tweet: x.com/adamhjk/status/1640368244484902912

Why it's here

1 person recommends this

What people say. Recommended as a cautionary explanation of MinIO's anti-FOSS licensing changes and why to avoid it for production.

u/BeowulfRubixin r/kubernetes • Recommends

On “Open source monitoring tool for production ??”

Whatever you do, avoid Mimio for S3. Naughty anti FOSS attitude. Not dependable for long term production. link to this video

u/BeowulfRubixin r/kubernetes • Recommends

On “Open source monitoring tool for production ??”

Minus Minio. Naughty anti FOSS attitude. Not dependable for long term production. link to this video