"We've broken the code base into logical chunks, called modules, and the foundation staff delegate authority for the modules to people with the most expertise"
About this Quote
Software governance is rarely sold as politics, but Mitchell Baker is describing power with a developer-friendly accent. “Broken the code base into logical chunks” sounds like clean engineering hygiene: modularity, clarity, an architecture any competent team would applaud. The real move arrives in the next clause, where “the foundation staff delegate authority” quietly reframes code as jurisdiction. Modules aren’t just technical boundaries; they become administrative borders where decisions can be made, vetoed, and defended.
Baker’s phrasing is careful: “delegate” implies legitimacy and restraint, not seizure. It signals that authority originates in an institution (the foundation) but is intentionally distributed, a nod to open-source ideals without surrendering accountability. This is the Mozilla-era tightrope: a project that wants the volunteer energy and credibility of a commons while still needing a chain of command strong enough to ship software and handle security crises.
“People with the most expertise” is the most culturally loaded part. It’s meritocracy language, and it works because it feels morally neutral: who could argue with expertise? Yet it also naturalizes gatekeeping. Expertise is real, but it’s also accrued through proximity, time, and access - which means the sentence doubles as a justification for why certain voices get to decide what enters the code and what doesn’t.
Context matters: Baker, a lawyer at the center of a major open-source foundation, is translating messy human governance into a system that sounds like engineering. It’s a pitch for trust: trust the structure, trust the experts, and the project can scale without collapsing into chaos or capture.
Baker’s phrasing is careful: “delegate” implies legitimacy and restraint, not seizure. It signals that authority originates in an institution (the foundation) but is intentionally distributed, a nod to open-source ideals without surrendering accountability. This is the Mozilla-era tightrope: a project that wants the volunteer energy and credibility of a commons while still needing a chain of command strong enough to ship software and handle security crises.
“People with the most expertise” is the most culturally loaded part. It’s meritocracy language, and it works because it feels morally neutral: who could argue with expertise? Yet it also naturalizes gatekeeping. Expertise is real, but it’s also accrued through proximity, time, and access - which means the sentence doubles as a justification for why certain voices get to decide what enters the code and what doesn’t.
Context matters: Baker, a lawyer at the center of a major open-source foundation, is translating messy human governance into a system that sounds like engineering. It’s a pitch for trust: trust the structure, trust the experts, and the project can scale without collapsing into chaos or capture.
Quote Details
| Topic | Coding & Programming |
|---|
More Quotes by Mitchell
Add to List

