| 15 Mar 2024 |
 aidalgol | In hindsight, the "nix-community" GitHub org should probably have been called "nix-contrib". | 05:23:36 |
|  @nuko:shimeji.cafe changed their profile picture. | 08:26:18 |
 Jonas Chevalier | agreed. here is some past discussion we had on this: https://github.com/nix-community/infra/issues/410 | 08:26:50 |
| Jonas Chevalier | we tried to come up with a better name but nothing really stuck, and the cost of switching is also quite high | 08:27:17 |
|  dustsucker joined the room. | 09:30:38 |
|  @grahamc:nixos.org joined the room. | 23:11:57 |
| 16 Mar 2024 |
|  @federicodschonborn:matrix.org joined the room. | 00:12:13 |
|  @a-n-n-a-l-e-e:matrix.org joined the room. | 07:40:43 |
| @nuko:shimeji.cafe changed their profile picture. | 20:32:42 |
| 17 Mar 2024 |
|  eliaselias joined the room. | 10:39:09 |
|  cblacktech joined the room. | 17:07:19 |
| 18 Mar 2024 |
|  @papalpenguin:matrix.org joined the room. | 01:08:06 |
|  Clumsily6239 joined the room. | 03:20:58 |
| 19 Mar 2024 |
|  NixOS Moderation Botchanged room power levels. | 00:30:19 |
| 20 Mar 2024 |
|  @admin:nixos.org joined the room. | 03:26:22 |
 @accelbread:matrix.org | Hey, I think it would be useful if the flakes that autoupdate using github actions consolidated on a schedule to do so
This way users who update their flakes get the same nixpkgs version for all of their inputs following that schedule, thus reducing copies of nixpkgs pulled
This could help alleviate some concerns I heard during NixCon NA
Are there recommendations on how I should go about gathering consensus on a schedule?
I'd be willing to go around making PRs if/once we get consensus | 04:33:50 |
|  knownasred joined the room. | 06:07:12 |
|  leona joined the room. | 09:19:42 |
|  @lotte:chir.rs changed their profile picture. | 11:02:20 |
 Mic92 | Mhm. It will be quite hard to schedule this if people don't automerge their pull requests. | 14:09:35 |
| Mic92 | I do this, but not everyone. | 14:09:41 |
| Mic92 | Is overriding nixpkgs with the follow mechanism not enough? | 14:10:07 |
| @accelbread:matrix.org | Thats an option, but from newer folk found that annoying.
It doesnt have to be every repo; the more that do so, the less nixpkgs instances get cloned for those not using follows. Follows might also use a nixpkgs revision the flake's CI didn't test with
Theres a bunch of repos where GH actions updates, tests, and directly pushes on a schedule, no PR involved. Would be good to sync those at least | 15:44:13 |
| @admin:nixos.org left the room. | 16:27:20 |
| Mic92 | In my case I would at least want to see a pull request that checks if the new nixpkgs still passed all the test before mering it. | 17:36:06 |
| 21 Mar 2024 |
| @accelbread:matrix.org | Yeah, I have it run tests with the new nixpkgs, and if it passes all tests, it merges. Otherwise workflow fails and I get an email | 05:42:39 |
| @nuko:shimeji.cafe changed their profile picture. | 09:48:40 |
| NixOS Moderation Botchanged room power levels. | 18:03:13 |
| @grahamc:nixos.org left the room. | 20:07:44 |
| 22 Mar 2024 |
| @nuko:shimeji.cafe changed their profile picture. | 04:47:47 |
