What Five Localization Pull Requests Revealed About Open Source Governance: A Field Report on Open Source’s i18n Infrastructure Gap
A bot recently approved one of my Pull Requests (PRs) with the cleanest possible verdict: “No Issues Found — Recommendation: Merge.” The story did not end there. Weeks later, a maintainer finally reviewed the contribution. By then, the parts of the repository targeted by the localization work had been removed as the project evolved. The PR was closed, not because the translation was incorrect, but because the review arrived after the underlying code structure had changed. That outcome highlights a broader challenge in open source internationalization (i18n). The problem is often not translation quality. It is the absence of processes that allows language contributions to be evaluated, routed, and integrated before project evolution overtakes them. Translation is Not the Hard Part When people hear “i18n,” many maintainers think it means “drop a JSON file in.” That is not what it involves. Internationalisation is a system: stable keys, defined fallback behaviour, plural rules...