Nix Documentation | 435 Members | |
| Discussion about documentation improvements around the Nix ecosystem | 92 Servers |
| Sender | Message | Time |
|---|---|---|
| 5 Jul 2023 | ||
| 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 | |
| 23:48:25 | ||
| 6 Jul 2023 | ||
| Welcome | 00:02:21 | |
| 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 | |
In reply to @mightyiam:matrix.orgThank you Dawn! | 00:39:29 | |
In reply to @fricklerhandwerk:matrix.org 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 | |
| Running a couple of minutes late for the meeting, be there in a second | 13:01:27 | |
| As far as I know it's an hour from now. | 13:02:04 | |
| This is the learning journey working group | 13:02:24 | |
| Oh, okay | 13:02:42 | |
| couldn't make it to the meeting, but checking the notes:
no, we worked our ass of getting large dependencies out of the manual | 15:19:37 | |
| * couldn't make it to the meeting, but checking the notes:
no, we worked our ass off getting large dependencies out of the manual | 15:19:44 | |
| live reload isn't something we can currently do at all anyway because every rebuild is necessarily a complete rebuild | 15:21:30 | |
there's no benefit to adding that much complexity over a small script that's pretty much inotifywait | while read; do nix-build; done | 15:22:09 | |
| (we're in favor of the script fwiw) | 15:22:30 | |
| we really have to get other things in order first before live-reload even begins to make sense | 15:33:50 | |
| Quick update & question. We plan to announce the migration of Nix.dev to the community/foundation.
| 15:44:05 | |
In reply to @ronef:matrix.org
| 16:22:05 | |
| Sending the announcement for review, feel free to edit directly :) | 16:55:17 | |
| I think we should add a linkchecker run triggered on a timer to nix.dev GitHub Actions. I pretty frequently get failed CI runs that have nothing to do with my changes because an anchor link somewhere broke. For instance: here | 18:34:51 | |
| 7 Jul 2023 | ||
| 20:24:41 | ||
| 9 Jul 2023 | ||
| 14:31:49 | ||
| 10 Jul 2023 | ||
| 15:47:52 | ||
| 11 Jul 2023 | ||
| 03:39:32 | ||