Comment by phoronixrly
9 days ago
> the software is under AGPL. Go forth and forkify.
No, what was minio is now aistor, a closed-source proprietary software. Tell me how to fork it and I will.
> they wanted to be the only commercial source of the software
The choice of AGPL tells me nothing more than what is stated in the license. And I definitely don't intend to close the source of any of my AGPL-licensed projects.
> Tell me how to fork it and I will.
https://github.com/minio/minio/fork
The fact that new versions aren't available does nothing to stop you from forking versions that are. Or were - they'll be available somewhere, especially if it got packaged for OS distribution.
The only packages I find of aistor, are binary packages. Not only that, the aistor license agreement explicitly states the following:
> You may not modify, reverse engineer, decompile, disassemble, or create derivative works of the Software.
Do you consider this a breach of the AGPL?
So fork the last minio, and work from there... nobody is stopping you.
aistor is proprietary software[1]. Having an old version of your software be open source does not make your software open-source. Why does this need an explanation?
[1] https://www.min.io/legal/aistor-free-agreement
You aren't entitled to the product of someone else's work even if they gave away older versions of that work... What is so hard for you to understand about that?
1 reply →
> And I definitely don't intend to close the source of any of my AGPL-licensed projects.
If a commercial company has "core" version under AGPL, it usually means their free version is an extended demo of the commercial product.