A co-founder who kept explaining the project in public

From walkout to co-founder

When the Joomla core team left Mambo in August 2005, the resignation letter carried dozens of names. Brian Teeman was among them — one of the developers and community figures who walked out over the plan to transfer the Mambo trademark to a newly formed foundation without the core team's agreement. The walkout was clean in one sense: the code was GPL, so it could be taken and continued. What couldn't be taken was the name, which is why Open Source Matters was incorporated quickly to hold whatever assets the new project would need, including the trademark on the new name.

Teeman's role in that early period was not primarily architectural. Louis Landry and Andrew Eddie carried most of the deep technical work; Teeman's documented contribution ran toward the visible and the communicative — the kind of work that keeps a volunteer project coherent when its governance is still improvised. In the months after the fork, that was not a small job.

The conference circuit as governance

Open-source projects have a persistent structural problem: the decisions that shape them are made by a small group of people with technical access and time, and everyone else learns about those decisions after the fact, if at all. One answer to that problem is documentation; another is presence. Teeman pursued both.

His conference record spans the better part of two decades. Joomla!Day events and the wider JoomlaWorld Conference circuit gave volunteer contributors somewhere to put a face to the project — to explain what a release changed, why a governance decision was made the way it was, and what the extension economy's rules actually required of developers. This kind of speaking looks informal but it performs a real function: it makes the governance record accessible to people who would never read a mailing list archive.

The GPL fight is a useful example. When the project took the position that extensions are derivative works ↗ and must therefore be licensed under the GPL, the technical and legal reasoning behind that position needed to reach extension authors who were not lawyers. The Software Freedom Law Center had been asked for a public opinion; the opinion existed; but it still had to be translated into something a developer selling templates could act on. The conference circuit was where that translation happened, and Teeman was consistently part of it.

Teeman's role in that early period was not primarily architectural.

Documentation as institutional memory

Volunteer projects lose memory fast. Maintainers move on, mailing lists become archives nobody reads, and the reasons behind a decision disappear even when the decision itself persists in code. Documentation is one partial remedy, and Teeman's work in that area is part of the public record at docs.joomla.org ↗, the project's official documentation site.

What makes documentation work in governance terms is not completeness but continuity — someone has to care about it across multiple release cycles, and the incentives to do so are weak. Writing documentation earns no commit credit and produces nothing a portfolio can show. Teeman's sustained involvement there is notable precisely because it is unglamorous.

What the record shows

The governance of an open-source project is not only its bylaws, its issue tracker, or its release schedule. It is also the accumulated record of how decisions were explained — who stood up at a conference and said why the security process works the way it does, or why the extension directory has the listing rules it has. That record shapes what contributors expect and what users tolerate.

Teeman's documented role over roughly twenty years is largely that: someone who showed up repeatedly in public to explain the project to the people it depended on. In a volunteer organisation, that kind of continuity is rarer than it looks, and more structural than it seems.