In reply to @infinisil:matrix.org
Anyways, this definitely isn't the right place to discuss it. I recommend opening an issue for this and checking the original PR for why it was done this way

In reply to @elikoga:matrix.org

Also "kill [...] with fire" seems a bit heavy handed, it could certainly be spaced out on 2 release cycles with a warning in the first one

https://github.com/NixOS/nixpkgs/pull/326262

In reply to @elikoga:matrix.org
This one

Reading that thread makes me have ambivalent feelings:

1. I want to just forget about it because there is no consensus there (other than K900 who is very clear in that the option sound.enable 'just has to be killed with fire'). That I can fix my config and just leave it with that. I.E. that I do not feel comfortable (as a newcomer) to engage in that discussion'.
2. I still want to make other 'casual NixOS users' have a smoother experience if only for the reason that this 'stream of errors' is a preventable occurance.

Is that PR really the right place to talk about that?

In reply to @koen:procolix.com

Reading that thread makes me have ambivalent feelings:

1. I want to just forget about it because there is no consensus there (other than K900 who is very clear in that the option sound.enable 'just has to be killed with fire'). That I can fix my config and just leave it with that. I.E. that I do not feel comfortable (as a newcomer) to engage in that discussion'.
2. I still want to make other 'casual NixOS users' have a smoother experience if only for the reason that this 'stream of errors' is a preventable occurance.

Is that PR really the right place to talk about that?

In reply to @koen:procolix.com

Reading that thread makes me have ambivalent feelings:

1. I want to just forget about it because there is no consensus there (other than K900 who is very clear in that the option sound.enable 'just has to be killed with fire'). That I can fix my config and just leave it with that. I.E. that I do not feel comfortable (as a newcomer) to engage in that discussion'.
2. I still want to make other 'casual NixOS users' have a smoother experience if only for the reason that this 'stream of errors' is a preventable occurance.

Is that PR really the right place to talk about that?

Is that PR really the right place to talk about that?

Maybe a new "topic" (= thread) in the forum would a an appropriate place? I'm unsure what category there would be most fitting, though.

In reply to @ners:nixos.dev
@room as usual we posted a request for feedback. Please take a few minutes to leave your thoughts, critique, suggestions, praise, haikus…: https://github.com/nix-community/developer-workshop/issues/7

Also, here's a shared photo album that currently just contains our group photo. Feel free to add your own if you have something cool to share from the weekend. We'll try to get in the rest that we took ASAP. :)

(We'll soon have to find a new photo spot for our ever-growing group 😬)

https://photos.app.goo.gl/bpUVA7kYm36K7aLW8

In reply to @ners:nixos.dev
@room as a gentle reminder, please take a moment to leave some feedback about the ZHF hackathon here: https://github.com/nix-community/developer-workshop/issues/7

@ners:nixos.dev CI also only enforces formatting on files that are already formatted, so that makes it even harder xD

I think probably something like

git diff --name-only HEAD | while read -r file; do
  if nixfmt --check <(git show HEAD:"$file");
    then nixfmt "$file"
  fi
done

@ners:nixos.dev^

I think probably something like

git diff --name-only HEAD | while read -r file; do
  if nixfmt --check <(git show HEAD:"$file"); then
    nixfmt "$file"
  fi
done

The goal is to format the entirety of Nixpkgs in like a month or so, after which treefmt and editor auto-formatting should be usable on it :D