The assumption that stops most people is that contributing to AI open source means optimising attention kernels. A small number of people do that. The rest of the work — the majority of what these projects need — is ordinary software engineering on unusually fast-moving code, and it is chronically under-supplied.
You do not need to write a kernel
Look at what an AI tooling repository actually contains. Client libraries. Configuration parsing. Retry and timeout handling. Streaming response parsers. Schema conversion between providers. Documentation. Examples that no longer run. Tests that mock a model. Almost none of it requires knowing how a transformer works, and all of it requires the discipline that makes software maintainable.
The gap is structural rather than accidental. These projects grow fast, are often started by people optimising for capability rather than for maintenance, and accumulate exactly the kind of debt that a careful engineer is good at paying down. A contributor who writes a reliable test for a flaky integration is more useful to most of these repositories than one more feature.
Six kinds of contribution
