We are the "thin blue line" that is trying to keep the code high quality

Upstream vs. Forks and the Role of Git

• Several comments argue “just keep your own branch” or use custom/forked kernels, but others counter that out-of-tree work fails socially and practically: users and vendors want “in-tree,” and Linux intentionally makes long‑term forks painful to maintain.
• API instability is identified as the core issue, not version control. When code is upstream, API changers are obligated to keep it working; when it’s in a fork, the fork owner bears all breakage.
• Some suggest better VCS or formal methods might help, but multiple replies insist the hard problem is semantic dependencies and shifting internal APIs, not tooling.

Rust in the Kernel and Maintainer Power

• There’s broad agreement that maintainers are overloaded and burned by “drive‑by” corporate contributions whose authors disappear. This is used to justify being conservative and demanding long‑term commitment.
• Critics say this doesn’t address the specific problem: some maintainers are explicitly blocking Rust work or particular subsystems for non-technical reasons, creating “no path forward” despite prior high‑level approval for Rust.
• Debate centers on whether maintainers owe contributors a clear decision (“yes under conditions” vs “no Rust here at all”) and consistent policy, versus having no obligation beyond their own judgment.
• “Just fork it” is proposed repeatedly; others counter that a sustainable Linux fork with broad hardware/software support is near-impossible without enormous backing.

Culture, Gatekeeping, and Burnout

• Many recount avoiding kernel work due to abrasive behavior, calling it a classic case of gatekeepers driving away would‑be maintainers and paying an opportunity cost in lost talent.
• Defenders argue that kernel work is inherently brutal and requires hard‑nosed, risk‑averse maintainers who must live with the consequences when things break.
• Some see the Rust conflict as a continuation of old FOSS schisms (gcc/egcs, vim/neovim) and predict that, if a fork proves itself, history will quietly rewrite around today’s drama.

“Thin Blue Line” Metaphor and Politics

• The “thin blue line” self‑description draws strong criticism: in the US context it’s widely seen as tied to police impunity, authoritarianism, and even white nationalism.
• Others argue for assuming ignorance rather than malice, noting the phrase’s older or non‑US connotations, or comparing it to reclaimed/contested symbols.
• A side debate emerges over policing itself—whether police serve the community, capital, or primarily themselves—showing how quickly the metaphor drags in contentious politics unrelated to kernel code.