5dfdb09561
While preparing this change, I read the git blame on all of the files I touched. I saw a working lifetime of building this system which we use every day and love dearly and keep maintained ourselves. I saw commits from a 14 year range between 2003 to 2017!! I could not be more thankful for Eelco's work on building large parts of the foundation of nixpkgs that all of us rely on now. However, the end date of that range of the files I looked at the blame on was 2017. I did not see surviving code from any newer date than that. Looking at the Git logs, Eelco has been working on other things, and that's totally fine. However, it means that our maintenance metadata is out of date on a lot of packages, and *that*'s the reason I am submitting this change. There are a lot of packages that don't have anyone with their name on them to be pinged if they need attention, even if they have had recent activity (although it is never clear if recent activity was just someone fixing it because ZHF or because the package actually matters to them). There are a lot of packages with storied history that maybe don't need to be in the set anymore at all since they have not been touched in years; or maybe they are simply finished. Empty maintainer lists should be a sign that we need to figure out who maintains it or potentially remove it if it has rotted, and allowing the maintainer list to be empty if it is already not maintained is part of a healthy repository ecology. Either way, I would like to have the maintenance metadata not mislead anyone into sending Eelco emails about packages he doesn't, in practice, work on anymore. I have not removed his name from everything; there are some things that he is the upstream for or has worked on more recently, for instance, like Nix, which I have left alone. |
||
|---|---|---|
| .github | ||
| ci | ||
| doc | ||
| lib | ||
| maintainers | ||
| nixos | ||
| pkgs | ||
| .editorconfig | ||
| .git-blame-ignore-revs | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .version | ||
| CONTRIBUTING.md | ||
| COPYING | ||
| default.nix | ||
| flake.nix | ||
| README.md | ||
| shell.nix | ||
Nixpkgs is a collection of over 100,000 software packages that can be installed with the Nix package manager. It also implements NixOS, a purely-functional Linux distribution.
Manuals
- NixOS Manual - how to install, configure, and maintain a purely-functional Linux distribution
- Nixpkgs Manual - contributing to Nixpkgs and using programming-language-specific Nix expressions
- Nix Package Manager Manual - how to write Nix expressions (programs), and how to use Nix command line tools
Community
- Discourse Forum
- Matrix Chat
- NixOS Weekly
- Official wiki
- Community-maintained list of ways to get in touch (Discord, Telegram, IRC, etc.)
Other Project Repositories
The sources of all official Nix-related projects are in the NixOS organization on GitHub. Here are some of the main ones:
- Nix - the purely functional package manager
- NixOps - the tool to remotely deploy NixOS machines
- nixos-hardware - NixOS profiles to optimize settings for different hardware
- Nix RFCs - the formal process for making substantial changes to the community
- NixOS homepage - the NixOS.org website
- hydra - our continuous integration system
- NixOS Artwork - NixOS artwork
Continuous Integration and Distribution
Nixpkgs and NixOS are built and tested by our continuous integration system, Hydra.
- Continuous package builds for unstable/master
- Continuous package builds for the NixOS 24.05 release
- Tests for unstable/master
- Tests for the NixOS 24.05 release
Artifacts successfully built with Hydra are published to cache at https://cache.nixos.org/. When successful build and test criteria are met, the Nixpkgs expressions are distributed via Nix channels.
Contributing
Nixpkgs is among the most active projects on GitHub. While thousands of open issues and pull requests might seem a lot at first, it helps consider it in the context of the scope of the project. Nixpkgs describes how to build tens of thousands of pieces of software and implements a Linux distribution. The GitHub Insights page gives a sense of the project activity.
Community contributions are always welcome through GitHub Issues and Pull Requests.
For more information about contributing to the project, please visit the contributing page.
Donations
The infrastructure for NixOS and related projects is maintained by a nonprofit organization, the NixOS Foundation. To ensure the continuity and expansion of the NixOS infrastructure, we are looking for donations to our organization.
You can donate to the NixOS foundation through SEPA bank transfers or by using Open Collective:
License
Nixpkgs is licensed under the MIT License.
Note: MIT license does not apply to the packages built by Nixpkgs, merely to the files in this repository (the Nix expressions, build scripts, NixOS modules, etc.). It also might not apply to patches included in Nixpkgs, which may be derivative works of the packages to which they apply. The aforementioned artifacts are all covered by the licenses of the respective packages.