285 commits, opened and closed in one minute: what I do with forks that never upstream
Building FOSS is mostly rewarding and occasionally aggravating. Once in a while it requires some cleverness. The old contract between maintainers and users was simple enough. We build the software, you use it, you report what breaks. Some of you stick around and contribute. The project gets battle-tested by people whose problems I would never have thought of, and everyone comes out ahead. That…
The story revolves around a technical user who maintains a private fork of a project indefinitely, using an agent to handle the maintenance without ever contributing back. This has become increasingly common due to issues like AI-generated noise and devaluing of open-source contributions. A particular example is a PR with 285 commits, 377 files, and about 150,000 added lines, closed within minutes.
The source acknowledges that the original contract between maintainers and users has become strained due to this behavior. To address this, the author decided to read public forks of the project, Xberg, which currently has 576 public forks, most of which are just the fork button with no commits. The author's process involves identifying the forks that have diverged significantly from the main project, extracting the diff, and passing it to an agent to find instances where the fork corrected or defended against issues in the upstream code.
This method results in fewer and better issues, as most divergence is due to packaging, CI, and dependency pinning. The author expresses sympathy for the fork maintainers, acknowledging the costs of upstreaming and the value of fixing problems silently. However, they argue that the aggregate effect of these forks is detrimental to everyone involved.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
