There is a mass of people alive right now who, on any given Tuesday evening, will open a laptop, navigate to a repository they do not own, and write code for free.
No one asked them to. No one is paying them. The code they write will be used by strangers in countries they will never visit, in products they will never see, to solve problems they will never know existed. They will receive, in return, a green square on a grid that no one outside their profession understands.
This is open source. It is the largest collaborative project in human history, and we talk about it as if it were normal.
THE CATHEDRAL AND THE BAZAAR
In 1997, Eric Raymond published an essay that described two models of software development. The cathedral: a small group of architects building in private, revealing the finished work when it is ready. The bazaar: a chaotic, public process where anyone can contribute, inspect, or argue.
He was describing Linux. But he was also describing something older. The bazaar model is how science worked before journals locked it behind paywalls. It is how cities were built before urban planning. It is how language evolves - collectively, messily, without anyone in charge.
Open source did not invent this. It rediscovered it.
WHAT THE GRAPH SHOWS
When you generate a Codex Stellarum atlas for a prolific open-source contributor, something specific happens. The graph is dense. Not dense in the way a startup founder's graph is dense - concentrated bursts of intense activity on a single project. Open-source contributors have a different pattern. It is broad. Consistent. Spread across months and years like a low, constant hum.
This is the signature of maintenance. Of someone who shows up, week after week, to review pull requests, fix edge cases, update dependencies, respond to issues filed by strangers at 3am in a timezone twelve hours away.
It is the least glamorous work in software. It is also the most important.
THE GIFT ECONOMY
Anthropologists have a term for economies where goods are given without explicit expectation of return: gift economies. Marcel Mauss wrote about them in 1925. Potlatch ceremonies of the Pacific Northwest. Kula ring exchanges in Melanesia. Systems where giving creates social bonds stronger than any contract.
Open source is a gift economy operating at planetary scale.
A developer in São Paulo fixes a bug in a library maintained by someone in Helsinki. A student in Lagos writes documentation for a framework built by a team in San Francisco. Nobody signs anything. Nobody invoices anyone. And yet the system works - not despite the absence of contracts, but because of it.
The green squares on a contribution graph are the record of these gifts. Each one is a small act of generosity disguised as a commit.
THE INVISIBLE INFRASTRUCTURE
Every time you use a banking app, book a flight, send a message, or read the news, you are standing on open source. The web server is probably Nginx or Apache. The database is probably PostgreSQL or MySQL. The programming language is probably Python, JavaScript, or Go - all open source. The operating system running the server is almost certainly Linux.
These are not side projects. They are the foundation of the digital economy. And they are maintained, in many cases, by a handful of people who do it because someone has to.
The contribution graph of someone who maintains a critical open-source dependency does not look like a founder's graph. It does not have the dramatic peaks and valleys of a startup sprint. It looks like a steady heartbeat. Quiet, persistent, unbroken. The kind of pattern that is easy to take for granted until it stops.
COMPANIES AND THE COMMONS
Something interesting happens when you generate an org atlas on Codex Stellarum. You see not just the company's private output, but its public contribution - the code it has chosen to give away.
Some companies treat open source strategically: release the framework, sell the hosting. Some treat it as recruitment marketing: look at our engineering culture. Some treat it as genuine contribution: we use these tools, we should help maintain them.
You can see which is which. A company that open-sources one flagship project has a graph with a single bright cluster. A company that contributes broadly across the ecosystem has a graph that looks like the individual open-source contributor - wide, steady, distributed.
The atlas does not judge which approach is better. But it makes the pattern visible.
WHY PEOPLE DO IT
Ask an open-source contributor why they do it and you will get a dozen different answers. For the craft. To learn. To give back. Because it is fun. Because the alternative - closed, proprietary, locked away - feels wrong. Because they used a library once when they were stuck at 2am on a deadline, and it saved them, and they never found out who wrote it, and now they want to be that person for someone else.
The reasons are as varied as the people. But the pattern on the graph is consistent: sustained, voluntary, distributed effort over time. It is not the pattern of obligation. It is the pattern of care.
THE RECORD
Contribution graphs are imperfect records. They do not capture code review comments, issue triage, community moderation, documentation edits that do not touch code, or the countless hours spent in discussions that shape a project's direction without ever producing a commit.
But they capture something. They capture the rhythm. The showing up. The Tuesday evenings and Saturday mornings and lunch breaks spent on code that belongs to everyone and no one.
When you render that rhythm as a star atlas - when you see fifteen years of open-source contribution mapped onto a vintage celestial chart - you are looking at something remarkable. Not because the visualisation is clever, but because the underlying behaviour is extraordinary.
Thousands of people, working for free, building the commons. And the only record most of them will ever have is a grid of green squares that resets every year.
Unless someone charts it among the stars.
Your open-source contributions deserve more than a green grid. See your sky →
Write about developers? Join our affiliate programme - 25% revenue share, 10% off for your audience.