| 29 Apr 2025 |
 Mic92 | Why do we need the nix overlay? | 17:43:47 |
| Mic92 | Is nix.package not enough? | 17:43:53 |
| Mic92 | I do not want to break random other packages by overriding nix in different places | 17:44:16 |
 hexa (signing key rotation when) | we don't set nix.package, but we could | 17:44:18 |
| Mic92 | Ok. I can add this | 17:44:55 |
| hexa (signing key rotation when) | we were tracking what ever nix was shipped with hydra on all the build/ machines | 17:44:58 |
| hexa (signing key rotation when) | which was pointless for haumea and pluto | 17:45:13 |
| hexa (signing key rotation when) | so maybe just in hydra.nix this time | 17:45:22 |
 John Ericson | https://github.com/NixOS/hydra/pull/1482 Mic92 left some questions on that | 18:23:33 |
| Mic92 | hexa (signing key rotation when): no specific procedure required for reboot on mimas, right? | 18:53:50 |
 vcunat | I don't think so. | 18:59:56 |
| hexa (signing key rotation when) | no | 19:26:32 |
| John Ericson | looks good, approved | 20:14:02 |
| 30 Apr 2025 |
 Jeremy Fleischman (jfly) | Shahar "Dawn" Or (mightyiam) and I would like to discuss deploying https://github.com/molybdenumsoftware/pr-tracker to official infrastructure at this week's team meeting. | 08:59:56 |
 Sandro 🐧 | The key difference to the other projects is, that it stores the results in a database, right? | 12:46:24 |
| Sandro 🐧 | Does it already expose a minimal web ui like nixpk.gs? I have interest in trying to deploy it because the existing pr-tracker performs not so well for me on our hardware due to io constraints | 12:47:30 |
 @adam:robins.wtf | This looks great. I see you're suggesting users could subscribe to some events through pr-tracker. If you'll be getting installed as a webhook receiver for the repo, would you be willing to route all webhooks you receive on to other targets on request? e.g. so others could leverage the access you've received to build their own tooling? Or would that be a level of service you'd prefer not to commit to? | 12:54:28 |
| @adam:robins.wtf | If not, would that be a standalone app we should consider? | 12:55:03 |
| @adam:robins.wtf | Or alternatively, it would be nice to have a formal way to request such webhook integration. I've been tinkering with a similar app of my own to track nixpkgs data, and eventually it would reach the point where I'd like access to the webhook feed. | 13:00:19 |
 Alyssa Ross | In reply to @sandro:supersandro.de
Does it already expose a minimal web ui like nixpk.gs? I have interest in trying to deploy it because the existing pr-tracker performs not so well for me on our hardware due to io constraints Do you make sure your git repo is regularly GCed? | 13:24:25 |
| Sandro 🐧 | I thought we did but after doinga double check apperantly not 🤔 that explains a LOT...
There was a nixpkgs PR for a module, so that people don't need to copy bits from your config but that kinda went stale. | 13:26:24 |
| Sandro 🐧 | maybe we should finish that but we are getting OT | 13:26:34 |
| Jeremy Fleischman (jfly) | we have not build a UI. our preference (not set in stone) would be for this to be a backend for other people to build stuff on top of | 15:27:00 |
| Jeremy Fleischman (jfly) | i don't think we'd want to forward all webhooks.
i do think that's something we (the infra team) should enable community members to do, though. do you know if this is a problem other communities have solved? | 15:30:06 |
 K900 | What exactly is the problem with "just ask the infra team" ? | 15:31:13 |
| Jeremy Fleischman (jfly) | i think that's fine. perhaps worth writing it down somewhere | 15:31:45 |
| Jeremy Fleischman (jfly) | i'm not sure if the infra team actually has the perms to do it | 15:31:59 |
| @adam:robins.wtf | I don't think they do. | 15:48:08 |
| @adam:robins.wtf | I think you need Owner(?) on the repo to add a webhook | 15:49:03 |
| hexa (signing key rotation when) | setting up webhooks on the org? we do not | 15:49:04 |
