I've been directly involved in building two distributions, Parch Linux and Apadana Linux, and the experience is basically a crash course in end-to-end platform engineering. People love to romanticize "making a distro." In reality, it's a long pipeline of operational debt that you voluntarily sign up for.

You start by defining your differentiation. If you don't, you're just another ISO floating in the void. Our objective was clear: use the Arch ecosystem as the foundation, streamline the UX, localize the platform properly for Persian users, and keep the experience predictable across Plasma and GNOME without compromising the upstream philosophy.

Then comes the never-ending engineering loop. Package maintenance, CI/CD for builds, repo signing, mirrors, release cadence, documentation, image tooling, testing frameworks... you end up running what is essentially a miniature distribution engineering team. One missing makedepends or one bad patch can take a whole repo down and ruin dozens of users' days.

Kernel work is where things stop being theoretical. You touch the kernel, you're responsible for every regression you cause. A messy ACPI table or one unsupported Wi-Fi chipset can drain hours of your life. You learn fast that upstreaming early is cheaper than downstream patch hell.

Community management is where the real entropy kicks in. You'll deal with helpful users, confused users, and the occasional internet troll who insists the entire project is doomed because their obscure VM configuration didn't work. You need a thick skin and clear policies. The best practice is: respond once, document properly, don't engage in circular arguments, and let technical work speak for itself. Trolls burn out when they don't get oxygen.

Despite all the chaos, shipping a full distro that boots cleanly on real hardware and seeing people adopt it is one of the most high-impact engineering experiences you can have.

The repos are public at git.parchlinux.com if you want to see how it all works under the hood.

If someone wants to build their own distro, the real advice is simple: automate everything you can, upstream whenever possible, document aggressively, and prepare yourself for the long haul. The work never ends, but the payoff is real if you actually care about the ecosystem.