mirror of
https://github.com/pgsty/minio.git
synced 2026-08-09 07:43:29 +03:00
Feng Ruohang
fd2ca1c6d2
README, README_ZH, SECURITY, COMPLIANCE, CONTRIBUTING, NOTICE, code_of_conduct, the vulnerability and PR-etiquette documents, the GitHub issue and pull request templates, and the docs/ tree all present Silo as the product. The Grafana dashboards under docs/metrics/prometheus/grafana/ have their panel titles and descriptions rebranded while every minio_* query, label and expression is left alone, so existing alerts and recording rules keep matching. The distinction the review demanded is applied per hit rather than by search-and-replace: - Product and command text becomes Silo and silo: install and run instructions, systemd examples, compose services, download links, badges. - Protocol and interface text keeps MinIO: MINIO_* variables, minio_* metrics, x-minio-* headers, /minio/* routes, .minio.sys, arn:minio, and API field and error names. - Attribution keeps MinIO and gains the fork's own: the AGPL obligations, original copyright, CREDITS and NOTICE stay, with the modification notice added alongside rather than replacing them. - Historical and third-party references are left as facts, not rewritten for brand tidiness. README and README_ZH each carry an explicit non-affiliation notice, document the side-by-side package migration including the /etc/systemd/system/silo.service.d/10-legacy-user.conf drop-in for keeping a legacy UID/GID, and state that recursive chown is never performed. The trademark attribution uses the policy's approved "based on MinIO technology" wording, not the shortened form the policy rejects. github.com/pgsty/minio links are left in place and labelled transitional. The repository has not been renamed, and rewriting them now would produce documented URLs that 404 until the cutover; they change in the cutover commit together with the goreleaser release target, the OCI source label and the raw-content branch. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
18 lines
922 B
Markdown
18 lines
922 B
Markdown
# AGPLv3 Compliance
|
|
|
|
Silo is distributed under the [GNU Affero General Public License v3.0](LICENSE).
|
|
It incorporates source code from the MinIO project and preserves the original
|
|
copyright, license, and attribution notices in [`NOTICE`](NOTICE),
|
|
[`CREDITS`](CREDITS), and source-file headers.
|
|
|
|
You are responsible for determining how the AGPLv3 applies to your use,
|
|
modification, deployment, and distribution of Silo and its dependencies. The
|
|
Silo maintainers cannot provide legal advice or determine whether a particular
|
|
application or service satisfies the license. Consult qualified counsel when
|
|
the obligations are material to your deployment.
|
|
|
|
If you convey modified binaries or provide network access to a modified
|
|
version, review the complete AGPLv3 text and ensure that the corresponding
|
|
source and notices are made available as required. Dependency licenses and
|
|
separate notices continue to apply independently.
|