!avYyleMexqjFHoqrME:nixos.org

Nix Documentation

438 Members
Discussion about documentation improvements around the Nix ecosystem93 Servers

Load older messages


SenderMessageTime
12 Aug 2022
* @ShadowRZ:matrixim.cc夜坂雅 | Yorusaka Miyabi wonders if there's any requirements for NixOS documentation to use DocBook.01:42:12
@pennae:matrix.eno.spacepennaepretty much everything except modules and the options we haven't touched yet use markdown as their primary format and just render to docbook as an intermediate format. some modules do that as well, albeit not automatically01:47:31
@ShadowRZ:matrixim.cc夜坂雅 | Yorusaka Miyabi
In reply to @pennae:matrix.eno.space
pretty much everything except modules and the options we haven't touched yet use markdown as their primary format and just render to docbook as an intermediate format. some modules do that as well, albeit not automatically
I thought that, eventually all NixOS module option docstrings are written in CommonMark.
02:55:24
@pennae:matrix.eno.spacepennaethat's the plan :)02:56:11
@pennae:matrix.eno.spacepennaehope we'll get there for 22.1102:56:18
@pennae:matrix.eno.spacepennaecurrently waiting for review on https://github.com/NixOS/nixpkgs/pull/185474 before we go any further02:57:00
@ShadowRZ:matrixim.cc夜坂雅 | Yorusaka Miyabi
In reply to @pennae:matrix.eno.space
currently waiting for review on https://github.com/NixOS/nixpkgs/pull/185474 before we go any further
In this PR I found that there's a remaining part that looks like DocBook. 😅
03:34:59
@ShadowRZ:matrixim.cc夜坂雅 | Yorusaka MiyabiThis PR looks good to me. BTW, is lib.mdDoc a marker ?03:36:43
@pennae:matrix.eno.spacepennae it wraps the given text in a form make-options-doc recognizes as markdown so it can convert it to docbook, yes 03:38:09
@Ericson2314:matrix.orgJohn Ericsonhttps://github.com/NixOS/nix/pull/6877#issuecomment-1212877941 Eelco commented providing more details why he doesn't like the arch chapter, and seems to be anti having a reference17:02:06
@Ericson2314:matrix.orgJohn Ericson(I wrote that in the Nixpkgs arch chanel, but I meant to write that in this channel)17:03:02
@Ericson2314:matrix.orgJohn EricsonBased on our call yesterday, I think we all disagree with that?17:03:19
@Ericson2314:matrix.orgJohn Ericsonso it would be good to do something as a team about that17:03:27
@tpw_rules:matrix.orgtpw_rulesis there a way to automatically extract that stuff into something that's not doxygen?19:13:48
@Ericson2314:matrix.orgJohn Ericson tpw_rules: not in a good way 19:27:28
@Ericson2314:matrix.orgJohn Ericsondoxygen is is per defintion code decs19:27:39
@Ericson2314:matrix.orgJohn Ericson * doxygen is is per defintion code docs19:27:41
@Ericson2314:matrix.orgJohn Ericsonthere is no good way to get spec prose from that19:27:52
@tpw_rules:matrix.orgtpw_rulesi was thinking more about the literate comment19:29:03
@pennae:matrix.eno.spacepennaeioo putting high-level docs in code is only any good for code bases that are structured like one would tell their story, and nix definitely isn't at this point19:32:25
@denna:matrix.orgolaf John Ericson: i am not opinionated about which repository docs go, as long as they go somewhere for a reason and the reasons gets documented (so we know for the future as well).
The statement that eelco "is anti having reference" is a bit broad.
It seems he believes that the nix documentation should be code reference.
But your work is spec reference. (can i say so?)
22:51:26
@Ericson2314:matrix.orgJohn Ericson olaf: Sure, I would appreciate you seconding me it is spec reference not code reference 22:52:42
@Ericson2314:matrix.orgJohn EricsonAs to the repo, well I am pretty sure bottom half documentation does belong there, not top half documentation22:53:52
@Ericson2314:matrix.orgJohn EricsonI don't think he wants it elsewhere because then any keeping in sync problem would just get worse22:54:16
@Ericson2314:matrix.orgJohn Ericsonand we can't require PRs that add new behavior also update the spec22:54:29
@pennae:matrix.eno.spacepennaehow frequent are such PRs outside of explicitly experimental features?22:59:21
@pennae:matrix.eno.spacepennaefor experimental stuff it's probably okay if well-written documentation lags behind the facts a bit, as long as the necessary information is there somewhere23:00:04
13 Aug 2022
@Ericson2314:matrix.orgJohn Ericson pennae: well most features should be experimental, I have a backlog of a few of them not sure what others got 03:09:00
@Ericson2314:matrix.orgJohn EricsonA space that multiple implementations folllow I understand keeping separate03:09:22
@Ericson2314:matrix.orgJohn EricsonBut I still rather start with that information in the manual03:10:07

Show newer messages


Back to Room ListRoom Version: 6