| 23 Aug 2023 |
 raitobezarius | In reply to @asymmetric:matrix.dapp.org.uk
OK, I think I'm happy to add a mention to i686 also as a signifier of a broader move away from 32bits arches.. is that correct? Strict people would say this may be invalid to talk about tier5/6/7 platforms of Nixpkgs like mips32 :p | 18:06:58 |
| raitobezarius | I'd really just say 32 bits x86 | 18:07:08 |
| raitobezarius | In reply to @raitobezarius:matrix.org
Sometimes it's really just random end users with their own way of seeing things Also I wonder if undeveloped countries have "average" access to 64 bits machine | 18:07:38 |
| raitobezarius | But well, we kind of already suck for those countries because of how Nix works | 18:07:56 |
 infinisil | I will skip at least tomorrows docs team meetings (but maybe also some following ones) in order to focus on implementing RFC 140. | 21:57:07 |
| 24 Aug 2023 |
 @brian:bmcgee.ie | I have to miss today's meeting aswell, gotta pay the bills | 08:07:26 |
 @mightyiam:matrix.org | Sorry for not being there this time. | 14:06:24 |
| raitobezarius | ryantm: I just realized that https://ryantm.github.io/nixpkgs was quite high in search results on Google but outdated | 22:34:17 |
| raitobezarius | Could we do something about this? | 22:34:21 |
| raitobezarius | e.g. a robots.txt to reduce its position wrt to SEO | 22:34:30 |
| raitobezarius | (we have users citing it in nixpkgs PRs) | 22:35:11 |
 proofconstruction | That makes sense - it's the nixpkgs manual I use when I go looking for something. The mdbook style is so much better than a 50km long page | 22:49:16 |
| raitobezarius | Indeed, the problem is that it's not fresh/outdated | 22:51:36 |
| raitobezarius | I honestly prefer the 50 km long page :P | 22:51:46 |
| raitobezarius | But I think offering both is not bad at all | 22:51:54 |
 ryantm | Many people have told me they like it better than the official manual. I should commit to an update at least every release. | 23:50:07 |
| ryantm | !00% not going to make my SEO worse in some way as long as people are telling me they prefer my manual rendering. | 23:55:40 |
| ryantm | I'll try to update it this weekend! | 23:58:35 |
| 25 Aug 2023 |
| raitobezarius | Thank you | 00:05:12 |
|  @dylandoesprogramming:matrix.org left the room. | 00:05:36 |
| raitobezarius | That being said, I feel like it would help a lot to get this "alternative" rendering merged somehow | 00:06:40 |
| raitobezarius | I don't have a big opinion on the rendering, but I personally find it hard to navigate the mdbook style and I prefer the long page, some prefers the mdbook and that's fine, we just have contributors who don't know what to do when folks are enforcing rules from the outdated mdbook manual | 00:07:29 |
| proofconstruction | Unifying the rendering infrastructure for all the manuals has been discussed often and is on the roadmap https://github.com/nix-community/projects/issues/6, but we don't have the time/energy/(funds to throw at it)/etc currently | 00:13:20 |
| raitobezarius | Understandable | 00:15:24 |
| ryantm | In reply to @proofconstruction:matrix.org
Unifying the rendering infrastructure for all the manuals has been discussed often and is on the roadmap https://github.com/nix-community/projects/issues/6, but we don't have the time/energy/(funds to throw at it)/etc currently This is why I made mmdoc in the first place. I wanted to make a documentation rendering system that was lightweight enough to be kept on as part of nixos-rebuild and didn't add to the closure size. | 13:44:17 |
| ryantm | Totally get that I didn't put in the effort to push it over the finish line though, wish I had that energy. | 13:54:31 |
| ryantm | I started updating it and it looks like it's mostly just compatible with the existing docs! I think I can make a super small diff that's not too invasive! | 15:01:00 |
| raitobezarius | you mean nrd or mmdoc or something else? | 15:06:26 |
|  @janik0:matrix.org joined the room. | 15:11:18 |
| ryantm | mmdoc | 15:13:33 |
