closed to tug requests, open to remix.

All proper, I’m going to open up a historical past lesson as a result of it has been a few generations of software program engineers since this essay, and I’ve to imagine not everybody is aware of what a cathedral is. Everyone is aware of what a bazaar is as a result of they’re utilizing it daily with GitHub.

GitHub took the bazaar’s concepts—a decentralized, open, self-organizing open-source venture—and offered a workflow that lets anybody examine or contribute supply code by way of a pull request.

I’ve been pondering that there must be a brand new software program growth mannequin. We’re not going again to the cathedral, the place a small, non-public, unique group builds the supply code, with releases which might be closely deliberate, rare, and polished.

But it is clear we want one thing else now that AI is right here. The GitHub bazaar mannequin, even earlier than AI, was already displaying its cracks as a result of it created consumer-based entitlements the place everybody was nagging maintainers to merge one thing. It created actually bizarre social-structure expectations: that somebody who releases code has an obligation to keep up it and receives a commission nothing for the work.

But now that AI is right here, the dams have effectively and actually burst.

For what is the level of studying a pull request that is been generated by code? All I need is to learn and perceive the core thought. If it is a good suggestion, I would incorporate it again upstream, however there ought to be no expectation that I’ll.

You see, open supply software program is open supply by definition as a result of the license says that it is as is, and that as is allows you to remix software program.

But the issue has been that it has been perceived as too exhausting to remix software program, nevertheless it hasn’t been. It’s only a information hole problem that now not exists now that brokers are right here. Nix has existed for a very long time. If you have not seen the article that I posted a few days in the past about Nix overlays, it is best to learn it.

the world hasn’t figured out yet that you can literally just fix everything with a Nix overlay

There are many things that are uncertain in our industry right now, but one thing I am certain about, and have been for almost 13 years, is that Nix is a terrible programming language. I remember when I first learned it, it felt like pushing shit uphill. The learning cliff

So, I’m going to suggest one thing that I hope helps different open supply maintainers. This is how I’m desirous about my software program now that I launch it beneath open-source licenses.

The Remix Model

• Structure: Decentralized and compositional. Ideas unfold via unbiased overlays somewhat than converging on a single repository and a single maintainer.
• Workflow: Publish supply and intent beneath an as-is license. Others remix by writing a small Nix overlay that expresses the specified change as soon as, then reuses that derivation throughout devenv shells, Docker photos, NixOS programs and assessments, CI, and agent sandboxes—with out forking or sustaining a divergent artifact.
• Core Principle: Ideas over patches. The precious unit is a change in conduct or structure. Maintainers determine whether or not to include it, reimplement it, or ignore it. The authentic writer has no standing obligation to evaluate, combine, or keep the change.
• Social Contract: The license already permits remixing with out making a declare on anybody’s future time. Credit and visibility can nonetheless exist; there is no such thing as a ongoing upkeep responsibility. Upstream incorporation stays elective and deliberate.
• Discovery: Useful diversifications seem as a proliferation of overlays within the wild. Maintainers can pattern from that unfold in the event that they select; everybody else can seize and compose concepts just by updating their very own overlays by way of an agent.

Example: A client of a venture needs to disable Git’s capability to power push in that venture. Instead of elevating a pull request to the upstream venture, the patron makes an overlay that patches Git to refuse power pushes; that is outlined as soon as after which seems constantly in developer environments, container photos, and system assessments—with no pull request in opposition to the upstream venture.

In follow, from this level ahead, for any code I launch on GitHub, I’ll disable pull requests, preserve discussions open, and publish + keep steerage on how one can remix my software program.

The GitHub community graph gives a implausible strategy to discover the remixes within the ecosystem. Heck, you’ll be able to even run brokers over it to summarize what individuals are doing. You can even use it in an agent loop to discover remix concepts and feed them again upstream into the principle venture.

GitHub – ghuntley/nix-demo at ghuntley.com

Patch git once with a Nix overlay; use it in devenv, a NixOS VM test and a Docker image – ghuntley/nix-demo

ps. socials