stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 2 Releases Wiki Activity

update license references from AGPL-3.0-or-later to BUSL-1.1 across multiple documents

Browse Source
This commit is contained in:
Vladimir Moushkov
2026-01-31 13:48:39 +02:00
parent 6f8ee8aacb
commit fa4a98dfef
12 changed files with 21 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs-archived/product/advisories/27-Nov-2025-superseded/28-Nov-2025 - Sovereign Crypto for Regional Compliance.md
View File

@@ -251,7 +251,7 @@ Sovereign deployments often require air-gapped operation:
- CryptoPro CSP requires customer license
- OpenSSL GOST engine under Apache 2.0
- Tongsuo under Apache 2.0
- Forked GostCryptography under MIT (with AGPL obligations from Stella Ops wrapper)
- Forked GostCryptography under MIT (with BUSL-1.1 obligations from Stella Ops wrapper)
---

4
docs-archived/product/advisories/27-Nov-2025-superseded/30-Nov-2025 - Implementor Guidelines for Stella Ops.md
View File

@@ -290,9 +290,9 @@ As an implementor:
## 7. Licensing, attribution, and governance
Stella Ops is AGPL-3.0-or-later and the governance docs + release playbook set clear expectations. ([Stella Ops][10])
Stella Ops is source-available under BUSL-1.1 and the governance docs + release playbook set clear expectations. ([Stella Ops][10])
* **AGPL network clause:** If you run a modified Stella Ops for others over a network, you must provide the source of that exact version. Don’t introduce proprietary modules that violate this. ([Stella Ops][10])
* **Source-available terms:** Evaluation and development are free within the Free tier limits; production use requires a paid plan. ([Stella Ops][10])
* **No hidden SaaS reselling:** Re-hosting as a service is disallowed without prior consent; design and documentation should not encourage “stealth SaaS” business models on top of Stella Ops. ([Gitea: Git with a cup of tea][5])
* **Attribution:** Keep the original Stella Ops attribution in the UI and CLI, even in forks; don’t strip branding. ([Gitea: Git with a cup of tea][5])
* **Contribution hygiene:** Ensure all MRs: