diff --git a/core/astro.config.mjs b/core/astro.config.mjs index 0a337e95c5..cc582a6cd1 100644 --- a/core/astro.config.mjs +++ b/core/astro.config.mjs @@ -57,6 +57,9 @@ export default defineConfig({ vite: { plugins: [tailwindcss()], }, + redirects: { + '/values': '/governance', + }, env: { schema: { THEME: envField.string({ diff --git a/core/src/components/ui/Quotation.astro b/core/src/components/ui/Quotation.astro index 67b3249ce6..3d37c62222 100644 --- a/core/src/components/ui/Quotation.astro +++ b/core/src/components/ui/Quotation.astro @@ -1,9 +1,14 @@ --- - +const { dark } = Astro.props; ---
diff --git a/core/src/content/menus/header.yaml b/core/src/content/menus/header.yaml index 2a88869668..4f27db18fa 100644 --- a/core/src/content/menus/header.yaml +++ b/core/src/content/menus/header.yaml @@ -5,8 +5,8 @@ items: link: /download - name: Learn link: /learn - - name: Values - link: /values + - name: Governance + link: /governance - name: Community link: /community - name: Blog diff --git a/core/src/pages/governance.astro b/core/src/pages/governance.astro new file mode 100644 index 0000000000..6b8775737a --- /dev/null +++ b/core/src/pages/governance.astro @@ -0,0 +1,354 @@ +--- +import Container from '../components/layout/Container.astro'; +import Divider from '../components/layout/Divider.astro'; +import PageHeader from '../components/layout/PageHeader.astro'; +import Layout from '../layouts/Layout.astro'; + +import Quotation from '@/components/ui/Quotation.astro'; +import { getCollection, getEntry } from 'astro:content'; +import Citation from '../components/ui/Citation.astro'; + +const teams = await getCollection('teams'); +const foundationBoard = await getEntry('teams', '010_foundation-board'); +const steeringCommittee = await getEntry('teams', '000_steering-committee'); + +const getMemberLink = (member) => { + if (member.github) + return [`https://github.com/${member.github}`, member.github]; + else if (member.discourse) + return [ + `https://discourse.nixos.org/u/${member.discourse}`, + member.discourse, + ]; + else return [null, member.name]; +}; +--- + + + + +

+ Nix Leadership Bodies +

+

The Nix community is guided by two leadership bodies:

+
+
+

+ The Steering Committee (SC) +

+ + 7 elected individuals to represent the community + + + Responsibilities: Technical and community decisions and delegation + + + Members: + { + steeringCommittee.data.members.map((member, idx) => { + const data = getMemberLink(member); + if (data[0]) { + return ( + <> + {' '} + ${data[1]} + {idx < foundationBoard.data.members.length - 1 ? ',' : ''} + + ); + } else { + return data[1]; + } + }) + } + + More Info +
+
+

+ The Foundation Board +

+ + Board members of the Stichting NixOS Foundation, a non-profit + organisation in Utrecht, the Netherlands + + + Responsibilities: Legal, financial and partnership decisions and + delegation + + + Members: + { + foundationBoard.data.members.map((member, idx) => { + const data = getMemberLink(member); + if (data[0]) { + return ( + <> + {' '} + ${data[1]} + {idx < foundationBoard.data.members.length - 1 ? ',' : ''} + + ); + } else { + return data[1]; + } + }) + } + + More Info +
+
+

+ Local decisions are made in a distributed way by the {teams.length} teams, among many other ones not listed on the website and many more + individual specialists, responsible for various areas. From the leadership + bodies down to individual contributors, almost everybody is here as a + passionate volunteer. +

+

+ Governance Constitution +

+

+ The Nix Governance Constitution describes each bodies responsibilities, how the steering committee is elected, + and how decisions are made inside the steering committee. +

+

+ Steering Committee Elections +

+

+ Every year, the Nix community elects members to the steering committee. + Each member holds a two-year term, with elections held annually to fill at + least half of the seats. You can read more about the election process in + the Nix Governance Constitution. +

+

+ The elections are documented in GitHub repositories under the NixOS organization. +

+

+ Current and past elections: + 2025, 2024 +

+ + +
+ +

+ Values + πŸ”— +

+ + +

+ Communities form when different people unite around a common purpose. + Shared values guide decision making, and community goals supersede + individual interests and agendas. +

+ +

+ The Open Source Way +

+ + +

+ Our common purpose is to develop, propagate, and promote the adoption of + the purely functional software deployment model. Our values help us achieve this purpose by guiding decisionmaking + across the community, keeping us moving in a common direction. This + document captures our core values so that they can be shared and + referenced by everyone in the community. +

+ +

+ What is a value? + πŸ”— +

+ +

+ Values are not a Code of Conduct, they do not + define governance structures, and they do not provide specific policies. + Instead, values inform the decisions we make about these things. A good test + for whether something is a value is: +

+ + + If a statement can be invoked by anyone in an organization, and cause a + decision to be re-evaluated or changed, without regard to anyone’s rank + or title, then you have a bona fide [i.e. genuine] value. If it doesn’t + work that way, then it’s not a value. + + +

+ To apply in many situations, values must be high-level, abstract + concepts. Therefore, in the text below, each value is presented as a + heading followed by an elaboration of its meaning. This is meant as a + starting point for interpretation, not a comprehensive definition. The + heading and the elaboration have equal importance. +

+

+ The values + πŸ”— +

+ +

+ Respect and civility + πŸ”— +

+ +

+ We treat each other with respect and civility. No matter one's + individual identity, circumstances, level of contribution to the + project, or status, everyone has the right to respect, and everyone has + the duty to treat others with respect. We prioritise project health over + individual interests. People with higher visibility within the project + or towards the public are subject to higher expectations for their + conduct. +

+ +

+ People come first + πŸ”— +

+ +

+ We are here, first and foremost, as individuals working together. Our + priority here is to work on Nix projects for the benefit of all their + contributors and users. We value building excellent software with a + vibrant and diverse community. Individuals gain trust and status by + doing the work. Organisations gain prestige by funding the work of + individuals and providing resources to support the project. +

+ +

+ Free software and choice over lock-in + πŸ”— +

+ +

+ Nix projects are and will always remain free software. We value working together with the broader free software community. + Free software is our priority, but we also support our users' needs to + use non-free software, when practical. +

+ +

+ Distribute decisionmaking widely + πŸ”— +

+ +

+ We are a synthesis of varied but overlapping communities. We rely on + distributed approaches: asynchronous communication, clear ownership, + deep-dive taskforces, and local decisionmaking. We focus our attention + on working together on our shared goals and working separately in a + non-interfering way when our goals are independent. We build trust + primarily by working together on Nix projects. +

+ +

+ Automation over process and toil + πŸ”— + + Toil is work that tends to be manual, repetitive, automatable, interrupt-driven, + devoid of enduring value, and scaling linearly with growth. + +

+ +

+ We are a global community, and disseminating information and maintaining + processes can be difficult. We are also a large project with a lot of + hard and repetitive work. Therefore, we value automation over toil, + while recognizing that not all toil can be automated. Automation reduces + toil, but people are still accountable. Adding new toil needs a very + strong justification. We build automation and processes that make the + best use of our contributors' limited time and energy. +

+ +

+ Stable evolution over stagnation or chaos + πŸ”— +

+ +

+ Openness to new ideas and evolution is part of what made Nix great. We + continue to foster that evolution while encouraging development of + re-usable building blocks and well-defined, stable interfaces. We value + experimenting with designs and concepts, and folding successful + experiments back into continuous improvement for stable components. The + larger the impact an action has, the more care and discussion is + warranted before taking the action. Our leaders have a duty to find, + support, and promote new contributors β€” and eventually step aside for + new leaders. +

+ +
+ + + diff --git a/core/src/pages/values.astro b/core/src/pages/values.astro deleted file mode 100644 index 3900d645e9..0000000000 --- a/core/src/pages/values.astro +++ /dev/null @@ -1,215 +0,0 @@ ---- -import Container from '../components/layout/Container.astro'; -import Divider from '../components/layout/Divider.astro'; -import PageHeader from '../components/layout/PageHeader.astro'; -import Layout from '../layouts/Layout.astro'; - -import Citation from '../components/ui/Citation.astro'; -import Quotation from '../components/ui/Quotation.astro'; - -// The source of truth for this document is https://github.com/NixOS/org/blob/main/doc/values.md. ---- - - - - -

- Introduction - πŸ”— -

- - -

- Communities form when different people unite around a common purpose. - Shared values guide decision making, and community goals supersede - individual interests and agendas. -

- -

- The Open Source Way -

- - -

- Our common purpose is to develop, propagate, and promote the adoption of - the purely functional software deployment model. Our values help us achieve this purpose by guiding decisionmaking - across the community, keeping us moving in a common direction. This - document captures our core values so that they can be shared and - referenced by everyone in the community. -

- -

- What is a value? - πŸ”— -

- -

- Values are not a Code of Conduct, they do not define - governance structures, and they do not provide specific policies. Instead, - values inform the decisions we make about these things. A good test for whether something is a value is: -

- - - If a statement can be invoked by anyone in an organization, and cause a - decision to be re-evaluated or changed, without regard to anyone’s rank or - title, then you have a bona fide [i.e. genuine] value. If it doesn’t work - that way, then it’s not a value. - - -

- To apply in many situations, values must be high-level, abstract concepts. - Therefore, in the text below, each value is presented as a heading - followed by an elaboration of its meaning. This is meant as a starting - point for interpretation, not a comprehensive definition. The heading and - the elaboration have equal importance. -

- - - -
- -

- The values - πŸ”— -

- -

- Respect and civility - πŸ”— -

- -

- We treat each other with respect and civility. No matter one's - individual identity, circumstances, level of contribution to the - project, or status, everyone has the right to respect, and everyone has - the duty to treat others with respect. We prioritise project health over - individual interests. People with higher visibility within the project - or towards the public are subject to higher expectations for their - conduct. -

- -

- People come first - πŸ”— -

- -

- We are here, first and foremost, as individuals working together. Our - priority here is to work on Nix projects for the benefit of all their - contributors and users. We value building excellent software with a - vibrant and diverse community. Individuals gain trust and status by - doing the work. Organisations gain prestige by funding the work of - individuals and providing resources to support the project. -

- -

- Free software and choice over lock-in - πŸ”— -

- -

- Nix projects are and will always remain free software. We value working together with the broader free software community. - Free software is our priority, but we also support our users' needs to - use non-free software, when practical. -

- -

- Distribute decisionmaking widely - πŸ”— -

- -

- We are a synthesis of varied but overlapping communities. We rely on - distributed approaches: asynchronous communication, clear ownership, - deep-dive taskforces, and local decisionmaking. We focus our attention - on working together on our shared goals and working separately in a - non-interfering way when our goals are independent. We build trust - primarily by working together on Nix projects. -

- -

- Automation over process and toil - πŸ”— - - Toil is work that tends to be manual, repetitive, automatable, interrupt-driven, - devoid of enduring value, and scaling linearly with growth. - -

- -

- We are a global community, and disseminating information and maintaining - processes can be difficult. We are also a large project with a lot of - hard and repetitive work. Therefore, we value automation over toil, - while recognizing that not all toil can be automated. Automation reduces - toil, but people are still accountable. Adding new toil needs a very - strong justification. We build automation and processes that make the - best use of our contributors' limited time and energy. -

- -

- Stable evolution over stagnation or chaos - πŸ”— -

- -

- Openness to new ideas and evolution is part of what made Nix great. We - continue to foster that evolution while encouraging development of - re-usable building blocks and well-defined, stable interfaces. We value - experimenting with designs and concepts, and folding successful - experiments back into continuous improvement for stable components. The - larger the impact an action has, the more care and discussion is - warranted before taking the action. Our leaders have a duty to find, - support, and promote new contributors β€” and eventually step aside for - new leaders. -

- -
- - -