| 15 May 2023 |
|  abathur joined the room. | 21:00:53 |
| abathur | cross-reporting from #marketing:nixos.org (https://matrix.to/#/!tPxtoBdChSsxHuBlNW:nixos.org/$PgasljhyDuZ2RX2W1XUzjc8CaaOuMyIaDKds7_5YwXk?via=matrix.org&via=nixos.dev&via=nixos.org) but someone in #nix:nixos.org reported that there are no titles in the links on https://nixos.org/learn.html
a quick skim makes me think these are sourced from nix.dev and I see the nix.dev flake consumed in the homepage repo, so I'm guessing this is a side-effect some restructuring the doc team is working on?
| 21:02:53 |
| abathur | * cross-reporting from #marketing:nixos.org (https://matrix.to/#/!tPxtoBdChSsxHuBlNW:nixos.org/$PgasljhyDuZ2RX2W1XUzjc8CaaOuMyIaDKds7_5YwXk?via=matrix.org&via=nixos.dev&via=nixos.org) but someone in #nix:nixos.org reported that there are no titles in the links on https://nixos.org/learn.html
a quick skim makes me think these are sourced from nix.dev and I see the nix.dev flake consumed in the homepage repo, so I'm guessing this is a side-effect of some restructuring the doc team is working on?
| 21:10:48 |
 @zmitchell:matrix.org | They are sourced from nix.dev, but I'm not exactly sure how. | 22:55:35 |
 fricklerhandwerk | Oh yes, that's the problem. Maybe we can just stop the including altogether: https://github.com/NixOS/nixos-homepage/pull/1054 | 22:57:12 |
| 17 May 2023 |
|  shivaraj-bh changed their display name from Shivaraj B H to shivaraj-bh. | 12:31:05 |
|  @silvio:booq.org joined the room. | 14:09:21 |
| 18 May 2023 |
|  maj joined the room. | 12:21:18 |
 asymmetric | is it on purpose that on the board, when a PR is merged it gets marked as "postponed", rather than "done"? https://github.com/orgs/NixOS/projects/15/workflows/1946068 | 12:22:31 |
| @zmitchell:matrix.org | Almost certainly not | 13:00:07 |
 j-k | swapped it now, can mention it in the call now or the normal docs call later today | 13:02:12 |
| fricklerhandwerk | I disabled the workflows to add documentation-related things from Nixpkgs, NixOS, and Nix. It's way too much stuff we can't work off anyway, and will probably even be overwhelming for dedicated maintainers. I take care of the Nix manual already, so probably no need to dump that on the team unless there are broader issues. | 13:08:25 |
| asymmetric | i don't know if i'll be able to join the meeting today, so here's a little status update:
- been mostly busy with maintaining nixdoc: want to understand rnix well, so can keep it up to date (and incorporate work from pennae that bumps rnix/rowan)
- this also has lead me to review, and apply to become a shepherd for, the doc-comments RFC
- i also started looking into how nix.dev can look+feel more official, and opened a couple PRs there
i think both of these will keep me busy for the next couple of weeks
| 13:41:36 |
| asymmetric | * i don't know if i'll be able to join the meeting today, so here's a little status update:
- been mostly busy with maintaining nixdoc: want to understand it (and rnix/rowan) well, so can keep it up to date (and incorporate work from pennae that bumps rnix/rowan)
- this also has lead me to review, and apply to become a shepherd for, the doc-comments RFC
- i also started looking into how nix.dev can look+feel more official, and opened a couple PRs there
i think both of these will keep me busy for the next couple of weeks
| 13:41:56 |
| asymmetric | * i don't know if i'll be able to join the meeting today, so here's a little status update:
- been mostly busy with maintaining nixdoc: want to understand it (and rnix/rowan) well, so can keep it up to date (and incorporate work from pennae that bumps rnix/rowan)
- the context is the same, so this also has lead me to review, and apply to become a shepherd for, the doc-comments RFC
- i also started looking into how nix.dev can look+feel more official, and opened a couple PRs there
i think both of these will keep me busy for the next couple of weeks
| 13:42:52 |
| asymmetric | * i don't know if i'll be able to join the meeting today, so here's a little status update:
- been mostly busy with maintaining nixdoc: want to understand it (and rnix/rowan) well, so can keep it up to date (and incorporate work from pennae that bumps rnix/rowan)
- the context is the same, so this also has lead me to review, and apply to become a shepherd for, the doc-comments RFC
- i also started looking into how nix.dev can look+feel more official, and opened a couple PRs there: one and two
i think both of these will keep me busy for the next couple of weeks
| 13:43:48 |
| 19 May 2023 |
 @johannes.kirschbauer:scs.ems.host | In case you need someone i‘ve worked quite a bit with rnix and nixdoc. So would be happy to answer questions. In case you have any. | 12:13:52 |
| 20 May 2023 |
|  Charles joined the room. | 02:55:21 |
| Charles | Does Nix/NixOS have an equivalent documentation page to https://wiki.archlinux.org/title/Help:Reading#Installation_of_packages? | 02:59:21 |
| Charles | I ask because I personally can't recall encountering such a thing (I've been using NixOS for nearly 2 years now I think), and if there really isn't one, I would be interested in trying to contribute it | 03:11:56 |
 @kranzes:matrix.org | In reply to @charles:computer.surgery
Does Nix/NixOS have an equivalent documentation page to https://wiki.archlinux.org/title/Help:Reading#Installation_of_packages? We have it in the manual I believe | 13:38:03 |
| @kranzes:matrix.org | 
Download image.png | 13:38:19 |
| @kranzes:matrix.org | there's also this | 13:38:23 |
| @kranzes:matrix.org | 
Download image.png | 13:38:55 |
| @kranzes:matrix.org | 
Download image.png | 13:39:05 |
| Charles | 👀 | 15:54:08 |
 @wiseh:matrix.org |
Does Nix/NixOS have an equivalent documentation page to https://wiki.archlinux.org/title/Help:Reading#Installation_of_packages?
You may also be interested in this https://github.com/NixOS/nix.dev/issues/554
| 22:08:18 |
| Charles | ooh, yes | 22:09:45 |
| Charles | the main use-case i had in mind for such a piece of documentation is similar to how the Arch page is used throughout its wiki: instead of giving a concrete example of how to install a package, things just link to a generic page explaining all the ways it can be done (and ideally enumerating the differences between each method) | 22:19:41 |
| Charles | the linked issue sounds like it's heading towards that sort of thing, which is great | 22:20:16 |
