| 5 Jul 2023 |
 asymmetric | https://github.com/NixOS/nixos-homepage/blob/87127a734b9789c222d404e4515a498a31c69edc/flake.nix#L8C1-L8C1 | 09:44:23 |
 @pennae:matrix.eno.space | In reply to @asymmetric:matrix.dapp.org.uk
It looks like that action only updates nixpkgs, which is not used for the manual ah, missed that. | 12:56:40 |
| @pennae:matrix.eno.space | looks like the hourly update takes care of those, and finally picked up the md manual and deployed it | 12:57:03 |
|  wamirez joined the room. | 23:32:55 |
| wamirez | Hello NixOS documentation team,
this is Daniel and I wanted to introduce myself to you all as briefly as possible to not break the flow of your conversation. The reason for my showing up out of the blue is that I'd like to become more familiar with the Nix environment/community, with the goal of landing a spot in one of next year's Summer of Nix mobs as a participant.
I've been catching up here and there with "new" paradigms and tools like functional programming, lambda calculus, and Haskell, after many years of procedural programming being beaten into my head by university courses and then of me doubling down on it on my own. I chose to study the closest thing to my hobby (mountaineering) that my home university had to offer, which at the time was geological engineering, only to find out later that a hobby is usually just that: a hobby. Nevertheless, I'd like to think that I have a good framework for tackling problems, and also good language skills that can be of use to contribute to documentation projects you may have or need help with :).
On a superficial level, and to get me started, I thought I could process some of the Nix Hour recordings and come up with news articles based on them to make myself acquainted with the jargon and the ecosystem before working on Nix.dev's open issues and/or pull requests. Of course, I'm open to any suggestions or roadmaps you may already have in place.
Cheers from the Venezuelan Andes,
Daniel RamÃrez | 23:41:36 |
| wamirez set a profile picture. | 23:48:25 |
| 6 Jul 2023 |
 @mightyiam:matrix.org | Welcome | 00:02:21 |
 fricklerhandwerk | Hey Daniel, awesome to have you! I warmly recommend to say hi in the team meetings, and feel your way around nix.dev and our maintainers handbook. We have lots of stuff going on where help would be highly appreciated. | 00:09:54 |
| wamirez | In reply to @mightyiam:matrix.org
Welcome Thank you Dawn! | 00:39:29 |
| wamirez | In reply to @fricklerhandwerk:matrix.org
Hey Daniel, awesome to have you! I warmly recommend to say hi in the team meetings, and feel your way around nix.dev and our maintainers handbook. We have lots of stuff going on where help would be highly appreciated. Thanks a lot!
I will take a look at those and will definitely stop by to say hello in the team meetings.
| 00:44:53 |
 @zmitchell:matrix.org | Running a couple of minutes late for the meeting, be there in a second | 13:01:27 |
| @mightyiam:matrix.org | As far as I know it's an hour from now. | 13:02:04 |
 henrik-ch | This is the learning journey working group | 13:02:24 |
| @mightyiam:matrix.org | Oh, okay | 13:02:42 |
| @pennae:matrix.eno.space | couldn't make it to the meeting, but checking the notes:
is it OK to pull in nodejs and a larger tree of dependencies for an update to the manuals' build system? This is related to a live-reload feature.
no, we worked our ass of getting large dependencies out of the manual | 15:19:37 |
| @pennae:matrix.eno.space | * couldn't make it to the meeting, but checking the notes:
is it OK to pull in nodejs and a larger tree of dependencies for an update to the manuals' build system? This is related to a live-reload feature.
no, we worked our ass off getting large dependencies out of the manual | 15:19:44 |
| @pennae:matrix.eno.space | live reload isn't something we can currently do at all anyway because every rebuild is necessarily a complete rebuild | 15:21:30 |
