Since the S3 API largely remained the same over the last two years, it might be an option to use the Apache version, if AGPL is not possible. Of course, that would lack security fixes that were done in the meantime.
There is also a discussion [1] about that license change.
[0]: https://github.com/minio/minio/commit/069432566fcfac1f105367...
AGPL is true open source.
https://github.com/minio/minio/issues/13308#issuecomment-929...
Lets just say they have a weird take on what constitutes agpl-compliant
Indeed, I don't think that's correct. That depends on the definition of "connecting" but I was under the impression that if you use MinIO on a server, the services that connects to MinIO don't need to be open-source. Only the server component that include MinIO need to be, and only if end users are connecting to that component. But correct me if I'm wrong.
> Combining MinIO software as part of a larger software stack triggers your GNU AGPL v3 obligations.
> The method of combining does not matter. When MinIO is linked to a larger software stack in any form, including statically, dynamically, pipes, or containerized and invoked remotely, the AGPL v3 applies to your use. What triggers the AGPL v3 obligations is the exchanging data between the larger stack and MinIO.
You’d be shocked to find out but linux is also run by cloud providers and offered as a service (in the form of VMs).
And unfortunately because of murky water of what constitutes “derivative work” in agpl (case in point - see the title of this thread) most companies won’t ever touch agpl licensed projects
That's not true, I am in contact with many business using AGPL software. (Not Minio specifically)
Some businesses choose not to touch it, but that's their losses.