EC 2026 + Standing EC
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 48
- Forks
- 36
- Avg merge
- 2m
- Merged PRs (30d)
- 3
Description
We would like to propose the following people to be on the Election Committee for the 2026 SC election:
- @ners
- @RossComputerGuy
- @iamanaws
Additionally, two more volunteers have stepped up to support in any way that might be needed:
- @ethancedwards8
- @trespaul
Two independent requests:
- Create the repository
NixOS/SC-election-2026and anec-2026team (with the 5 members above) that administer it so that we may begin the process of the 2026 SC election. - Create a standing EC team with the above 5 members, which can onboard future members as needed. The purpose of the standing EC is to facilitate a quick formation of an EC in the event of either regular or special elections. From a pool of all its members, a 3-member EC can quickly be formed and announced, kicking off the process.
Each member of the EC and the standing EC will also require Zulip and Freescout access.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the two requested actions in the issue: create NixOS/SC-election-2026 and the ec-2026 team, then establish the standing EC team. Confirm the five listed members and required Zulip and Freescout access with the relevant organization administrators; this is done when the repository, teams, memberships, and access are provisioned as requested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100