| 19 Mar 2022 |
 hexa | projects on the org level span multiple repositories which is more realistic for release engineering | 23:47:18 |
| 20 Mar 2022 |
 jonringer | In reply to @janne.hess:helsinki-systems.de
Does anyone know the purpose of the 22.05 milestone? It seems kind of redundant to the org-wide project to me. Or is there something nice about it I haven't noticed yet? we also wanted a way to track things across different repos: homepage, nixos-org-configuration, nixpkgs, etc | 00:34:26 |
| hexa | basically what I said, no? | 02:26:36 |
| jonringer | Yea, I read the question, answered it, then read your answer 😅 | 03:32:59 |
 Janne Heß | So the milestone is redundant and I don't have to care about it in my process? I'm also trying to write stuff like this down into the wiki so the next generations know what to do with it | 09:46:02 |
|  stigo joined the room. | 13:05:50 |
| jonringer | In reply to @janne.hess:helsinki-systems.de
So the milestone is redundant and I don't have to care about it in my process? I'm also trying to write stuff like this down into the wiki so the next generations know what to do with it I've stopped using it as a tool. Lots of little things made their way in with no one to do the work. So they're meaningless | 16:22:07 |
| 21 Mar 2022 |
|  nixinator joined the room. | 17:09:36 |
|  John Ericson joined the room. | 17:20:36 |
| 22 Mar 2022 |
|  Fabian Affolter joined the room. | 19:46:28 |
| 23 Mar 2022 |
| hexa | https://github.com/NixOS/nixpkgs/pull/161146 | 02:33:29 |
| hexa |
./alias/maintainers/scripts/remove-old-aliases.py --file ./pkgs/top-level/aliases.nix --year 2019 --month 6
| 02:33:35 |
| hexa | this feels like something that should be done once every release and a release manager entry could be helpful | 02:33:58 |
| hexa | * this feels like something that should be done once every release and a release manager entry could be helpful to make sure it happens | 02:34:03 |
| jonringer | Agreed | 04:34:39 |
| hexa | * this feels like something that should be done once every release and a release manager wiki entry could be helpful to make sure it happens | 04:36:57 |
| Janne Heß | In reply to @hexa:lossy.network
this feels like something that should be done once every release and a release manager wiki entry could be helpful to make sure it happens I'll add it to my local checkout and PR it when I actually did it | 10:58:49 |
| Janne Heß | In reply to @hexa:lossy.network
this feels like something that should be done once every release and a release manager wiki entry could be helpful to make sure it happens * I'll add it to my local checkout and PR it when I actually removed the aliases | 10:58:57 |
| 25 Mar 2022 |
|  sielicki joined the room. | 16:28:07 |
| sielicki | not really sure where to ask this, but the nix-community/nixos-wsl repo is looking to get a nix tarball and installer onto the windows store and that may mean managing a windows build server and/or a microsoft-blessed signing key. nzbr or myself could reach out to microsoft directly for this, but that feels inappropriate given that there's a team dedicated to this sort of thing.
https://github.com/nix-community/NixOS-WSL/issues/63
https://github.com/microsoft/WSL-DistroLauncher#publishing-pre-requisites
who can I contact about this? | 16:32:02 |
| sielicki | I just think that key should be in the hands of someone on the infrastructure or releng team. | 16:32:43 |
| Janne Heß | maybe in the #infra:nixos.org channel? | 17:20:36 |
| 26 Mar 2022 |
|  Artturin joined the room. | 02:25:54 |
|  andi- joined the room. | 07:59:02 |
|  Lars Lillo Ulvestad joined the room. | 23:10:01 |
| 27 Mar 2022 |
| hexa | since it will soon be time to ping all package set maintainers, how could I formally join the python-band without subscribing to the madness that is pkgs/development/python-modules via CODEOWNERS? | 16:14:40 |
| hexa | * since it will soon be time to ping all package set maintainers, how could I formally join the python-band without subscribing to the madness that is pkgs/development/python-modules via CODEOWNERS? Subscribing there makes GitHub notifications entirely unusable. | 16:15:08 |
| Janne Heß | In reply to @hexa:lossy.network
since it will soon be time to ping all package set maintainers, how could I formally join the python-band without subscribing to the madness that is pkgs/development/python-modules via CODEOWNERS? Subscribing there makes GitHub notifications entirely unusable. I thought about that as well and my idea was to take the list of Subsystem: @maintainer and put it into the release wiki. If every RM just uses this list, people who want to join/leave can just PR against the release wiki. Would that work for you? | 17:29:46 |
| hexa | better, put it into the nixpkgs repo so people can manage it themselves | 17:30:16 |
| hexa | * better yet, put it into the nixpkgs repo so people can manage it themselves | 17:30:29 |
