No. The AGPL only consider distribution if the modified service is directly accessible to the users. If someone makes modifications to Minio but the modificati

No. The AGPL only consider distribution if the modified service is directly accessible to the users. If someone makes modifications to Minio but the modifications are only for their internal services - or even if those accessing this Modified-Minio are internal to them - then it does not count as software distribution and therefore they can keep the source private without needing to provide their code modifications. To take a few examples: - if I use Minio to store data for my application and I make some improvements (e.g: SSO login for the console for back-office users), it won't count as distribution. - If I have a set of services that use object storage running on my Minio cluster, and I add torrent-gateway capability to this cluster to make my applications able to find the data by content addressing, it won't count as network distribution and I do not need to share the source. - If I start offering S3-compatible services to end users based on Minio, and if I start offering to people the ability to download files via a torrent gateway, I need to provide the source of my changes. - If I make changes on the minio console to allow, e.g, a sleek file browsing UI with search, I need to provide the source with all my changes if this is acessible by the users.