diff --git a/package-lock.json b/package-lock.json index fe1d229ca6..bc830996cb 100644 --- a/package-lock.json +++ b/package-lock.json @@ -21,7 +21,7 @@ "astro-heroicons": "^0.3.0", "astro-icon": "^0.8.2", "astro-seo": "^0.8.0", - "daisyui": "^3.7.3", + "daisyui": "^4.0.4", "htmx.org": "^1.9.9", "markdown-it": "^14.0.0", "sanitize-html": "^2.11.0", @@ -1999,11 +1999,6 @@ "integrity": "sha512-dOy+3AuW3a2wNbZHIuMZpTcgjGuLU/uBL/ubcZF9OXbDo8ff4O8yVp5Bf0efS8uEoYo5q4Fx7dY9OgQGXgAsQA==", "optional": true }, - "node_modules/colord": { - "version": "2.9.3", - "resolved": "https://registry.npmjs.org/colord/-/colord-2.9.3.tgz", - "integrity": "sha512-jeC1axXpnb0/2nn/Y1LPuLdgXBLH7aDcHu4KEKfqw3CUhX7ZpfBSlPKyqXE6btIgEzfWtrX3/tyBCaCvXvMkOw==" - }, "node_modules/comma-separated-tokens": { "version": "2.0.3", "resolved": "https://registry.npmjs.org/comma-separated-tokens/-/comma-separated-tokens-2.0.3.tgz", @@ -2182,16 +2177,23 @@ "node": ">=8.0.0" } }, + "node_modules/culori": { + "version": "3.2.0", + "resolved": "https://registry.npmjs.org/culori/-/culori-3.2.0.tgz", + "integrity": "sha512-HIEbTSP7vs1mPq/2P9In6QyFE0Tkpevh0k9a+FkjhD+cwsYm9WRSbn4uMdW9O0yXlNYC3ppxL3gWWPOcvEl57w==", + "engines": { + "node": "^12.20.0 || ^14.13.1 || >=16.0.0" + } + }, "node_modules/daisyui": { - "version": "3.9.4", - "resolved": "https://registry.npmjs.org/daisyui/-/daisyui-3.9.4.tgz", - "integrity": "sha512-fvi2RGH4YV617/6DntOVGcOugOPym9jTGWW2XySb5ZpvdWO4L7bEG77VHirrnbRUEWvIEVXkBpxUz2KFj0rVnA==", + "version": "4.0.7", + "resolved": "https://registry.npmjs.org/daisyui/-/daisyui-4.0.7.tgz", + "integrity": "sha512-D84DnNDZKcamwNsxCMrwYaddyz5kC6VO6oe30nM1x67GzCAfarfd3Ar1rpLGXCIqSsEoNZUHO8EcXvX93W2ZkA==", "dependencies": { - "colord": "^2.9", "css-selector-tokenizer": "^0.8", - "postcss": "^8", - "postcss-js": "^4", - "tailwindcss": "^3.1" + "culori": "^3", + "picocolors": "^1", + "postcss-js": "^4 }, "engines": { "node": ">=16.9.0" diff --git a/package.json b/package.json index 178c20b120..d8085f0b7b 100644 --- a/package.json +++ b/package.json @@ -23,7 +23,7 @@ "astro-heroicons": "^0.3.0", "astro-icon": "^0.8.2", "astro-seo": "^0.8.0", - "daisyui": "^3.7.3", + "daisyui": "^4.0.4", "htmx.org": "^1.9.9", "markdown-it": "^14.0.0", "sanitize-html": "^2.11.0", diff --git a/public/images/commercial-support-logos/5inaries.png b/public/images/commercial-support-logos/5inaries.png new file mode 100644 index 0000000000..0e1f046d34 Binary files /dev/null and b/public/images/commercial-support-logos/5inaries.png differ diff --git a/public/images/commercial-support-logos/determinate-systems.svg b/public/images/commercial-support-logos/determinate-systems.svg new file mode 100644 index 0000000000..65cb04db4e --- /dev/null +++ b/public/images/commercial-support-logos/determinate-systems.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/public/images/commercial-support-logos/engelen-open-source.png b/public/images/commercial-support-logos/engelen-open-source.png new file mode 100644 index 0000000000..950cf5bbf5 Binary files /dev/null and b/public/images/commercial-support-logos/engelen-open-source.png differ diff --git a/public/images/commercial-support-logos/enlambda.png b/public/images/commercial-support-logos/enlambda.png new file mode 100644 index 0000000000..1e13bb6e9c Binary files /dev/null and b/public/images/commercial-support-logos/enlambda.png differ diff --git a/public/images/commercial-support-logos/flox.png b/public/images/commercial-support-logos/flox.png new file mode 100644 index 0000000000..39e66d8f9e Binary files /dev/null and b/public/images/commercial-support-logos/flox.png differ diff --git a/public/images/commercial-support-logos/helsinki-systems.png b/public/images/commercial-support-logos/helsinki-systems.png new file mode 100644 index 0000000000..3271e4ed16 Binary files /dev/null and b/public/images/commercial-support-logos/helsinki-systems.png differ diff --git a/public/images/commercial-support-logos/immutable-solutions.png b/public/images/commercial-support-logos/immutable-solutions.png new file mode 100644 index 0000000000..9a93accba2 Binary files /dev/null and b/public/images/commercial-support-logos/immutable-solutions.png differ diff --git a/public/images/commercial-support-logos/nix-how.png b/public/images/commercial-support-logos/nix-how.png new file mode 100644 index 0000000000..f75e5e951f Binary files /dev/null and b/public/images/commercial-support-logos/nix-how.png differ diff --git a/public/images/commercial-support-logos/nixcademy.svg b/public/images/commercial-support-logos/nixcademy.svg new file mode 100644 index 0000000000..09bf13604d --- /dev/null +++ b/public/images/commercial-support-logos/nixcademy.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/public/images/commercial-support-logos/numtide.png b/public/images/commercial-support-logos/numtide.png new file mode 100644 index 0000000000..12d026f050 Binary files /dev/null and b/public/images/commercial-support-logos/numtide.png differ diff --git a/public/images/commercial-support-logos/obsidian-systems.svg b/public/images/commercial-support-logos/obsidian-systems.svg new file mode 100644 index 0000000000..1297390eeb --- /dev/null +++ b/public/images/commercial-support-logos/obsidian-systems.svg @@ -0,0 +1,18 @@ + + + + + + + + + + + + + + + + + + diff --git a/public/images/commercial-support-logos/platonic-systems.svg b/public/images/commercial-support-logos/platonic-systems.svg new file mode 100644 index 0000000000..ed934836cc --- /dev/null +++ b/public/images/commercial-support-logos/platonic-systems.svg @@ -0,0 +1,264 @@ + + + + + + image/svg+xml + + + + + + + + + + + + + + + + + + + + + + diff --git a/public/images/commercial-support-logos/serokell.png b/public/images/commercial-support-logos/serokell.png new file mode 100644 index 0000000000..561688a8c7 Binary files /dev/null and b/public/images/commercial-support-logos/serokell.png differ diff --git a/public/images/commercial-support-logos/tweag.svg b/public/images/commercial-support-logos/tweag.svg new file mode 100644 index 0000000000..31bf286f76 --- /dev/null +++ b/public/images/commercial-support-logos/tweag.svg @@ -0,0 +1,144 @@ + + + +image/svg+xml + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/public/images/external-link.svg b/public/images/external-link.svg new file mode 100644 index 0000000000..9817b31fe7 --- /dev/null +++ b/public/images/external-link.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/public/images/teams/cuda.svg b/public/images/teams/cuda.svg new file mode 100644 index 0000000000..97b9c431be --- /dev/null +++ b/public/images/teams/cuda.svg @@ -0,0 +1,70 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + image/svg+xml + + + + + + + + + + + + + \ No newline at end of file diff --git a/public/images/teams/documentation.svg b/public/images/teams/documentation.svg new file mode 100644 index 0000000000..746ceaff2b --- /dev/null +++ b/public/images/teams/documentation.svg @@ -0,0 +1 @@ +NixOS diff --git a/public/images/teams/foundation-board.svg b/public/images/teams/foundation-board.svg new file mode 100644 index 0000000000..5b6910caec --- /dev/null +++ b/public/images/teams/foundation-board.svg @@ -0,0 +1,3 @@ + + + diff --git a/public/images/teams/infrastructure.svg b/public/images/teams/infrastructure.svg new file mode 100644 index 0000000000..4223a5fbe4 --- /dev/null +++ b/public/images/teams/infrastructure.svg @@ -0,0 +1,99 @@ + + + + + + + image/svg+xml + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/public/images/teams/marketing.svg b/public/images/teams/marketing.svg new file mode 100644 index 0000000000..66440f03f3 --- /dev/null +++ b/public/images/teams/marketing.svg @@ -0,0 +1,67 @@ + + + + + + + image/svg+xml + + + + + + + + + + + + + + + + + diff --git a/public/images/teams/moderation.svg b/public/images/teams/moderation.svg new file mode 100644 index 0000000000..0c19bf9de0 --- /dev/null +++ b/public/images/teams/moderation.svg @@ -0,0 +1,51 @@ + + + + + + + image/svg+xml + + + + + + + + + + + + + diff --git a/public/images/teams/nix.svg b/public/images/teams/nix.svg new file mode 100644 index 0000000000..eb5a14abc9 --- /dev/null +++ b/public/images/teams/nix.svg @@ -0,0 +1,3 @@ + + + diff --git a/public/images/teams/nixcon.svg b/public/images/teams/nixcon.svg new file mode 100644 index 0000000000..c4d2c775eb --- /dev/null +++ b/public/images/teams/nixcon.svg @@ -0,0 +1,35 @@ + + + + + + + image/svg+xml + + + + + + + + diff --git a/public/images/teams/nixos-release.svg b/public/images/teams/nixos-release.svg new file mode 100644 index 0000000000..12b33eedb5 --- /dev/null +++ b/public/images/teams/nixos-release.svg @@ -0,0 +1,44 @@ + + + + + + + image/svg+xml + + + + + + + + + + + + diff --git a/public/images/teams/nixpkgs-architecture.svg b/public/images/teams/nixpkgs-architecture.svg new file mode 100644 index 0000000000..746ceaff2b --- /dev/null +++ b/public/images/teams/nixpkgs-architecture.svg @@ -0,0 +1 @@ +NixOS diff --git a/public/images/teams/rfc-steering-committee.svg b/public/images/teams/rfc-steering-committee.svg new file mode 100644 index 0000000000..b5ad165d7b --- /dev/null +++ b/public/images/teams/rfc-steering-committee.svg @@ -0,0 +1,47 @@ + + + + + + + image/svg+xml + + + + + + + + + + + + diff --git a/public/images/teams/security.svg b/public/images/teams/security.svg new file mode 100644 index 0000000000..6649db0d3b --- /dev/null +++ b/public/images/teams/security.svg @@ -0,0 +1,69 @@ + + + + + + + + image/svg+xml + + + + + + + + + + diff --git a/public/images/world-map.svg b/public/images/world-map.svg new file mode 100644 index 0000000000..c47f6bdf41 --- /dev/null +++ b/public/images/world-map.svg @@ -0,0 +1 @@ + diff --git a/src/components/ui/RfcDiagram.astro b/src/components/ui/RfcDiagram.astro new file mode 100644 index 0000000000..47c482819b --- /dev/null +++ b/src/components/ui/RfcDiagram.astro @@ -0,0 +1,67 @@ + + + Final Comment Phase + + + + + New Submission + + + + + + Refine Submission + + + + + + Submission Rejected + + + + + + Submission Accepted + + + + + FCP Cancelled + + + + + Motion for FCP + + Discussion Phase + + + + + + Nomination Phase + + + + + + New Submission + + + + + + + + + + + + + + Substantial New Arguments + + Assignment of Shepherding Team + \ No newline at end of file diff --git a/src/content/community/commercial-support.yaml b/src/content/community/commercial-support.yaml new file mode 100644 index 0000000000..0b6750e8ca --- /dev/null +++ b/src/content/community/commercial-support.yaml @@ -0,0 +1,97 @@ +- href: https://nixcademy.com + name: Nixcademy + logo: /images/commercial-support-logos/nixcademy.svg + locations: + - Remote + - Germany + description: Elevate your organization's expertise with Nix and NixOS through our comprehensive corporate training classes, personalized mentoring, and expert consulting services. Empower your team with the latest knowledge and best practices. +- href: https://arnout.engelen.eu + name: Engelen Open Source + logo: /images/commercial-support-logos/engelen-open-source.png + locations: + - Remote + - Netherlands + description: Arnout 'raboof' Engelen is an independent consultant available for support and small- to medium-sized projects around Nix and Open Source. +- href: https://www.enlambda.com/ + name: Enlambda + logo: /images/commercial-support-logos/enlambda.png + locations: + - Remote + - Estonia + description: Turning operational issues into development tasks using Nix since 2013. +- href: https://determinate.systems/ + name: Determinate Systems + logo: /images/commercial-support-logos/determinate-systems.svg + locations: + - Remote + - Massachusetts, USA + description: Confidently build and deploy to the cloud, stadium, or stock exchange. Expert help with the Nix ecosystem from Graham Christensen and collaborators. +- href: https://immutablesolutions.com/ + name: Immutable Solutions + logo: /images/commercial-support-logos/immutable-solutions.png + locations: + - Sweden + description: Nix specialists helping companies design, develop and deploy systems in a declarative fashion. +- href: https://nix.how + name: Nix.How + logo: /images/commercial-support-logos/nix-how.png + locations: + - Remote + - United Kingdom + description: Nix experts specialising in converting legacy infrastructure to a Nix/NixOS methodology and workflow +- href: https://www.fivebinaries.com/ + name: five binaries + logo: /images/commercial-support-logos/5inaries.png + locations: + - Tallinn, Estonia + - Prague, Czech Republic + description: Five Binaries are an infrastructure development company focused on creating customized highly reliable solutions for blockchain-powered industries. +- href: https://obsidian.systems + name: Obsidian Systems + logo: /images/commercial-support-logos/obsidian-systems.svg + locations: + - New York, USA + description: Software consultancy specializing in Haskell, Nix, curiosity, and innovation. +- href: https://serokell.io/ + name: Serokell + logo: /images/commercial-support-logos/serokell.png + locations: + - Remote + - Tallinn, Estonia + description: Serokell is a custom software engineering company that creates innovative solutions for complex problems. We do software development, consulting, and auditing. +- href: https://helsinki-systems.de + name: Helsinki Systems + logo: /images/commercial-support-logos/helsinki-systems.png + locations: + - Stuttgart, Germany + description: Your partner for hosting, networks and IT solutions running on NixOS. We have multiple years of NixOS and decades of Linux experience to aid your NixOS integration and administration. +- href: https://floxdev.com + name: flox + logo: /images/commercial-support-logos/flox.png + locations: + - Remote + - San Francisco + - London + description: flox is a platform for building, sharing, and collaborating across the entire development lifecycle. +- href: https://www.tweag.io/group/nix/ + name: Tweag + logo: /images/commercial-support-logos/tweag.svg + locations: + - Remote + - Paris, France + - London, UK + - Zurich, Switzerland + description: The Nix Technical Group at Tweag is a team of leading domain experts and top open source contributors. We assist your enterprise with harnessing the full potential of Nix at scale. Check the website for our track record and more details on what we offer. +- href: https://platonic.systems/ + name: Platonic.Systems + logo: /images/commercial-support-logos/platonic-systems.svg + locations: + - Remote + description: Solving your toughest software problems Trying to build an innovative software solution? Is it behind schedule? Over budget? Not working properly? Growing with bugs? We can help. +- href: https://www.numtide.com/ + name: Numtide Ltd + logo: /images/commercial-support-logos/numtide.png + locations: + - Switzerland + - Remote + description: Numtide is a Nix and DevOps consulting company. We help our customers with declarative development, cloud and bare-metal infrastructures. diff --git a/src/content/community/community-platforms.yaml b/src/content/community/community-platforms.yaml new file mode 100644 index 0000000000..f78eff1790 --- /dev/null +++ b/src/content/community/community-platforms.yaml @@ -0,0 +1,25 @@ +main: + - href: https://discourse.nixos.org/ + name: NixOS Forum on Discourse + iconName: simple-icons:discourse + description: The official forum is the right place to get help from other users and discuss the development of the projects. There are also Announcements, Job offers and Events. + - href: https://matrix.to/#/#community:nixos.org + name: NixOS Matrix Space + iconName: simple-icons:matrix + description: Real-time help, development chat, and off-topic community discussion takes place on Matrix. +other: + - href: https://mastodon.social/tags/nixos + name: Mastodon + iconName: simple-icons:mastodon + - href: https://twitter.com/hashtag/NixOS + name: Twitter + iconName: simple-icons:twitter + - href: https://stackoverflow.com/questions/tagged/nix+or+nixpkgs+or+nixos+or+nixops + name: Stackoverflow + iconName: simple-icons:stackoverflow + - href: https://discord.gg/RbvHtGa + name: Discord + iconName: simple-icons:discord + - href: https://www.reddit.com/r/NixOS/ + name: Reddit + iconName: simple-icons:reddit diff --git a/src/content/community/meetups.yaml b/src/content/community/meetups.yaml new file mode 100644 index 0000000000..aa678b783d --- /dev/null +++ b/src/content/community/meetups.yaml @@ -0,0 +1,37 @@ +america: + - href: https://www.meetup.com/New-York-Nix-Users-Group/ + location: New York (New York) + - href: https://www.meetup.com/Nova-Nix-NixOS-NixOps-Meetup/ + location: Reston (Virginia) + - href: http://www.meetup.com/Bay-Area-Nix-NixOS-User-Group/ + location: San Francisco (California) + - href: https://www.meetup.com/Seattle-Nix-NixOS-and-Guix-GuixSD-Users/ + location: Seattle (Washington) +europe: + - href: http://www.meetup.com/Amsterdam-Nix-Meetup/ + location: Amsterdam (Netherlands) + - href: http://www.meetup.com/Berlin-NixOS-Meetup/ + location: Berlin (Germany) + - href: https://www.meetup.com/Greater-Copenhagen-NixOS-User-Group + location: Copenhagen (Denmark) + - href: https://www.meetup.com/Suisse-Romande-NixOS-User-Group/ + location: Lausanne (Switzerland) + - href: https://www.meetup.com/NixOS-London/ + location: London (United Kingdom) + - href: https://mobilizon.fr/@nix-mtp + location: Montpellier (France) + - href: https://matrix.to/#/#nixos-nuernberg:matrix.org + location: Nürnberg (Germany) + - href: http://www.meetup.com/Munich-NixOS-Meetup/ + location: Munich (Germany) + - href: https://www.meetup.com/Oslo-NixOS-User-Group/ + location: Oslo (Norway) + - href: https://blog.shackspace.de/?p=5829 + location: Stuttgart (Germany) + - href: https://www.meetup.com/NixOS-User-Group-Zurich/ + location: Zürich (Switzerland) +asia: + - href: https://www.meetup.com/Singapore-NixOS-Nix-User-Group/ + location: Singapore (Singapore) + - href: http://www.meetup.com/Tokyo-NixOS-Meetup/ + location: Tokyo (Japan) diff --git a/src/content/nixcons/2015.yaml b/src/content/nixcons/2015.yaml new file mode 100644 index 0000000000..7cbd6562e3 --- /dev/null +++ b/src/content/nixcons/2015.yaml @@ -0,0 +1,4 @@ +title: NixCon 2015 - Berlin +date: 14-17 November 2015 +href: https://conf.nixos.org/ +description: Taking place in a Berlin-style converted loft, it was the first NixOS conference. It was the first time Nix community came together in such numbers. In two days there were many interesting talks. diff --git a/src/content/nixcons/2017.yaml b/src/content/nixcons/2017.yaml new file mode 100644 index 0000000000..91f935f1d9 --- /dev/null +++ b/src/content/nixcons/2017.yaml @@ -0,0 +1,4 @@ +title: NixCon 2017 - Munich +date: 28-31 October 2017 +href: http://nixcon2017.org/ +description: After a year of a break, Nix community gathered at TNG Technology Consulting in Munich. diff --git a/src/content/nixcons/2018.yaml b/src/content/nixcons/2018.yaml new file mode 100644 index 0000000000..1859c5b6a9 --- /dev/null +++ b/src/content/nixcons/2018.yaml @@ -0,0 +1,4 @@ +title: NixCon 2018 - London +date: 25-27 October 2018 +href: https://nixcon2018.org/ +description: For the first time a Nix conference outside the Germany. London was the first conference that was not run over the weekend, but during the week. diff --git a/src/content/nixcons/2019.yaml b/src/content/nixcons/2019.yaml new file mode 100644 index 0000000000..af35737a37 --- /dev/null +++ b/src/content/nixcons/2019.yaml @@ -0,0 +1,4 @@ +title: NixCon 2019 - Brno +date: 25-27 October 2019 +href: https://2019.nixcon.org/ +description: NixCon is becoming a regular gathering that everybody expects to happen. This year we met at Brno, Czech Republic. This was the biggest conference so far. diff --git a/src/content/nixcons/2020.yaml b/src/content/nixcons/2020.yaml new file mode 100644 index 0000000000..8e0b93d5e8 --- /dev/null +++ b/src/content/nixcons/2020.yaml @@ -0,0 +1,4 @@ +title: NixCon 2020 - Online +date: 16-18 October 2020 +href: https://2019.nixcon.org/ +description: NixCon is a community-oriented conference for contributors and users of Nix and NixOS. It's about sharing experiences, inspiring people and discussing future development. diff --git a/src/content/nixcons/2022.yaml b/src/content/nixcons/2022.yaml new file mode 100644 index 0000000000..66419195eb --- /dev/null +++ b/src/content/nixcons/2022.yaml @@ -0,0 +1,4 @@ +title: NixCon 2022 - Paris +date: 20-22 October 2022 +href: https://2022.nixcon.org/ +description: NixCon is a community-oriented conference for contributors and users of Nix and NixOS. It's about sharing experiences, inspiring people and discussing future development. diff --git a/src/content/nixcons/2023.yaml b/src/content/nixcons/2023.yaml new file mode 100644 index 0000000000..2fc23c68d9 --- /dev/null +++ b/src/content/nixcons/2023.yaml @@ -0,0 +1,4 @@ +title: NixCon 2023 - Darmstadt +date: 8-10 September 2023 +href: https://2023.nixcon.org/ +description: NixCon is a community-oriented conference for contributors and users of Nix and NixOS. It's about sharing experiences, inspiring people and discussing future development. diff --git a/src/content/teams/cuda.mdx b/src/content/teams/cuda.mdx new file mode 100644 index 0000000000..14f54762f3 --- /dev/null +++ b/src/content/teams/cuda.mdx @@ -0,0 +1,44 @@ +--- +name: CUDA Team +description: Making Nix and NixOS the first choice for users of CUDA-accelerated software. +members: +- name: Samuel A + username: samuela + title: Team creator +- name: Serge K + username: sergek + title: +- name: Connor Baker + username: connorbaker + title: Sponsored by Tweag +contact: +- name: Discourse + href: https://discourse.nixos.org/t/announcing-the-nixos-cuda-maintainers-team-and-a-call-for-maintainers/18074 +- name: Matrix + href: https://app.element.io/#/room/#cuda:nixos.org +- name: GitHub project board + href: https://github.com/orgs/NixOS/projects/27 +--- +# Motivation + +GPU-acceleration has become a fundamental prerequisite to machine learning work and scientific computing. Without support for GPU-acceleration, the Nixpkgs ecosystem will remain largely invisible to practitioners. + +Nixpkgs and NixOS give us the tools we need to build reproducible and robust packages and environments. However, the state of scientific computing in Nixpkgs does not reflect this. + +# Goals and Responsibilities + +The singular focus of the CUDA-maintainers team is to make Nixpkgs the best repository of packages leveraging CUDA, especially in machine learning and scientific computing. Towards that end, we seek to: + +- improve the quantity and quality of CUDA-enabled package in Nixpkgs +- document CUDA packaging best practices, guidelines, and patterns +- support community efforts involving packaging or distributing CUDA-enabled software + +# Call for Sponsors + +The CUDA-maintainers team is seeking sponsors to help fund or supply technical infrastructure related to our mission. Therefore, if you or your organization: + +- are impacted by these issues, +- have related issues with Nixpkgs CUDA support, +- would like to prioritize or accelerate certain work, + +please consider supporting this effort directly or through the NixOS Foundation. Reach out via GitHub [@connorbaker](https://github.com/connorbaker), or email connor.baker@tweag.io to get involved. diff --git a/src/content/teams/documentation.mdx b/src/content/teams/documentation.mdx new file mode 100644 index 0000000000..6522f77ed4 --- /dev/null +++ b/src/content/teams/documentation.mdx @@ -0,0 +1,55 @@ +--- +name: Documentation Team +description: Works on improving learning experience and documentation. +members: +- name: Valentin Gagarin + username: fricklerhandwerk + title: Sponsored by Antithesis via Tweag +- name: Silvan Mosberger + username: infinisil + title: Sponsored by Tweag +- name: Olaf + username: olaf + title: +- name: henrik-ch + username: henrik-ch + title: +- name: zmitchell + username: zmitchell + title: +- name: asymmetric + username: asymmetric + title: +- name: wamirez + username: wamirez + title: +- name: yukiisbored + username: yukiisbored + title: +- name: proofconstruction + username: proofconstruction + title: +- name: Robert Hensing + username: roberth + title: +- name: alejandrosame + username: alejandrosame + title: +contact: +- name: Discourse + href: https://discourse.nixos.org/c/dev/documentation/25 +- name: Matrix + href: https://app.element.io/#/room/#docs:nixos.org +- name: GitHub project board + href: https://github.com/orgs/NixOS/projects/15 +--- +# Goals + +- Flatten the infamous learning curve +- Ease Nix learning, increase onboarding success, and user retention +- Improve organization of Nix knowledge +- Lead, guide, and support community efforts + +# Contact and Information + +Information about team procedures can be found in the [Team handbook](https://github.com/NixOS/nix.dev/tree/master/maintainers). Discussions are held on Matrix, Discourse, and on GitHub issues and pull requests. diff --git a/src/content/teams/foundation-board.mdx b/src/content/teams/foundation-board.mdx new file mode 100644 index 0000000000..779f1104f6 --- /dev/null +++ b/src/content/teams/foundation-board.mdx @@ -0,0 +1,45 @@ +--- +name: Foundation board +description: Responsible for providing operational and organizational support to the NixOS project and community. +members: +- name: Eelco Dolstra + username: edolstra + title: Chair +- name: Ron Efroni + username: ron + title: Treasurer +- name: Théophane Hufschmitt + username: regnat + title: Secretary +- name: Domen Kozar + username: domenkozar + title: +- name: Jonas Chevalier + username: zimbatm + title: +contact: +- name: Discourse + href: https://discourse.nixos.org/c/dev/nixos-foundation/47 +- name: Matrix + href: https://app.element.io/#/room/#foundation:nixos.org +- name: GitHub project board + href: https://github.com/orgs/NixOS/projects/28 +--- +# Responsibility + +The role of the board is to provide operational and organizational support to the NixOS project and community. In particular, its responsibilities are to: + +- Handle the administrative, legal and financial tasks of the Foundation +- Serve as an interface between the community and the corporate/governmental world + - Handle sponsoring and donations + - Build and maintain beneficial and collaborative relationships +- Provide a framework for teams to self-organize + - Hand out the credentials and permissions as needed by the teams' work +- Fund community events and efforts +- Unblock things that would be stuck otherwise + - Arbiter in case of conflicts + - Serve as a backup for critical tasks when needed + +The board is not responsible for technical leadership, decisions, or direction. + +# Contact \ No newline at end of file diff --git a/src/content/teams/infrastructure.mdx b/src/content/teams/infrastructure.mdx new file mode 100644 index 0000000000..134d0c5a98 --- /dev/null +++ b/src/content/teams/infrastructure.mdx @@ -0,0 +1,30 @@ +--- +name: Infrastructure Team +description: Provides infrastructure for the Nix and NixOS community. +members: +- name: Amine Chikhaoui + username: aminechikhaoui + title: +- name: Eelco Dolstra + username: edolstra + title: +- name: Graham Christensen + username: grahamc + title: +- name: Jonas Chevalier + username: zimbatm + title: +- name: Vladimír Čunát + username: vcunat + title: +contact: +- name: Discourse + href: https://discourse.nixos.org/c/dev/infrastructure-team/31 +--- +# Responsibility + +The responsibility of the team is to provide infrastructure for the Nix and NixOS community. + +# Reporting issues + +If you experience any issues with the infrastructure, please [post a issue to this repository](https://github.com/NixOS/nixos-org-configurations/issues/new). diff --git a/src/content/teams/marketing.mdx b/src/content/teams/marketing.mdx new file mode 100644 index 0000000000..9406a5c8e9 --- /dev/null +++ b/src/content/teams/marketing.mdx @@ -0,0 +1,150 @@ +--- +name: Marketing Team +description: Maintains this website, responsible for social media outreach, collects metrics. It's mission is to help grow the Nix user base. +members: +- name: Rok Garbas + username: garbas + title: Leader +- name: Thomas Bereknyei + username: tomberek + title: +- name: Bryan Honof + username: bjth + title: +- name: Ida Bzo + username: idabzo + title: +- name: Ilan Joselevich + username: Kranzes + title: +- name: Guillaume Desforges + username: arsleust + title: +- name: Dan Baker + username: djacu + title: +contact: +- name: Discourse + href: https://discourse.nixos.org/c/dev/marketing-team/28 +- name: Matrix + href: https://matrix.to/#/#marketing:nixos.org +- name: Email + href: mailto:webmaster@nixos.org +--- +# Why we want growth + +Growth is instrumental to something. What is that? + +We strive to advance the state of the art in software engineering. That's why we're using and contributing to Nix. + +Ultimately, we're interested in using and making software that is: + +- more up-to-date +- more reliable +- easier to distribute +- easier to integrate +- easier to collaborate on. + +We cannot achieve this alone. As the Nix marketing team, we believe that talking about work done is as important as doing the work. This is where we can help the Nix ecosystem to thrive. + +We're convinced that the more people *know about* Nix, the more people will *use* Nix, and the more people will become *contributors and maintainers*. We want to serve those people who are indispensable for maintaining and developing the Nix ecosystem, by promoting their work and facilitating communication with a wider audience. + +# How we want to grow + +Our strategy is for the Nix ecosystem to become known for something unique we already excel at. This is what we will emphasize in order to attract users. + +This is not to set directions for development, but simply recognizing and leveraging current strengths. + +## Target audience + +Our target audience are software developers. + +Nix tooling already fits developer use cases most closely, and it is developers who will derive the most value from using Nix in its current state. Developers are also more likely to become contributors, and eventually maintainers. Finally, among our users, software professionals have the greatest influence on organizations that can provide the resources necessary to keep developing and maintaining the Nix ecosystem. + +## Communication strategy + +Nix can do many things. If we start to talk about all of those things at once, the message gets lost. + +For example: There is only a limited amount of space on the landing page. We will choose a narrow set of topics that best serve our purpose of increasing adoption most effectively. The particular focus may change over time as we move through the [adoption life cycle](https://en.wikipedia.org/wiki/Technology_adoption_life_cycle) for our target audience. + +# How to measure growth + +In order to know where we're going, we need to know where we are. + +Therefore, we will first collect metrics relevant to our mission, separated into phases in the user journey: + +## Discovery phase + +- Google Search trends +- Social media impressions +- Visits to the landing page + +## User phase + +- Number of members and messages on the community platforms (Discourse, Matrix, GitHub) +- Binary cache usage +- Number of queries on search.nixos.org +- Website statistics on documentation +- Community surveys + +## Contribution phase + +- Number of contributors and forks +- Number of opened issues and pull requests + +# 3-months plan (June through August 2023) + +The current team consists of 5 people with regular availability of ca. 2 hours per week for working on marketing topics. We estimate the required work to fulfill the following goals to ca. 115 hours over three months, given a total team capacity of ca. 120 hours in the same period. + +## Media outreach + +- More posts on social media + - Currently involved: @idabzo @pxc @btjh @garbas @raboof + - Estimated effort: 2h/week (24h total) +- Revive the newsletter + - One post per month + - Currently involved: @idabzo @garbas + - Estimated effort: 2h/month (5h total) +- Continue "What's new in Nix?" + - Goal: Release one video + - Currently involved: @btjh @garbas @djacu @tomberek + - Estimated effort: 20h +- (optional) Write a content policy + - What to include, what not to + - Which language to use + - Define audience personae + - Estimated effort: 10 + +## Community Survey 2023 + +- Goal: publish in June +- Currently involved: @garbas @kranzes @Arsleust +- Estimated effort: 55h + +# 1-year plan + +- Set up continuous collection and presentation of metrics +- Develop communication strategy and adoption plan for the Nix platform +- Establish a communication workflow to support community teams with outreach +- Support appearances in podcasts, interviews, conferences, ... +- Publish 12 newsletters +- Publish 4 video updates + +# Get in touch + +We are looking for additional members. We are especially interested in people interested in frontend development, content creation for social media, and technical writing. + +We would like to see the team being assembled from every corner of a Nix community. To join the team please write an email to [webmaster@nixos.org](mailto:webmaster@nixos.org) trying to answer the following questions: + +- Why would you like to join the team? +- Why are you interested in marketing Nix? +- What drives you? +- How would you contribute to the marketing team? +- What is your idea of what the marketing team will work on, this year? Next year? Next 5 years? +- What could be a few easy fixes to the website that would solve problems that you heard others complain about Nix/NixOS? + +The answers are actually not used to judge people if they are good enough to join, but to understand the person joining, their intent and their vision. Since we will discuss many things that could be very bikeshedding, it is important that we understand each other’s position and the context they are arguing from. + +# Meetings + +You can expect at meetings to discuss things first in an abstract manner (what are our goals) and only then get into more concrete proposals (how do we achieve goals). Meetings will be scheduled as needed and as much as the team has time, but at least once a month. Initially, it might happen that we will meet more often until the whole idea of what a marketing team is/does is bootstrapped. Minutes of the meetings will be published with the potential agenda and the date of the next meeting. diff --git a/src/content/teams/moderation.mdx b/src/content/teams/moderation.mdx new file mode 100644 index 0000000000..f690163986 --- /dev/null +++ b/src/content/teams/moderation.mdx @@ -0,0 +1,35 @@ +--- +name: Moderation Team +description: Moderates participation on official community platforms. +members: +- name: Alyssa Ross + username: qyliss + title: +- name: Graham Christensen + username: grahamc + title: +- name: Jörg Thalheim + username: mic92 + title: +- name: Martin Weinelt + username: hexa + title: +- name: Rok Garbas + username: garbas + title: +- name: Ryan Mulligan + username: ryantm + title: +contact: +- name: Email (for reporting) + href: mailto:community@nixos.org +- name: Discourse + href: https://discourse.nixos.org/c/meta/moderation-team/40 +--- +# Responsibility + +This team is responsible for moderating participation on [official community platforms](/community/#platforms) in accord with [RFC 102](https://github.com/NixOS/rfcs/blob/master/rfcs/0102-moderation-team.md). + +# Reporting issues + +Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [community@nixos.org](mailto:community@nixos.org). The project team is obligated to maintain confidentiality with regard to the reporter of an incident. diff --git a/src/content/teams/nix.mdx b/src/content/teams/nix.mdx new file mode 100644 index 0000000000..33982e2b28 --- /dev/null +++ b/src/content/teams/nix.mdx @@ -0,0 +1,54 @@ +--- +name: Nix Team +description: Maintains and releases the Nix package manager. +members: +- name: Eelco Dolstra + username: edolstra + title: Leader +- name: Théophane Hufschmitt + username: regnat + title: +- name: Valentin Gagarin + username: fricklerhandwerk + title: +- name: Thomas Bereknyei + username: tomberek + title: +- name: Robert Hensing + username: roberth + title: +- name: John Ericson + username: Ericson2314 + title: +contact: +- name: Discourse + href: https://discourse.nixos.org/c/dev/nix/50 +- name: Matrix + href: https://matrix.to/#/#nix-dev:nixos.org +- name: GitHub project board + href: https://github.com/orgs/NixOS/projects/19 +--- +# Responsibilities + +The Nix team is responsible for maintaining and releasing the Nix package manager. + +The Nix team has ownership of the Nix source code. It is accountable for and has the authority to make changes to Nix happen. + +This includes, but isn’t limited to: + +- Establish, communicate, and maintain a technical roadmap +- Enable contributors +- Ensure capacity for reviewing PRs and addressing issues +- Define and assert quality criteria for contributions +- Keep code healthy, documentation up to date +- Manage the release lifecycle +- Regularly publish reports on work done +- Engage with third parties in the interest of the project + +# Meetings + +The Nix team has a weekly meeting to triage and discuss issues and PRs, and a weekly working session to review PRs and hack on code. + +# Team handbook + +The Nix team handbook is available [here](https://github.com/NixOS/nix/tree/master/maintainers) \ No newline at end of file diff --git a/src/content/teams/nixcon.mdx b/src/content/teams/nixcon.mdx new file mode 100644 index 0000000000..dd37337a8e --- /dev/null +++ b/src/content/teams/nixcon.mdx @@ -0,0 +1,26 @@ +--- +name: NixCon Team +description: Helps organize NixCon, a conference for the Nix and NixOS community. +members: +- name: Ryan Lahfa + username: RaitoBezarius + title: +- name: Hexchen + username: hexchen + title: +- name: Janik Haag + username: Janik + title: +- name: "0x4A6F" + username: "0x4A6F" + title: +- name: Ron Efroni + username: ron + title: Observer +contact: +- name: Discourse + href: https://discourse.nixos.org/c/events/nixcon/18 +--- +# Responsibilities + +Organizing NixCons diff --git a/src/content/teams/nixos-release.mdx b/src/content/teams/nixos-release.mdx new file mode 100644 index 0000000000..6242506aee --- /dev/null +++ b/src/content/teams/nixos-release.mdx @@ -0,0 +1,30 @@ +--- +name: NixOS Release Team +description: Manages the twice-yearly releases of NixOS. It is responsible the entire release process from setting the roadmap to uploading the artifacts. +members: +- name: Figsoda + username: figsoda + title: +- name: Ryan Lahfa + username: RaitoBezarius + title: +contact: +- name: Discourse + href: https://discourse.nixos.org/c/dev/nixos-release-team/32 +--- + +# Responsibilities + +- Manage the release process +- Start discussions about features and changes for a given release +- Create a roadmap +- Release in cooperation with Eelco Dolstra +- Decide which bug fixes, features, etc... get back ported after a release + +# Release process + +For each release there are two release managers. After each release the release manager having managed two releases steps down and the release management team of the last release appoints a new release manager. + +This makes sure a release management team always consists of one release manager who already has managed one release and one release manager being introduced to their role, making it easier to pass on knowledge and experience. + +More information can be found in [the NixOS Release Wiki](https://nixos.github.io/release-wiki/Home.html). diff --git a/src/content/teams/nixpkgs-architecture.mdx b/src/content/teams/nixpkgs-architecture.mdx new file mode 100644 index 0000000000..a022b95448 --- /dev/null +++ b/src/content/teams/nixpkgs-architecture.mdx @@ -0,0 +1,58 @@ +--- +name: Nixpkgs Architecture Team +description: Solves architectural Nixpkgs issues that are too big in scope for any single person to undertake. +members: +- name: Silvan Mosberger + username: infinisil + title: Leader +- name: Thomas Bereknyei + username: tomberek + title: From Flox +- name: Robert Hensing + username: robertha + title: From Hercules CI +- name: John Ericson + username: Ericson2314a + title: From Obsidian Systems +- name: Alex Ameen + username: + title: From Tulip Interfaces +- name: Paul Haerle + username: + title: +- name: David Hauer + username: + title: +contact: +- name: Discourse + href: https://discourse.nixos.org/c/dev/nixpkgs/44 +- name: Matrix + href: https://matrix.to/#/#nixpkgs-architecture:nixos.org +- name: GitHub organization + href: https://github.com/nixpkgs-architecture +- name: GitHub issues + href: https://github.com/nixpkgs-architecture/issues/issues +- name: YouTube + href: https://www.youtube.com/@nixpkgs-architecture +--- +# Motivation + +Nixpkgs is arguably the most valuable resource for Nix users. Its collection of packages is used by virtually every Nix user, private or commercially. However, there's continuous complaints by virtually every user of nixpkgs about various aspects, like missing documentation, difficulty of contributing, inconsistent interfaces and missing features. These problems need to be fixed eventually; doing nothing is not an option if Nix should be taken seriously as a universal solution for packaging. + +The scale of nixpkgs has grown so considerably in recent years that it's not possible anymore for any single person to fix larger problems. And even if someone does manage to find _a_ solution to a problem, there's nobody who can officially _accept_ that solution and actually merge it. Over the years, a number of improvements have been suggested and implemented, but most of them never made it to the finish line. + +By creating a team tasked with the job of finding solutions to these issues, it becomes much more feasible to actually do it. + +# Goals + +The primary goal of this team is to make interactions with nixpkgs a joy, so that it's easy and intuitive to use, learn, and contribute to. The way in which this should be achieved is to fix problems in a clean, consistent, and future-proof way. It should be ensured that nixpkgs is a solid and trustworthy foundation for the Nix community that can be relied upon. + +The process in which this should be achieved is to gather and analyze critical feedback from users to find the root causes of problems. We will come up with solutions to these problems and evaluate them. Eventually, we'll reach consensus and decide on a solution and turn it into reality. This is explained in more detail in the [process](https://github.com/nixpkgs-architecture/#process) section over on GitHub. + +Since nixpkgs is widely used by third-party code, this team needs to be very careful to ensure reasonable backwards-compatibility. Backwards incompatible changes are only in scope after a deprecation window of an appropriate duration and accompanying warning. + +Check out [this GitHub board](https://github.com/orgs/nixpkgs-architecture/projects/2/views/2) for an up-to-date list of issues that are being considered. If you have an idea for an issue that should be considered, please [open a new issue](https://github.com/nixpkgs-architecture/issues/issues/new?assignees=&labels=&template=issue.md&title=) and it will be automatically added to the board. + +# Administration and Communication + +Information about how to join or leave the team and the meetings can be found on the [team page on GitHub](https://github.com/nixpkgs-architecture). Discussions are held on Matrix, Discourse, and GitHub issues (link in *Contact* section). \ No newline at end of file diff --git a/src/content/teams/rfc-steering-committee.mdx b/src/content/teams/rfc-steering-committee.mdx new file mode 100644 index 0000000000..931e91e74f --- /dev/null +++ b/src/content/teams/rfc-steering-committee.mdx @@ -0,0 +1,43 @@ +--- +name: RFC Steering Committee +description: Responsible for forming an RFC Shepherd team from the available nominations on each RFC, which is then responsible for accepting or rejecting a specific RFC. +members: +- name: Tom Bereknyei + username: tomberek + title: +- name: Kevin Cox + username: kevincox + title: +- name: Eelco Dolstra + username: edolstra + title: +- name: Linus Heckemann + username: lheckemann + title: +- name: Silvan Mosberger + username: infinisil + title: +contact: +- name: No contact provided +--- +# Responsibility + +This committee is responsible for forming an RFC Shepherd team from the available nominations on each RFC. This team also names the leader of the Shepherd team. + +They have no special responsibility with regard to the content of an RFC; they can weigh in on them, the same as any other community member, but are only in charge of: + +- Selecting the Shepherds unanimously +- Supervising that the Shepherds are carrying out their work +- Committing the final RFC + +# Shepherd Team + +A team of 3-4 community members defined unanimously by the RFC Steering Committee, responsible for accepting or rejecting a specific RFC. This team is created per RFC from community members nominated in the discussion on that RFC. + +This team should be people who are very familiar with the main components touched by the RFC. The author cannot be part of the Shepherd Team. In addition, at most half of the Shepherd Team can be part of the RFC Steering Committee. + +The responsibility of the team is to guide the discussion as long as it is constructive, new points are brought up, and the RFC is iterated on. From time to time, they should summarize the current state of discussion. If this is no longer the case, then the Shepherd Team shall step in with a motion for FCP. + +# Shepherd Leader + +The person in charge of the RFC process for a specific RFC, responsible for ensuring the process is followed in a timely fashion. The Shepherd Leader has no special responsibility with regard to moving an undecided Shepherd Team to a certain decision. diff --git a/src/content/teams/security.mdx b/src/content/teams/security.mdx new file mode 100644 index 0000000000..aba7b19170 --- /dev/null +++ b/src/content/teams/security.mdx @@ -0,0 +1,38 @@ +--- +name: Security Team +description: Security is a priority for the NixOS community. In addition to community-sourced developments, NixOS has a dedicated team, to look into privately reported security issues. +members: +- name: Martin Weinelt + username: hexa + title: +- name: Linus Heckemann + username: lheckemann + title: +- name: Robert Scott + username: ris + title: +contact: +- name: Matrix + href: https://matrix.to/#/#security:nixos.org +- name: Discourse + href: https://discourse.nixos.org/c/dev/security +--- +# Sources of Security Information + +Security is a priority for the NixOS community. A variety of channels are used to coordinate development in this vein. Three of the main modes of communication about NixOS security are: + +- The issues tagged "Security" on [NixOS/nixpkgs](https://github.com/NixOS/nixpkgs/issues?q=is%3Aopen+is%3Aissue+label%3A%221.severity%3A+security%22) +- The [Matrix room](https://matrix.to/#/#security:nixos.org) +- The NixOS security [Discourse](https://discourse.nixos.org/c/dev/security) + +In addition to community-sourced developments, NixOS has a dedicated security team. If the above sources are not enough to answer your question, please reach out to the team. + +# Security Disclosures + +To privately report a security issue with NixOS, Nix, and its ecosystem, please email a member of the NixOS Security Team and we will ensure the issue is handled. + +- Martin Weinelt: **hexa@darmstadt.ccc.de**, GPG Fingerprint: `F7D6 7CFB F2CA 32F1 641A 03DB 0D9F 7008 4786 0BC5` + +- Linus Heckemann: **linus@sphalerite.org**, GPG Fingerprint: `58FB 812B 0FCF 7B87 343C 35D4 9EF3 625A C8C1 9C9C` + +- Robert Scott: **secure@humanleg.org.uk**, GPG Fingerprint: `8868 8AE4 8AE6 3195 BCF5 F732 3A7B 7B7A 2611 CE25` diff --git a/src/layouts/Footer.astro b/src/layouts/Footer.astro index 44914e9778..ac81b58894 100644 --- a/src/layouts/Footer.astro +++ b/src/layouts/Footer.astro @@ -8,7 +8,7 @@ const footerMenu = await getEntry('menus', 'footer'); ---