Nobody reads source code anymore
The code still exists; people just stopped reading it. It scrolls past by the thousand lines, written and checked by machines.
The next GitHub will not look like GitHub.
coss.com is crowd opinionated source software. Contribute in English, not code. The maintainers decide, their software factory builds, and everyone watches it ship.
prompt request #482
opened by a user · English
“Let me filter the bookings list by date. Quick presets like ‘this week’ and ‘last 30 days’ would cover almost everything I do.”
- maintainer · ApprovedYes. Keep the existing range picker, add presets above it. Sent to the factory.
- factory · BuiltPreview is up with screenshots of light and dark. All end-to-end tests pass.
preview-482.example.coss.app
Watch the idea
Why the next GitHub won't look like GitHub, and what contributing looks like when nobody writes the code by hand.
Open source is dead. Heck, source code is dead.
Pull requests review themselves
Types, tests, a security scan and a review agent sign off on a pull request before a person would have opened the tab.
Systems heal themselves
When something breaks in production, the system rolls back, patches and recovers on its own. Nobody opens the source to find out why.
Open source died of exposure
Every public line is an attack surface. Potential security vulnerabilities made shipping your source in the open a liability, not a virtue.
Reading code died of volume
More code is pushed in a day than a team could review in a year, and AI systems now read it better than we do.
Guardrails are what matter now
End-to-end tests and AI-automated QA decide whether software works. Not a human squinting at a diff.
Open a Prompt Request, not a pull request
Contribute in English, not code. A Prompt Request is an idea with a decision attached, and a software factory waiting at the other end.
- 1
Write a prompt
Anyone opens a Prompt Request instead of a pull request: what should change, and why, in plain English.
- 2
Maintainers decide
They read it and approve or decline, with a comment either way. Nobody is left wondering.
- 3
The factory builds
Approved requests go straight to the maintainer's software factory, such as Shipyard, which writes, tests and ships the change.
- 4
Everyone sees it
The factory notifies the author and can update everyone publicly with a preview URL and screenshots.
Maintainers set the rules
Let the routine through on its own and keep a hand on everything that matters. Auto-allow certain kinds of changes, or require approval for each one.
Auto-allow
goes straight to the factory- Copy and translation fixes
- Dependency updates that pass every test
- Accessibility improvements
- Any kind of change you choose to trust
Require approval
waits for a maintainer- New features and changed behaviour
- Anything touching auth, billing or data
- Design and product direction
- Every single change, if that's how you run it
Collaborative, but opinionated
Software is built by the crowd, but the source is opinionated by the maintainers. Ideas come from everywhere; taste stays where it belongs.
- Who contributes
- Everyone, in English
- Who decides
- The maintainers
- Who writes the code
- The software factory
- Who checks it works
- End-to-end tests and AI QA
- Who sees the result
- Everyone, with a preview URL
- Whose software it is
- Still the maintainers'
Launch your repository on coss.com.
Every repository, private or public, can launch on coss.com today. Bring your guardrails and your opinions; the crowd brings the prompts.