On openness · The But Is It Open? blog

Open License, Closed Door: The Repos Where You Can't Really Join

· 4 minute read

AlphaFold and Whisper pass the license test easily. KataGo is the one that lets you in. A license grants the right to use the code; it doesn't make a project participatory.

Abstract painting on warm ivory paper: a towering, opaque navy slab with a thin sliver of light at its base, small ochre and burgundy shards stopping at its face on the left, and a loose, overlapping cluster of translucent mustard, burgundy and navy planes with open gaps on the right.

Open License, Closed Door: The Repos Where You Can't Really Join

Open source without a community just feels wrong to me. I can read the license, check that it's Apache 2.0 or MIT, confirm that I'm allowed to use, modify and redistribute the code, and still come away with the sense that something is missing. Open source without participation doesn't feel like open source.

A license tells you what you're allowed to do with the code. It says nothing about whether anyone will take your bug report, review your patch or let you near the work that matters. A few very famous repositories make that gap easy to see.

AlphaFold: a door that opens one way

Start with the generous part. DeepMind's AlphaFold changed structural biology, and releasing its code under Apache 2.0, one of the most permissive licenses there is, was a real gift. Nearly 15,000 people have starred it.

Now look at how outsiders are received. People have opened 148 pull requests against AlphaFold. As of today, GitHub shows none of them merged. Issues are open, with 909 filed, and the contributing guide is candid: small bug fixes and documentation patches are welcome, but "we do not plan to make any major changes to this repository."

That zero is less hostile than it looks. Every recent commit in the repository arrives through Copybara, the tool Google uses to sync code out from its internal systems. When a maintainer likes an outside fix, they often reimplement it inside Google and close the pull request with a thank-you and a link to their own commit. People are listening. But the development happens somewhere you can't see, and the public repository is where it gets published.

You can make a suggestion. You can't join the work.

Whisper: the bug channel is switched off

OpenAI's Whisper is a different shape. It's MIT-licensed, it has close to 113,000 stars, and it does merge outside work: 124 of its 454 pull requests have been merged. So it would be unfair to say strangers have no way in.

What's missing is the most basic public channel a project has. Issues are disabled on the repository. There's a Discussions tab, but there's no place where a bug report becomes a tracked, visible piece of work that somebody owns. And the part of Whisper that matters most, the trained model, isn't something an outsider can contribute to at all. The code in the repository runs the model. The data and the training run that produced the weights stay with OpenAI. You can fix the wrapper. You can't help with what's inside it.

KataGo: what participation looks like

Then there's KataGo, the Go engine David Wu started as a personal project. It's a fraction of Whisper's size, with about 5,300 stars, but 153 of its 285 pull requests have been merged and its issue tracker holds 985 issues. The license is MIT-style.

What really sets it apart is that participation goes all the way down to the model. KataGo's public distributed training run lets volunteers donate GPU time: their machines play games against themselves and upload the results, and that data trains the networks everyone downloads. You don't need to work for anyone to help make the model stronger. Developers hang out in a public Discord. In the README, Wu says he'd love to hear from anyone who uses the code for their own training experiments.

KataGo has an advantage: a Go engine can generate its own training data, and a protein or speech model can't, so the economics aren't equal. But it shows that open development of a trained model is possible, not just open distribution of one.

The question the license can't answer

When we score projects for the book's openness index, the sixth dimension is Governance & Participation. The question is plain: can a person help develop this model, contributing data, code, evaluation or direction, without being employed by or affiliated with the publisher? Or is it a one-way corporate release?

AlphaFold and Whisper pass the license test easily, and I'm grateful for both releases. On that question, though, the index gives AlphaFold 2 and Whisper a 1 out of 3, which means limited. KataGo gets a 3. One accepts suggestions and does the work in-house. The other merges code but turned off its public bug tracker and keeps the model out of reach. KataGo, with fewer stars, a smaller budget and a scruffier license file, is the one that actually lets you in.

A license lets you take the code. Participation lets you take part in the project. Only one of those makes it feel open.

But is it open? If the only thing you can do is download it, I'm not sure it is.

Commentary based on GitHub repository data and contributing guides checked November 16, 2026.

Sources

← More from the blogJoin the newsletter ↗