-
-
Notifications
You must be signed in to change notification settings - Fork 74
Nix Steering Committee Election 2024 #1
Comments
Since the team notification apparently didn't work, let's try it again with another @NixOS/voters-2024 mention, maybe GitHub wasn't ready the first time. Also specifically:
Please set/update your Email to be able to vote. |
Continuation of the above because of the 50 mentions per comment limit:
Please set/update your Email to be able to vote. |
My address in |
@l0b0 Let's discuss in the election support Matrix channel |
Additional people whose Email failed to be sent: @tjni @avnik @lovek323 @luc65r @panicgh @oluceps @poscat0x04 @samuelgrf @pupbrained @foo-dogsquared Please check/update your email address. |
As a first step towards a better governance for official Nix projects, we are happy to announce the kick-off of the first Nix Steering Committee election!
The Steering Committee will be the primary community leadership body, responsible for steering the official Nix projects -- organisationally, socially, and technically. This includes making decisions over what is official, managing teams, approving NixOS Foundation policies relevant for the community, being the final escalation point, and more as detailed in the Nix Governance Constitution.
While the Steering Committee is given the authority to make decisions within the scope of its responsibilities directly, it is expected to delegate as much as possible.
Note that you can also read and publicly discuss this announcement on Discourse.
Participating
If you're pinged by the mention of @NixOS/voters-2024 here, it means you're automatically eligible to vote.
If you didn't also receive an announcement email, make sure to check and optionally update your email address.
Members of the GitHub team can:
If you have any questions or need support, please get in touch with the Election Committee.
Timeline
The results are expected to be announced just before NixCon 2024 in Berlin, which starts on 2024-10-25.
The text was updated successfully, but these errors were encountered: