简体中文
EnglishWhat is OpenChaos.dev?
Updated
OpenChaos.dev is a self-evolving open source project where the community votes on pull requests each week, and the winning PR gets merged. It is designed for people who want to see how a project changes when direction is set by recurring community votes rather than by a single maintainer or roadmap. The site frames this as "Control vs Chaos": instead of one owner deciding what enters the codebase, the merge decision is handed to a weekly vote.
How the weekly cycle works
The core loop is simple and time-boxed:
- PRs are proposed — contributors open pull requests against the project.
- The community votes — voting runs on a weekly cadence.
- A winner is selected — the PR with the winning vote is merged.
- The cycle resets — a countdown on the site tracks time to the next merge.
The homepage shows a "Next Merge Countdown" with hours, minutes, and seconds, which makes the deadline visible rather than leaving it implicit. Past results are collected in a "Hall of Chaos — Past Winners" section, so you can review what has actually been merged instead of only what is currently proposed.
What makes it different from a typical open source project
Most open source projects concentrate merge authority in maintainers or a core team. OpenChaos.dev inverts that: the deciding mechanism is a public vote, and the outcome is binding on the next merge.
| Dimension | Typical open source project | OpenChaos.dev |
|---|---|---|
| Who decides merges | Maintainer or core team | Community vote |
| Decision cadence | As needed | Weekly |
| Direction | Roadmap or maintainer vision | Emergent, vote by vote |
| What you can inspect | Issues, PRs, releases | PRs, votes, past winners |
The trade-off is deliberate. You get transparency and a low barrier to influencing the project, but you also get less predictability — the project's direction can shift with each vote rather than following a stable plan. That is the "chaos" in the name, and it is the point rather than a bug.
What you can do on the site
- Check the countdown to see how long is left before the next merge.
- Review past winners in the Hall of Chaos to understand what kind of PRs have won before.
- Follow the GitHub activity for the current set of PRs and the voting state.
One practical caveat: the page evidence shows GitHub API errors (404) on the winners section and a "Loading..." state, with a prompt to refresh if the data does not appear. If you visit and see the same, the live GitHub data is failing to load rather than the project being empty — refreshing after a minute is the suggested fix.
Who it is for
OpenChaos.dev suits you if you want to participate in or observe a project whose evolution is decided by repeated public votes, and if you are comfortable with direction that is emergent rather than planned. It is a poor fit if you need a stable, predictable dependency with a conventional maintainer-led roadmap, since the weekly vote can change what gets merged from one cycle to the next.
If you want to influence the outcome, the actionable step is to watch the countdown, submit or support a PR before the deadline, and check the Hall of Chaos to see what has won in previous rounds.