Eternal September originally names a moment in Usenet’s history: each September a wave of new university students arrived online unfamiliar with its norms and was patiently onboarded, until mainstream dial-up ISPs brought a continuous influx of new users and it became “the September that never ended”. In a February 2026 post (Welcome to the Eternal September of open source. Here’s what we plan to do for maintainers.), GitHub applies the term to open source, arguing that it is now experiencing its own Eternal September — driven not just by new users but by the sheer volume of contributions, as generative AI lets people produce code, issues and security reports at scale while the cost of reviewing them stays the same.
Usage
In GitHub’s usage the term frames a trust problem rather than a quality problem alone. Open collaboration runs on trust, which the friction of contributing used to protect; the post argues that most contributors act in good faith, but that when volume accelerates faster than review capacity even well-intentioned submissions can overwhelm maintainers, and trust starts to strain. GitHub treats it as a continuation of older problems — noisy inbound, triage of bug reports, automated scanner reports — at a new scale.
The post uses the metaphor optimistically as well: it calls open source’s Eternal September a sign that more people want to participate than ever, and argues that, as the early internet evolved norms and tools to sustain community at scale, open source needs better signals and tools for maintainers rather than raised drawbridges. Responses it describes range from platform controls on who may open pull requests to community trust systems such as Vouch and written AI contribution policy rules.