Nix finalizes its constitution and opens the first Steering Committee election

The first election under a new constitution has a problem later elections do not. There is no existing elected committee to administer or constrain the transition. Nix's final governance constitution addresses that case directly. The constitutional assembly runs the first election, cannot stand in it, and will cease to exist when the elected Steering Committee takes office.

The 16 September finalisation announcement confirms the constitution after feedback and minor final changes. The election announcement, published the same day, opens the process of choosing the first seven-member committee. Finalising the rules and appointing the members are separate events. Today starts the latter process.

I find this transition important to Nix's long-term usefulness. A declarative configuration can be precise while the project maintaining its inputs has an unclear decision process. The constitution cannot eliminate disagreement, but it can define who has responsibility for resolving it and how that person obtains authority.

The final text makes authority explicit

The final constitution at its published revision gives the Steering Committee authority within its listed responsibilities. It can revoke a delegation when necessary, including authority a team held before the constitution. That is a significant clarification for a project with pre-existing teams and working conventions.

Delegation remains the expected operating model. The election announcement says the committee should delegate as much as possible. The constitution also requires formal decision procedures for teams, so delegation has more content than assigning a topic to a group and hoping it eventually returns an answer.

If a delegated team cannot make a decision, responsibility returns to the committee. The constitution also requires stalled decisions to be identified explicitly, with follow-up times or conditions where possible. These provisions make unresolved work part of the governing body's responsibility instead of leaving it indefinitely between teams.

That is useful even without central intervention in most changes. Maintainers can continue handling their areas while knowing where a dispute goes when local authority is insufficient. The existence of that route changes how an exceptional case can proceed, without requiring the committee to review every routine patch.

Shared policy requires approval from both bodies

The final text preserves the division between community and technical leadership in the Steering Committee and the Foundation board's legal and financial responsibilities. It also explicitly requires both bodies to approve policies concerning highly visible actions, events and relevant Foundation resources.

Sponsorship eligibility and trademark policies appear in that shared responsibility. Those decisions affect the community's public identity as well as the legal entity that manages relationships and assets. Requiring both approvals makes the overlap a stated procedure rather than a dispute about which body ought to prevail.

The budget arrangement remains distinct. The Foundation decides how much funding is available within broad categories, and the committee chooses priorities within those limits. An elected priority cannot create money, while the existence of a funding category does not settle every priority inside it.

Constitutional changes affecting the board's authority, responsibilities or appointment procedures also require board approval. That limits the committee's ability to rewrite the relationship unilaterally. The shared institution is therefore constrained through a combination of elected authority and the Foundation's continuing obligations.

Board appointments now have a defined objection process

The August draft used a joint selection-committee arrangement for changes to the Foundation board. The final text replaces that with notification and objection procedures. Before a new appointment, the board informs the Steering Committee and gives it an opportunity to object by simple majority.

An objection to a new appointment binds the board unless the committee withdraws it. The committee must privately provide written reasons. That supplies both a concrete power and a requirement to explain its use, instead of leaving the objection as an informal consultation with no specified effect.

Renewals follow a different rule. Board terms last no more than two years. The board can approve renewal, the Steering Committee can object by supermajority, and the board can override that objection only unanimously. The constitution distinguishes appointing a new member from retaining an existing one.

The committee can also request a board decision, with published votes, on removing a particular member. That does not give it an unrestricted power to dismiss the board. It creates a route to require a decision and make the board's response visible.

These details matter because accountability depends on what an objection actually does. A rule that permits comment without binding effect is different from a veto, and a veto on initial appointment is different from the renewal procedure. The final constitution names those distinctions.

The electorate includes a route for non-code contributions

The voting rules consider official contributions during the four years before a cutoff date. Automatic eligibility comes through authored merged work totalling at least 25 commits, or through exercising commit access to merge a pull request in the NixOS GitHub organisation. The final wording makes that second route about exercising access, not merely having a proposal accepted by someone else.

People whose contributions are not fully visible there can request an exception. The final constitution describes roughly equivalent contributions and includes infrastructure maintenance, participation in official teams and event organisation. It therefore recognises work needed to keep the project functioning beyond authored source changes.

The election announcement makes that route actionable. Automatically eligible voters receive an email and membership or an invitation to the voters' GitHub team. Someone who appears on the team but has no email can check the address used for election communication. Someone outside the automatic list can consider an exception request.

The distinction prevents missing email from being treated as definitive evidence of ineligibility. There is a communication mechanism and a contribution rule, and failure in the first does not establish failure in the second. The announcement provides separate instructions for those situations.

The first committee receives staggered terms

The constitution provides annual elections for alternating halves of the seven seats. To establish that pattern, the first election assigns four two-year terms and three one-year terms. Higher-ranked winning candidates receive the longer terms. Later rotation can then happen without replacing the entire committee every year.

Assembly members administer the first election and are ineligible for election to the first committee. They join the new committee as non-voting members for six months to transfer context. This gives the elected body access to the assembly's knowledge while keeping its voting authority with the election winners.

The first-election provision also says all nominees become candidates because no existing Steering Committee is present to decide disqualifications. That addresses a specific transition question instead of quietly assigning the assembly every power of the future committee. It is part of the procedure available today, before any result exists.

I prefer that explicit treatment of the initial handover. Founding processes can otherwise acquire exceptions that no later participant can reconstruct. Here the constitution states who administers the election and which role those people will have after the committee is appointed.

Conflicts must be classified before voting

The final text preserves limits on shared conflicts of interest, including a common employer or payer for Nix work. It adds a public commitment before voting to the candidate pairs the election committee considers to share a conflict. Voters can therefore know how those constraints apply before choosing among the candidates.

This is consequential because the soft limit affects which candidates can take seats after an election. Disclosing the classification only after voting would leave participants unable to assess that effect in advance. The final procedure moves that information to the point where it can inform the electorate.

The harder limit during a term addresses later changes such as employment shifts or acquisitions. Those events can change the committee's relationships without another election. The constitution specifies how uninvolved members assess a suspected violation and how the limit is restored.

The election has a published sequence

The announcement sets 29 September as the nomination deadline and schedules voting for 7 through 20 October, with results expected on 23 October. These are the announced dates as the process opens, rather than a report that any later stage has occurred. Candidate questions and answers have their own deadlines before voting.

That question period gives voters a way to assess how nominees intend to use the authority the constitution defines. A position statement can name priorities, while answers can explain how a candidate would handle a disputed delegation or a shared policy decision. The rules have now been finalised, and the next task is choosing the people who will operate them.