f13283c3f5
This change was preceded by the idea of adding a pronoun field to the file, which we determined to be a bad idea: * maintainers-list: add pronoun to the optional fields I often do not know how to address maintainers, so giving them the ability to specify their pronouns is helpful for communication purposes. * maintainers-list: add pronoun for Profpatsch maintainers-list: make the pronoun field into a list Some people have a set of pronouns they are fine with, so let’s make that possible. Based on feedback by somebody With An Idea™ of the topic. * maintainers-list: remove the pronouns field The discussion around the field raised a good point, quoting: > What you are proposing here is keeping an irrevocable permanent > history of people’s pronouns. It makes anybody would want to do bad > things with it one small script away from a list of which Nixpkgs > contributors are trans. Even looking at the history of name > changes (which we probably also shouldn’t store) wouldn’t be nearly > as reliable a source. While it might be tempting to say that > participating in this would be optional, it would be establishing a > de facto standard location for this information, that might make > people feel compelled to participate or accept having the wrong > pronoun used. Compounding this is the fact that the people who will > be most comfortable using this field are the people who have never > changed their pronouns. If they decide to in future, they now have > to choose between permanently marking themselves as somebody who > changed or deleted their pronouns (which is dangerous) or leaving > the wrong pronouns up. Because of this, I think that over time this > list would probably result in even more people being referred to by > the wrong pronouns, because of outdated entries that are dangerous > to correct. > > **This idea is extremely dangerous**. If somebody wants to publish > their pronouns, they can already do that on their website or GitHub > profile, without having to include that information in a large > public dataset with history tracking. So let’s remove it again. |
||
|---|---|---|
| .github | ||
| doc | ||
| lib | ||
| maintainers | ||
| nixos | ||
| pkgs | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .version | ||
| COPYING | ||
| default.nix | ||
| flake.nix | ||
| README.md | ||
Nixpkgs is a collection of over 40,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
- IRC - #nixos on freenode.net
- NixOS Weekly
- Community-maintained wiki
- Community-maintained list of ways to get in touch (Discord, Matrix, Telegram, other IRC channels, 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 20.03 release
- Tests for unstable/master
- Tests for the NixOS 20.03 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 over 40,000 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. When pull requests are made, our tooling automation bot, OfBorg will perform various checks to help ensure expression quality.
The Nixpkgs maintainers are people who have assigned themselves to maintain specific individual packages. We encourage people who care about a package to assign themselves as a maintainer. When a pull request is made against a package, OfBorg will notify the appropriate maintainer(s). The Nixpkgs committers are people who have been given permission to merge.
Most contributions are based on and merged into these branches:
masteris the main branch where all small contributions gostagingis branched from master, changes that have a big impact on Hydra builds go to this branchstaging-nextis branched from staging and only fixes to stabilize and security fixes with a big impact on Hydra builds should be contributed to this branch. This branch is merged into master when deemed of sufficiently high quality
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 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.