Open source & its licences
Source: https://influences.sgit.ai/register/open-source/index.html↗ · markdown twin of the entry page.
An influence on Dinis Cruz — one of 25 entries in his register.
- tier traced — corpus evidence exists today
- kind topic + movement
- status link-out — blocks 1-3 and a pointer: the trace of this influence is an entire sibling site
- briefing none
A link-out entry that owns one thing the sibling site does not foreground: open source as personal formation. What two decades of releasing tools taught about licences as social contracts rather than legal ones.
Block 1 — The anchor
Releasing tools in the open, from the O2 Platform era onward
A practice rather than a work. The anchor is the habit of publishing, and what it cost and returned.
Linked, never rehosted.
Block 2 — In his own words
The sibling site carries the history, the licence positions and the argument for publishing. What belongs here instead is the formation: what releasing changes about how you write. Code you will publish is code you explain; a tool with users is a tool with a boundary; and a licence choice made twenty years ago still decides who can use the thing today.
The second strand is the one that connects to the rest of this register. Open source is the demonstration that OWASP's↗ compounding-in-the-open claim works outside a conference, that Raymond's essay↗ described something real, and that Torvalds↗ built the two pieces of infrastructure the whole habit now rests on.
Block 3 — The principle
Releasing work is how it compounds — and the licence is the constitution, not the paperwork: it decides who can build on this and what they owe.
Block 4 — The trace table
Where the trace table would be: The trace of this influence is an entire site, with a full history pack behind it. This entry owns the personal half — what publishing did to Dinis Cruz's practice — and two nested entries: The Cathedral and the Bazaar↗ and Torvalds↗.
open-source.sgit.ai — https://open-source.sgit.ai↗
Block 6 — The checklist
- If this were public tomorrow, what would have to change first — and is that thing a defect?
- Does the licence say what someone building on this owes, or only what they may not do?
- Is the boundary of this tool something a stranger could find, or only something the author knows?
- Is this being kept private for a reason that would survive being written down?
The corpus evidence
| Path in the corpus | What it carries |
|---|---|
open-source.sgit.ai (sibling site + its brief pack) | an 11,619-word corpus and a 17,909-word history on file — the material this entry deliberately does not repeat |
(corpus-wide) | licence positions and publishing decisions across the estate |
CC BY 4.0 — Dinis Cruz, with AI co-authorship (Claude, Anthropic). The anchor work belongs to its author and is linked, not licensed here.