| 21 Jul 2023 |
 raitobezarius | I am very interested into that too | 22:36:41 |
| raitobezarius | I can help reviewing, etc. | 22:36:44 |
|  @nasrally:matrix.org joined the room. | 23:48:10 |
| 22 Jul 2023 |
 asymmetric | As soon as I’m back at my laptop I’ll look into this too, it should def be documented. It’s sad that the best documentation for this is the wiki | 12:35:20 |
 toonn | raitobezarius: supported.nix has since been disappeared from the repo. | 13:22:01 |
| toonn | That issue wasn't even meant as a draft of an implementation really. Just *something* to start discussion. | 13:23:13 |
| toonn | Looks like supported.nix was kinda replaced by https://github.com/NixOS/nixpkgs/blob/master/lib/systems/flake-systems.nix | 13:37:01 |
| toonn | Which is now just a flat list with comments indicating support tiers. | 13:37:22 |
| asymmetric | btw i'veopened a separate issue for this, lmk if it's a duplicate of something else https://github.com/NixOS/nixpkgs/issues/244686 | 18:53:52 |
| toonn | asymmetric: Oh, just pinged you on the PR I updated. | 20:44:16 |
| 24 Jul 2023 |
 henrik-ch | I won't be able to join today's meeting. Have a good session! | 13:32:55 |
| asymmetric | In reply to @toonn:matrix.org
asymmetric: Oh, just pinged you on the PR I updated. i'm primarily interested in documenting the tiers in the manual, as that's where most users would go and check, imo. the manual could/should reference the location in nixpkgs where this is codified, if one exists. Not sure where that would be, after reading amjoseph's review | 13:54:19 |
| asymmetric | In reply to @toonn:matrix.org
asymmetric: Oh, just pinged you on the PR I updated. * i'm primarily interested in documenting the tiers in the manual, as that's where most users would go and check, imo. the manual could/should reference the location in nixpkgs where this is codified, if one exists. Not sure where that would be though, after reading amjoseph's review | 13:54:36 |
 proofconstruction | Won't be at the meetings today or Thursday, taking a break from computers to go fishing (stream processing) | 19:17:53 |
| proofconstruction | Well I guess that sent late. Anyway | 19:18:11 |
 infinisil | https://github.com/NixOS/nixpkgs/pull/245243 | 21:34:00 |
| 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 |
