Blame · Line-by-line history

`LICENSE-CHANGE-NOTICE.md`

Each line is annotated with the commit that last touched it. Click any SHA to jump to that commit and see the surrounding change.

LICENSE-CHANGE-NOTICE.mdBlame94 lines · 1 contributor

Normal view Raw

e461e99Claude	1	# Gluecron License Change Notice
	2
	3	Status: Announced 2026-05-25 · Effective with v1.0 release · Pending counsel review
	4
	5	## What's changing
	6
	7	Gluecron is moving from the MIT License to the **GNU Affero General
	8	Public License v3.0 (AGPL-3.0)** effective with the v1.0 release.
	9
	10	The current `LICENSE` file (MIT) continues to apply to every commit up
	11	to the v1.0 cutover. From v1.0 onwards, all new contributions and the
	12	codebase as a whole are licensed under AGPL-3.0.
	13
	14	## Why
	15
	16	### The short answer
	17
	18	The AGPL is the only widely-recognised license that closes the
	19	"network-use loophole." If someone takes Gluecron, modifies it, and runs
	20	it as a service — they must publish their modifications. Other licenses
	21	(MIT, Apache, even GPL) let cloud vendors privatise improvements.
	22
	23	### The strategic answer
	24
	25	Gluecron is built to be the AI-native git platform for the next decade.
	26	We need to ensure:
	27
	28	1. The platform stays open. AGPL guarantees every Gluecron
	29	instance, anywhere, contributes back any modifications it ships
	30	to its users.
	31
	32	2. Hyperscale forks return value. Microsoft, AWS, GCP — if any of
	33	them fork Gluecron and run it as a managed service, AGPL forces
	34	them to release their changes. MIT/Apache let them do so without
	35	contribution.
	36
	37	3. The community benefits from every deployment. Whether you run
	38	Gluecron at home, in an enterprise, or as a SaaS — your improvements
	39	flow back to the commons.
	40
	41	### What this means for you
	42
	43	- You can still use Gluecron commercially. AGPL doesn't restrict
	44	commercial use. Run it for your company, your customers, your SaaS —
	45	all permitted.
	46	- You must share modifications you ship to users. If you modify
	47	Gluecron and run that modified version as a network service that
	48	your users interact with, you must make the modified source code
	49	available to those users.
	50	- Private internal modifications are fine without disclosure.
	51	AGPL only triggers when your modified version is offered as a
	52	service to others. Internal-only changes have no disclosure
	53	requirement.
	54
	55	## What about my existing fork/integration?
	56
	57	Anything you forked or integrated against under the MIT license
	58	stays MIT-licensed. You don't have to retroactively re-license
	59	work that was done before the v1.0 cutover.
	60
	61	For integrations against the Gluecron API (Holden Mercer, Crontech,
	62	Cursor, etc.) — the API contract is unchanged. Your integration code
	63	remains under whatever license you originally chose.
	64
	65	## What about Crontech?
	66
	67	Crontech and Gluecron are sister platforms. The AGPL change is
	68	neutral on the Crontech ↔ Gluecron edge-layer relationship — Crontech
	69	acts as a network service in front of Gluecron, not a fork of it. No
	70	AGPL implications for that integration.
	71
	72	## What about contributors?
	73
	74	By submitting a PR to Gluecron after the v1.0 cutover, you agree to
	75	license your contribution under AGPL-3.0. Pre-v1.0 contributions
	76	remain under MIT.
	77
	78	## When does v1.0 ship?
	79
	80	v1.0 is the "platform stability" milestone. We'll cut it once:
	81	- The closed-loop core (spec → code → ship → monitor) is stable
	82	- Agent multiplayer is production-tested at scale
	83	- We have at least one external enterprise customer in production
	84	- Counsel has reviewed the AGPL transition
	85
	86	Target: late 2026 calendar year.
	87
	88	## The single sentence
	89
	90	**Gluecron will be open source forever. AGPL guarantees that
	91	"forever" includes every hyperscale fork of us, not just every
	92	self-host of us.**
	93
	94	— Gluecron team, 2026-05-25