From 8346ccdc7f62e45f2cd53fc9fe1cfb62483291e2 Mon Sep 17 00:00:00 2001 From: fricklerhandwerk Date: Thu, 2 Nov 2023 20:39:28 +0100 Subject: [PATCH] remove the vision outline we're already close enough to the original idea that there is no need to keep it here. --- CONTRIBUTING.md | 175 +----------------------------------------------- 1 file changed, 2 insertions(+), 173 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index d92551e5b..5c5fc4d2f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -2,25 +2,12 @@ nix.dev is a community effort to collect, create, and maintain world-class learning resources for Nix. -It is supposed to fit between first impressions on the [Nix web site](https://nixos.org) and the reference manuals for [Nix][nix manual] ([source][nix manual src]), [Nixpkgs][nixpkgs manual] ([source][nixpkgs manual src]), and [NixOS][nixos manual] ([source][nixos manual src]). -See the [vision](#vision) and [textual outline](#outline) for an idea of a desired end state. - -[nix manual]: https://nixos.org/manual/nix -[nix manual src]: https://github.com/NixOS/nix/tree/master/doc/manual -[nixpkgs manual]: https://nixos.org/manual/nixpkgs -[nixpkgs manual src]: https://github.com/NixOS/nixpkgs/tree/master/doc -[nixos manual]: https://nixos.org/manual/nixos -[nixos manual src]: https://github.com/NixOS/nixpkgs/tree/master/nixos/doc/manual - We strongly encourage everyone interested to contribute by asking informed questions or directly proposing changes. -Make a [pull request] if you want to introduce an incremental change. +Make a [pull request](https://github.com/NixOS/nix.dev/pulls) if you want to introduce an incremental change. Note our [considerations on licensing and attribution](#licensing-and-attribution). -Open an [issue] if you want to clarify something not evident from what is provided in this repository, or if you want to discuss a significant change before starting to work on it. - -[issue]: https://github.com/NixOS/nix.dev/issues -[pull request]: https://github.com/NixOS/nix.dev/pulls +Open an [issue](https://github.com/NixOS/nix.dev/issues) if you want to clarify something not evident from what is provided in this repository, or if you want to discuss a significant change before starting to work on it. ## Code of conduct @@ -80,164 +67,6 @@ We would be glad to incorporate your insights. Please read [Contributing Documentation](https://nix.dev/contributing/documentation). -# Vision - -This is our vision for the journey into Nix, Nixpkgs, and NixOS. -We want to create and collect learning resources for mastering the ecosystem step by step. - -Use it as a scaffold to to find a place for your ideas on new tutorials and guides. -It is still subject to change and refinement as we find out more about learners' needs, but already proved helpful for orienting beginners. - -```mermaid -flowchart TB - subgraph install[install Nix] - direction TB - Linux - macOS - Windows - Docker - end - subgraph first-steps[run any program] - run[ad hoc environments] - findpkgs[find packages] - scripts[reproducible scripts] - gc[garbage collection] - end - subgraph imperative[imperative package management] - install-imperative[install packages] - upgrade[upgrade packages] - rollback[rollback packages] - pinning[pin package version] - end - subgraph lang[Nix language] - basics - debugging - best-practices[best practices] - tooling - end - subgraph declarative[declarative environments] - shell[declarative shells] - pin[pinning dependencies] - adapt[package variants and patches] - end - subgraph configuration[declarative configuration management] - user[declarative user environments] - nixos[declarative operating systems] - nixos-contrib[contributing to NixOS] - end - subgraph pkgs[declarative package management] - trivial[creating simple packages] - ecosystems[language ecosystems] - nixpkgs[contributing to Nixpkgs] - end - subgraph dev[software development lifecycle] - tests - caching[build caching] - deployment - ci[continuous integration] - distributed[distributed builds] - cross-compilation - bundling[bundling build results] - nixos-tests[testing distributed systems with NixOS] - nix[contributing to Nix] - end - install --> first-steps - first-steps --> lang & imperative - lang --> declarative - declarative --> configuration & pkgs - configuration --> dev - pkgs --> dev -``` - -# Outline - -See [Vision](#vision) for a graphical outline that illustrates the intended learning journey. - -## Install Nix - -Instructions for the various installation methods. - -## Build and run software - -Here we show how existing build plans are used to produce working software. - -- Find packaged software -- Run software from existing packages -- Set up a temporary environment - -The next chapter chapter is about how to hold onto the ephemeral examples from the previous chapter, and how to create more complex environments by composing existing packages. - -## Imperative package management - -Describes a straightforward transition from temporary environments using existing packages. - -- Persist packages in the file system -- Updates, rollbacks, pinning -- Garbage collection - -Imperative package management's unique feature is that it allows updating each package independently to the most recent available version without touching the rest of the system. - -## Nix language - -Leveraging the full power of Nix requires understanding the Nix language, and eventually learning to write Nix expressions. - -- Syntax and semantics - - Attribute sets - - Functions -- Debugging -- Best practices -- Tooling - - Syntax highlighting - - Linters - - Formatters - -## Declarative environments - -While imperative package management supports "generations", it does not have proper change management, "profiles" are not portable, and it is not immediately obvious how to compose packages into a larger unit. -This section shows how to have all of that by declaring a Nix expression in a file that can be used on any system that supports Nix. - -- Declare a reproducible environment -- Pinning dependencies -- Adapt packages to your needs - -## Declarative package management - -Here we show how existing packages come into being, and how to modify and create packages. - -- Modifying existing packages -- Creating new packages -- Language ecosystems -- Contribute to Nixpkgs - -Creating packages and contributing are advanced topics that require much more detail (especially langauge specifics), and are partially covered in the Nixpkgs manual already. -In this context they are intended to demonstrate Nixpkgs architecture and design, to enable readers to navigate existing code, assess pull requests, and create or maintain their own packages. -This should be fairly superficial, otherwise it would duplicate much of the Nixpkgs manual. - -Alternatively these sections could be dropped entirely, or moved to their own chapter and reference or reuse much of the Nixpkgs manual. -This is subject to refinement. - -## Declarative configuration management - -This section shows how the disconnected packages from previous examples can be wired up into a consistent and persistent user environment or operating system configuration. - -- Declarative user environments with Home Manager -- Declarative operating systems with NixOS -- Contributing to NixOS - -## Software development lifecycle - -- Caching -- Deployment -- Continuous integration -- Distributed builds -- Cross-compilation -- Bundling build results - - Virtual machines - - Docker containers -- Contributing to Nix - -# Contributor notes - ## GitHub heading anchors fails linkcheck Due to a [Sphinx bug][linkcheck gh bug], linkcheck fails when it verifies the