From 5397dad619530711c484e2715a074e31ce6a8ce6 Mon Sep 17 00:00:00 2001 From: Colin Date: Sat, 16 Nov 2024 14:19:04 +0000 Subject: [PATCH] nix: nixos-upstreaming: fix capitalization --- content/blog/2022-10-13-nixos-upstreaming.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/blog/2022-10-13-nixos-upstreaming.md b/content/blog/2022-10-13-nixos-upstreaming.md index fbbee0e..8305c15 100644 --- a/content/blog/2022-10-13-nixos-upstreaming.md +++ b/content/blog/2022-10-13-nixos-upstreaming.md @@ -4,7 +4,7 @@ description = "a low-maintenance workflow for upstreaming simple package changes date = 2022-10-13 +++ -as a [nix/nixOS](https://nixos.org) user, you'll inherently find yourself writing code, and some of this code might be valuable to others: be it new packages, improvements upon existing packages, or new services/options. part of what makes nix successful (IMO) is the ease of sharing work and upstreaming, so i'm setting out here to show some easy workflows for doing so. +as a [nix/NixOS](https://nixos.org) user, you'll inherently find yourself writing code, and some of this code might be valuable to others: be it new packages, improvements upon existing packages, or new services/options. part of what makes nix successful (IMO) is the ease of sharing work and upstreaming, so i'm setting out here to show some easy workflows for doing so. the number one thing you can do -- if you're not already -- is host your nix config publicly. for example, mine is [here](https://git.uninsane.org/colin/nix-files), and even without advertising it i occasionally hear from people in my orbit that they've found it useful. as a beginner i had some public configs i found on google or [wiby](https://wiby.me) which i routinely consulted, even though many of those authors probably never heard a word from the people like me who found use in their work.