NixOS governance clash, Fedora process fights, baselines

NixOS and Fedora forums drove the day with heated governance fights over team structure and discussion venues, while packaging workflow proposals and hardware baseline talks filled technical threads. Performance regressions, historical Nixpkgs tooling, and an OpenWrt routing package RC rounded out maintainer attention.

NixOS SC role in Nixpkgs core team disbandment

The NixOS Steering Committee faces accusations of micromanagement and opacity over the disbandment of the Nixpkgs core team. A Discourse thread of 53 messages from 26 participants centers on meeting notes and the decisions themselves. The outcome shapes who steers core package maintenance and how transparent that power remains in the Nix ecosystem.

Tuned-ppd regressions versus power-profiles-daemon

Fedora users report that tuned-ppd produces clear performance and efficiency regressions compared with power-profiles-daemon on new Intel hardware. The discussion cites Phoronix data and includes talk of switching back, across 13 messages from 8 participants. Laptop and workstation users tracking power management defaults have a concrete reason to watch the default stack choice.

Nixpkgs-multiverse catalogs every historical package

Nixpkgs-multiverse was announced as a tool that exposes every historical package version across Nixpkgs revisions via flakes. The release thread drew 32 messages from 16 participants on the NixOS Discourse. Developers who need to bisect behavior or rebuild from any past revision gain a structured index instead of ad-hoc git archaeology.

Fedora package review process reimagined

A proposal would move Fedora package reviews to a pull-request workflow on an intermediate forge repository. Discussion of CI and integration blockers spans 17 messages from 7 participants. The shift would change how new packages enter the distribution and how reviewers and submitters interact day to day.

F46 changes discussion limited to devel list

Fedora proposes confining F46 Change discussions to the devel mailing list only, with Discourse limited to read-only announcements. The thread produced 108 messages from 36 participants and heated debate over platform preferences and who can participate. The rule would dictate where contributors must watch and reply through the next release cycle.

Expected CPU baselines for Debian forky

Debian developers are discussing expected baseline feature tests such as SSE3 and later, ARMv8, and i386 FPU changes for forky. The debian-devel thread holds 31 messages from 10 participants. These choices set the minimum hardware that future Debian packages can assume without runtime fallbacks.

Fedora conflict of interest policy draft

The Fedora Council published a draft conflict-of-interest policy and sought feedback on scope, necessity, and GDPR implications. Thirty messages from 12 participants address the draft. Clear rules on conflicts affect trust in packaging decisions and governance outcomes.

OpenWrt pbr package RC and ucode port

The Policy-Based-Routing (pbr) package is in RC testing for a ucode port, with users reporting domain and file handling fixes. The OpenWrt forum thread contains 130 messages from 14 participants. Router administrators who rely on policy routing have a direct stake in the stability of the ported implementation.