Hanzo Dev
fcece90c2b
- Replace all MinIO brand references with S3 in docs, helm charts, and comments - Replace quay.io/minio images with ghcr.io/hanzoai/s3 and ghcr.io/hanzos3/* - Replace min.io domains: docs→docs.hanzo.ai, dl→dl.hanzo.space, play→play.hanzo.space - Replace slack.min.io with hanzo.ai/discord - Replace subnet.min.io with subnet.hanzo.ai - Update Makefile REPO to ghcr.io/hanzoai - Update helm values: mc image, OIDC clientId, service account name - Update Go source user-facing URLs and messages - Fix test configs and grafana dashboard descriptions
1.1 KiB
AGPLv3 Compliance
We have designed S3 as an Open Source software for the Open Source software community. This requires applications to consider whether their usage of S3 is in compliance with the GNU AGPLv3 license.
S3 cannot make the determination as to whether your application's usage of S3 is in compliance with the AGPLv3 license requirements. You should instead rely on your own legal counsel or licensing specialists to audit and ensure your application is in compliance with the licenses of S3 and all other open-source projects with which your application integrates or interacts. We understand that AGPLv3 licensing is complex and nuanced. It is for that reason we strongly encourage using experts in licensing to make any such determinations around compliance instead of relying on apocryphal or anecdotal advice.
S3 Commercial Licensing is the best option for applications that trigger AGPLv3 obligations (e.g. open sourcing your application). Applications using S3 - or any other OSS-licensed code - without validating their usage do so at their own risk.