Nixpkgs has a due-process problem

4 hours ago

Nixpkgs has a due-process problem where governance rules are vague, leading to arbitrary exercise of power.
The author was removed from Nixpkgs commit access for a 'consistent pattern of bad judgment' without a defined review or restoration process.
The removal rule allows one member to remove a committer without binding safeguards like notice, response period, or appeal.
A pull request adding a minimal AGENTS.md file was closed as 'rejected by the community' based on informal feedback, lacking a defined decision-making process.
A critical glibc patch review was blocked indefinitely by an unavailable reviewer, causing stagnation despite significant work.
Personal attacks and speculation about motives emerged in reviews, conflating technical concerns with personal judgments.
Due process failures are structural, not unique to specific cases, and require clear rules for removals, blocks, and policy decisions.
Reforms should separate emergency suspension from indefinite removal, require actionable reviews, and define project-wide decision-making.
Mechanical rules should be automated, and claims about policy effectiveness should be tested with data.
Clear rules and legitimate processes protect all contributors, regardless of faction, ensuring long-term collaboration.

Code review can be used constructively to improve code and skills, but also obstructively with dark-side antipatterns.
The 'Death of a Thousand Round Trips' involves repeatedly nitpicking to delay the patch, often across time zones.
Hostage-taking: demanding unrelated work in exchange for approving a critical patch.

AI-driven development is breaking traditional code review: faster code generation caps velocity at slow human reviews.
Asynch diff-centered code review, ~20 years old, fails in an era where writing code is cheap but reviewing isn't.
Diffs lack context, requiring reviewers to reconstruct intent and design, adding expensive overhead.

Supreme Court decisions impacting broadcasters require immediate consideration.
Declaration of Independence drafting process involved committee work and revisions.
Concerns about AI usability lagging behind rapid evolution halfway through 2026.

AI accelerates execution but erodes judgment by replacing the developmental friction where judgment was built.
Organizations face a hidden gap: more output but no proportional business impact, as experienced judgment is sidelined by plausible AI-generated options.
Judgment forms through observation and consequence—proximity to real decisions and ownership of outcomes—not through reading summaries.

The cost of producing plausible code has collapsed, but broad claims about dramatic speedups, obsolete practices, or halving headcount are unproven.
Management practices should be audited based on their underlying assumptions: those resting on code cost need review; those on human coordination, trust, or verification remain valid.
Evidence of speedups is smaller than noise; honest instrumentation is needed to measure actual acceleration, not felt speed.

Hasty Briefsbeta