Switching git-mind to the MIND-UCAL v1.0 License — Let’s Talk

[flyingrobots]

📢 Switching git-mind to the MIND-UCAL v1.0 License — Let’s Talk

Posted 2025-06-18

Apache 2.0 carried us this far, but our ethics should scale with our code.
We’re replacing Apache 2.0 with MIND-UCAL v1.0 (“No Killer Robots”).
Here’s why:

Why Apache 2.0 no longer works	How MIND-UCAL fixes it
Cops & military can use it — zero limits on weaponization or mass surveillance.	Five Unbreakables block weapons, surveillance states, behavior-manipulation engines, extractive SaaS, and dignity violations.
Branding baggage — the “Apache” name/feather appropriates Indigenous imagery.	Our branding is ours: Moral Intelligence · Non-violent Dev · Universal-Charter-aligned.
Ethics in README, not law — “Please don’t” got forked into “We did anyway.”	Ethics baked into legal text — violate terms, rights auto-terminate.

---

TL;DR

• git-mind now ships under MIND-UCAL v1.0.
• Source headers use
  // SPDX-License-Identifier: LicenseRef-MIND-UCAL-1.0
• Legal text → LICENSE.md; philosophy → COVENANT.md.

---

What changes for you?

If you…	Impact
Build cool, non-violent stuff	Keep hacking — zero workflow change.
Build predictive-policing dashboards or drone swarms	Look elsewhere.
Sell closed-source SaaS built on git-mind	Open your source (under an aligned license) or swap libraries.

We know “ethical source” isn’t OSI-approved — that’s deliberate. Freedom to harm isn’t a freedom we intend to ship.

---

We’d love your input

1. Any problems integrating MIND-UCAL into your stack?
2. Concerns about SPDX headers or package-registry license fields?
3. Suggestions for smoother contributor onboarding under the new license?

“Let this license be a flame, not a fence.”
— Universal Charter, First Flame