| 31 Aug 2023 |
 proofconstruction | I agree it felt rushed. There was no further discussion/action after the thumbs-up general agreement. I would like to further discuss (here or ideally in the thread of a PR proposing concrete changes) some of the ideas for implementing this. | 18:21:09 |
 infinisil | What is the context? | 18:24:56 |
| infinisil | proofconstruction: asymmetric: ^ | 18:25:10 |
| proofconstruction | We had some more discussion around how/whether to include mention (or more) of unofficial tooling, including commercial products in the ecosystem. Examples that came up were the pinning nixpkgs tutorial which explains a niv workflow, and the GitHub Actions CI tutorial which (my opinion, my words, etc) is really just a Cachix/Magic Nix Cache advertisement instead of a tutorial. The final thing that happened in the meeting was a thumbs-up/down "vote" for whether to mention 3rd-party FOSS tools on nix.dev. (It wasn't really a vote in the sense of establishing a mandate/obligating a specific action be taken, but I can't think of a better word for this currently). Separately, we essentially dropped discussion around mentioning commercial stuff, with some agreement (not consensus here either, no decisions, etc) to kick that question back to the foundation board, though this is more contentious (especially given the current climate around governance). | 18:50:57 |
| infinisil | I see, thanks! | 19:00:34 |
| infinisil | I don't have a big opinion on this, doesn't seem worth spending too much time on for now | 19:00:47 |
| infinisil | (well, it's part of the bigger question for how to onboard and offboard official projects, which is definitely worth discussing) | 19:02:33 |
| proofconstruction | Yes, it's certainly not a high priority compared to e.g making sure we actually have documentation for the official projects, or improving this team's PR -> review -> merge velocity. Just echoes some broader discussion currents happening in the community. | 19:08:01 |
| 1 Sep 2023 |
 @penguincoder:matrix.wolfie.pw | maybe instead of putting it directly in nix.dev we could make an "awesome nix reading" repo instead? that could be more independent, include commercial software without any implication of promotion, and all kinds of FOSS sources too. | 14:21:04 |
 fricklerhandwerk | There already exists https://github.com/nix-community/awesome-nix and the problem I personally have with it is that it's not helping to guide if there is just a huge collection of things all you know about is the name. And that's our biggest problem: getting the big picture and essential skills to be able to navigate the ecosystem and problem space yourself | 14:51:23 |
| fricklerhandwerk | * There already exists https://github.com/nix-community/awesome-nix and the problem I personally have with it (or any "awesome" resource) is that it's not helping to guide if there is just a huge collection of things all you know about is the name. And that's our biggest problem: getting the big picture and essential skills to be able to navigate the ecosystem and problem space yourself | 14:51:39 |
| fricklerhandwerk | * There already exists https://github.com/nix-community/awesome-nix and the problem I personally have with it (or any "awesome" resource) is that it's not helping to guide beginners if there is just a huge collection of things all you know about is the name. And that's our biggest problem: getting the big picture and essential skills to be able to navigate the ecosystem and problem space yourself | 14:51:51 |
| @penguincoder:matrix.wolfie.pw | Then the problem should become a tree-like shape. Start at the very beginning, then make a bunch of choices (IOW pick a tool), and go down a bunch of paths to show how you might navigate the solutions. For instance, after getting nix installed, you could make a flake tutorial, then use flake-parts down one path, and flake-utils down another... then show how you might make derivations after that using each system. | 15:02:55 |
| @penguincoder:matrix.wolfie.pw | As a beginner myself, it would be helpful to have those kinds of paths written down so that I can see the choices that are made and get a better handle on why as well as what. | 15:06:40 |
| fricklerhandwerk | In reply to @penguincoder:matrix.wolfie.pw
Then the problem should become a tree-like shape. Start at the very beginning, then make a bunch of choices (IOW pick a tool), and go down a bunch of paths to show how you might navigate the solutions. For instance, after getting nix installed, you could make a flake tutorial, then use flake-parts down one path, and flake-utils down another... then show how you might make derivations after that using each system. Yes, that is exactly what this PR is trying to address: https://github.com/NixOS/nix.dev/pull/701 | 15:41:58 |
| 2 Sep 2023 |
 @zmitchell:matrix.org | proofconstruction: I was going to post the working group meeting notes today. I'm working on the This Month in Nix Docs post now, please don't post that too. | 00:02:41 |
| @zmitchell:matrix.org | https://discourse.nixos.org/t/this-month-in-nix-docs-4-july-august-2023/32502 | 00:28:52 |
| infinisil | zmitchell: Hmm you didn't reuse the previous start of the update: https://pad.lassul.us/BQletwJYRkWAVZ9HY76kGA | 00:37:21 |
| infinisil | And the Nixpkgs PR list seems rather poor, we curated that in the above pad | 00:37:35 |
| infinisil | In particular https://github.com/NixOS/nixpkgs/pull/245243 seems to be missing, which we put as a highlight in the pad | 00:37:52 |
| infinisil | * And the Nixpkgs PR list seems rather poor (has various package updates), we curated that in the above pad | 00:38:25 |
| infinisil | (actually, seems to be written about, but not linked to!) | 00:42:22 |
| proofconstruction | Apologies, I just realized nothing got posted from yesterday and dumped the notes to discourse before going out for a walk. I can still edit the post if you have additions. | 02:47:18 |
| @zmitchell:matrix.org | I took all of the bullets from the highlights section and wrote about them. The only one I didn’t write about was the code examples test because it hasn’t been merged yet, and, as discussed on Thursday, will take quite some time before it gets there. | 18:37:24 |
| @zmitchell:matrix.org | And the extra PRs look like they're because of the additional tag that was added to the script that scrapes GitHub | 18:43:34 |
| @zmitchell:matrix.org | I think it was a good idea to include that tag (I'd rather not miss something), but I can actually curate the PR list next time. Generally I'm not sure people care all that much :) | 18:44:55 |
| 3 Sep 2023 |
| infinisil | zmitchell: Still, the link to the clean up contributing docs PR is missing | 14:54:04 |
| @zmitchell:matrix.org | I added a comment with the link | 16:40:27 |
| 4 Sep 2023 |
|  @nord:one.ems.host left the room. | 04:05:11 |
| fricklerhandwerk | I’m in the process of joining the meeting but there is some weird authentication issue | 14:03:29 |
