| 28 Jan 2025 |
 K900 | No | 15:50:04 |
 Sami Liedes | Ok. | 15:50:15 |
| K900 | It's evaluating snapshots of master on a fixed timer | 15:50:23 |
| Sami Liedes | That didn't sound like it should work at Nix scale :) | 15:50:24 |
| K900 | It could have, if we had incremental evaluation | 15:50:35 |
| K900 | Which I think is something that has been brought up before on the Lix side | 15:50:46 |
| K900 | But that's a whole other can of worms | 15:50:52 |
| Sami Liedes | Yeah... I think a lot of things that are less than perfect in the Nix world seem to come down to having a better Nix or tooling around it. | 15:51:21 |
 dgrig | Hello! The Nix@NGI team would like to send some emails from a @nixos.org address in the near future. Based on https://github.com/NixOS/infra/pull/511 and https://github.com/NixOS/infra/issues/485 I understand we don't have this capability currently. Am I missing something or is this the case?
If it's the latter, what are our options here? Can I help somehow (with code reviews or writing code) to move this forward or is the best course of action to wait for the mentioned ETA in #410 and send emails from a non-nixos.org address until then?
| 16:51:14 |
 Winter | that’s possible - i was talking to valentin about this just a few minutes ago | 16:53:11 |
 fricklerhandwerk | To be clear, we need two independent things:
- team members receiving emails over a nixos.org address
- reliably mailing to numerous contacts from the nixos.org address
| 17:08:17 |
| fricklerhandwerk | * To be clear, we need two independent things:
- team members receiving emails over a nixos.org address (ideally somewhat easy to keep up to date who's in the recipient list)
- reliably mailing to numerous contacts from the nixos.org address
| 17:08:40 |
| fricklerhandwerk | * To be clear, we need two independent things:
- team members receiving emails over a nixos.org address (should be somewhat easy to keep up to date who's in the recipient list, ideally eventually auto-synced with whatever mechanism is available for managing teams)
- reliably mailing to numerous contacts from the nixos.org address
| 17:09:11 |
| fricklerhandwerk | * To be clear, we need two independent things:
- team members receiving emails to a team's nixos.org address (should be somewhat easy to keep up to date who's in the recipient list, ideally eventually auto-synced with whatever mechanism is available for managing teams)
- reliably mailing to numerous contacts from the nixos.org address
| 17:09:24 |
 Artturin | Can someone bump
https://hydra.nixos.org/build/287227270
https://hydra.nixos.org/build/287219458
https://hydra.nixos.org/build/287218582
https://hydra.nixos.org/build/287220720
After they're built nixos-unstable will advance | 21:49:34 |
 hexa | done | 21:50:27 |
| Artturin | Thanks | 21:54:43 |
| Artturin | Welp I was looking at the wrong place (status of tested) instead of queued jobs of trunk-combined, will be a while before the channel advances 11387. | 22:02:45 |
| Artturin | restarted the acme test 5 times to get it to succeed | 22:03:47 |
 Jeremy Fleischman (jfly) | dgrig, you've correctly identified the state of things. The summary at the top of https://github.com/NixOS/infra/issues/485 is accurate. We need to set up some alerts for the mailserver. I just haven't taken the time to familiarize myself with prometheus and the blackbox alerting we have set up on pluto. I don't think there's a lot of work remaining there.
Here's an idea that feels low risk: we could set up this new mailserver to send emails alongside our existing improvmx account. That would let us start to test out this arrangment without breaking any existing send accounts.
| 23:26:19 |
| Jeremy Fleischman (jfly) | For receiving, we have to either:
- complete the rollout
- OR, use improvmx to set up additional mailing lists
Do you have a sense of the timeline you're working on here?
| 23:27:10 |
| Jeremy Fleischman (jfly) |
team members receiving emails to a team's nixos.org address (should be somewhat easy to keep up to date who's in the recipient list, ideally eventually auto-synced with whatever mechanism is available for managing teams)
This is news to me. Is this github teams? Or something TBD that'll be used for sign-on to our new grist service?
| 23:28:40 |
| Winter | improvmx can send emails already | 23:28:41 |
| Jeremy Fleischman (jfly) | yes, that's also definitely an option. i was just thinking this could be a nice, low-risk opportunity to test out the new mailservef | 23:29:05 |
| Jeremy Fleischman (jfly) | * yes, that's also definitely an option. i was just thinking this could be a nice, low-risk opportunity to test out the new mailserver | 23:29:06 |
| Winter | “reliable delivery” != “low-risk” ;) | 23:29:17 |
| Winter | * | 23:29:49 |
| Winter | In reply to @jfly:matrix.org
team members receiving emails to a team's nixos.org address (should be somewhat easy to keep up to date who's in the recipient list, ideally eventually auto-synced with whatever mechanism is available for managing teams)
This is news to me. Is this github teams? Or something TBD that'll be used for sign-on to our new grist service?
he means github teams || whatever alternate mechanism exists, if any, which i’m pretty sure the answer is “no” to | 23:30:04 |
| Jeremy Fleischman (jfly) | Sure, I just mean it would be nice to test with 1 brand new send address rather than all of them. But totally acknowledge there's risk here, and an annoyingly hard one to anticipate ahead of time. | 23:30:44 |
| dgrig | I don't have an exact timeline, but I think it would be around sometime next week.
If improvmx can send emails then it's good enough for this usecase now I think and there's no need to worry about potential issues with the new setup.
| 23:37:21 |
