| 25 Jul 2023 |
|  @federicodschonborn:matrix.org changed their profile picture. | 01:57:05 |
 asymmetric | I'm not sure I understand what's happening with the "postponed" column on the board. 99% of the issues there are done. How does that happen? | 09:39:54 |
| asymmetric | also, what's the purpose of the "prioritized" column? Prioritized for whom? AFAIU, work is taken on on a "willing to do this" basis, i.e. if somebody is assigned to a task, then it's prioritized "for them". | 09:41:54 |
| asymmetric | * also, what's the purpose of the "prioritized" column? Prioritized for whom? AFAIU, work is taken on on a "willing to do this" basis, i.e. if somebody is assigned to a task, then it's prioritized "for them". Is it supposed to capture "prioritized for the whole team"? If so, I don't see that as reflecting how the team has worked so far, and in any case, it takes up space without being used much. So I propose to remove it | 09:42:41 |
| asymmetric | In reply to @asymmetric:matrix.dapp.org.uk
I'm not sure I understand what's happening with the "postponed" column on the board. 99% of the issues there are done. How does that happen? Also what's the difference between postponed and stale? | 09:43:19 |
| asymmetric | In reply to @asymmetric:matrix.dapp.org.uk
I'm not sure I understand what's happening with the "postponed" column on the board. 99% of the issues there are done. How does that happen? * Also what's the difference between postponed and stale? I propose we remove stale | 09:43:49 |
| asymmetric | In reply to @asymmetric:matrix.dapp.org.uk
I'm not sure I understand what's happening with the "postponed" column on the board. 99% of the issues there are done. How does that happen? Also, does anyone know why the automation which should move merged PRs and closed issues to "done" isn't working? Is it just that it's not retroactive? | 09:47:38 |
| asymmetric | infinisil: just created this: https://github.com/NixOS/nixpkgs/pull/245358. Not sure how it interacts with https://github.com/NixOS/nixpkgs/issues/244056, I guess whichever gets merged first needs to take the other one into consideration | 10:22:32 |
| asymmetric | cc pennae | 10:22:41 |
 infinisil | In reply to @asymmetric:matrix.dapp.org.uk
infinisil: just created this: https://github.com/NixOS/nixpkgs/pull/245358. Not sure how it interacts with https://github.com/NixOS/nixpkgs/issues/244056, I guess whichever gets merged first needs to take the other one into consideration Yeah, my PR will take a while still, I'll rebase it as needed :) | 10:25:12 |
| asymmetric | posting this draft here for early feedback, as the topic is not my area of expertise: https://github.com/NixOS/nixpkgs/pull/245368 | 11:42:44 |
| asymmetric | Redacted or Malformed Event | 11:43:22 |
 nikstur | We have some NixOS documentation outside the nixos/doc/manual tree, e.g.: https://github.com/NixOS/nixpkgs/tree/master/nixos/modules/system/boot/loader/external Is this something we want to support/encourage in the long run? I think it's nice because it keeps the docs close to the code but on the other hand its makes it more difficult for docs contributors to find the source. | 13:44:55 |
| nikstur | * We have some NixOS documentation outside the nixos/doc/manual tree, e.g.: https://github.com/NixOS/nixpkgs/tree/master/nixos/modules/system/boot/loader/external Is this something we want to support/encourage in the long run? I think it's nice because it keeps the docs close to the code but on the other hand it makes it more difficult for docs contributors to find the source. | 13:45:05 |
| infinisil | nikstur: +1 from me, having documentation right next to the implementation makes it easy to update it | 13:52:04 |
 raboof | Redacted or Malformed Event | 13:59:42 |
| nikstur | In reply to @raboof:matrix.org
yeah, if you can change 'the thing' and 'the documentation for the thing' in the same commit, that's very helpful both when reviewing it and when looking at the change in the history But this would also be possible if the docs lay somewhere completely different in the repo | 14:02:31 |
| raboof | 🤦sorry I misread, nvm | 14:03:44 |
|  ncfavier changed their profile picture. | 16:43:13 |
| 26 Jul 2023 |
| infinisil | asymmetric: Ping for https://github.com/nix-community/nixdoc/pull/62 :) | 16:50:41 |
| asymmetric | In reply to @infinisil:matrix.org
asymmetric: Ping for https://github.com/nix-community/nixdoc/pull/62 :) Traveling today, will look at it tomorrow hopefully | 19:53:14 |
| 27 Jul 2023 |
|  ribosomerocker joined the room. | 03:04:09 |
|  @quark97:matrix.org left the room. | 04:35:42 |
|  @viktor:kleen.org left the room. | 07:07:34 |
 alejandrosame | I won't be joining today's meeting. See you next week! | 12:01:50 |
| 29 Jul 2023 |
| infinisil | I won't be there for the Monday meeting | 12:33:54 |
 proofconstruction | I'm back in civilization and will be at the Monday meeting | 22:57:22 |
| 30 Jul 2023 |
|  h7x4 set a profile picture. | 08:30:49 |
| asymmetric | https://discourse.nixos.org/t/nixos-installation-instructions-could-use-a-lot-more-details/31062/6?u=asymmetric | 16:42:32 |
| asymmetric | Is the SE placement of the manuals something that the marketing team needs to work on (as in SEO), or is it dependent on us, for example by splitting the manual to reduce page load? | 16:43:47 |
