| 28 Aug 2023 |
 @mightyiam:matrix.org | Sorry. We relocated recently. Lots of house chores. "I'm a software developer!", I keep saying. "Why am I doing plumbing work? Why am I hanging drapes?". Anyway, I'll try to get some progress on extracting the doctester into its own repo soon. That's my update. | 13:47:55 |
| @mightyiam:matrix.org | Thank ya'll for your works. | 13:48:16 |
| 29 Aug 2023 |
|  Lurkki joined the room. | 15:42:38 |
| 30 Aug 2023 |
|  wackbyte changed their profile picture. | 20:25:59 |
| 31 Aug 2023 |
 infinisil | Note that I'll continue abstaining from the doc team meetings for now, probably until after Nixcon | 12:45:17 |
 @zmitchell:matrix.org | The Jitsi room says that I need to wait for a moderator to let me in? | 13:01:48 |
| @zmitchell:matrix.org | That's pretty new | 13:02:13 |
 @garbas:matrix.org | zmitchell: I had the same problem yesterday at the marketing meeting. I solved it by creating the account | 13:02:51 |
| @zmitchell:matrix.org | Interesting | 13:03:34 |
| @zmitchell:matrix.org | Thanks | 13:03:38 |
 Alyssa Ross | https://jitsi.org/blog/authentication-on-meet-jit-si/ | 13:04:28 |
 alejandrosame | I won't be a le to join today's since I'll be in transit | 13:13:07 |
|  tdillenburg joined the room. | 13:36:21 |
 asymmetric | hey, the decision at the end (not sure whether it was taken or not) felt a bit rushed to me. with just a little more time we could've easily have reached unanimity imo | 15:10:35 |
| asymmetric | i understand it's not a super high priority decision, but still my pref would've been to dedicate a little bit more time to it | 15:11:18 |
| asymmetric | we were only 6 people in the call after all, it should be possible 🙂 | 15:11:40 |
|  moritz.hedtke removed their display name moritz.hedtke. | 16:13:14 |
 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 |
