| 3 Oct 2025 |
|  moleksiak joined the room. | 23:20:53 |
| 4 Oct 2025 |
|  aleksana 🏳️⚧️ (force me to bed after 18:00 UTC) changed their profile picture. | 08:40:51 |
| aleksana 🏳️⚧️ (force me to bed after 18:00 UTC) changed their profile picture. | 08:41:22 |
 hexa | https://github.com/NixOS/nixpkgs/pull/448680 | 23:40:31 |
| hexa | did the thing | 23:40:36 |
| hexa | hope auto updates will do the trick from here on out | 23:40:51 |
| 5 Oct 2025 |
 7c6f434c | Hello. For the context, EC agreed to recognise clicking emailed magic links as email confirmation, and this is what the subdomain requested in https://github.com/NixOS/infra/pull/862 would be used for | 07:42:15 |
| 7c6f434c | (To avoid being phishing-like…) | 07:42:58 |
| 7c6f434c | Is there advice on what delay between messages to use when sending the corresponding hundreds of emails (at least the PR-based registration cut the number by a third…)? | 07:45:41 |
 Vladimír Čunát | I agree that links to .top might appear suspicious. | 07:48:24 |
| Vladimír Čunát | I guess I'll cancel the trunk-combined eval. Lots of expensive jobs for Hydra (tests), and I hope we'd merge staging-next today. | 07:54:56 |
| Vladimír Čunát | (posted at #staging:nixos.org first where it's also relevant; I don't know who manually triggered the eval, otherwise I'd ask them) | 07:55:42 |
| 7c6f434c | Unknown .com or .me would also be suspicious, honestly | 07:57:11 |
| hexa | Mic92: looks like you set up a fastly service for a domain that you didn't set up yet 🙂 | 12:38:48 |
 Mic92 | @hexa:lossy.network: the wiki test domain, you | 14:35:40 |
| hexa | I know | 14:35:52 |
| Mic92 | Any issues with it? | 14:36:14 |
| Mic92 | Ah got the email | 14:36:32 |
| hexa | That 🙃 | 14:37:00 |
 Sandro | there is also this open PR from me from half a year ago https://github.com/NixOS/nixpkgs/pull/400448 | 14:53:00 |
| 6 Oct 2025 |
|  lovesegfault changed their profile picture. | 17:32:56 |
| lovesegfault changed their profile picture. | 17:33:43 |
| 7 Oct 2025 |
 djacu | Hey Infra Team
Would you be able to create an npmjs account? @avocadoom and I would like to have so we can publish branding assets and then use them with npm-like tooling. It would be more ergonomic if we had an npm/yarn dependency rather than trying to shim the branding assets into the homepage via Nix. We also are considering other teams might want access to this in the future so we are coming to you all.
Thanks! | 04:14:43 |
| Vladimír Čunát | If someone else understands this, no need for me to, but otherwise... it's like filling https://www.npmjs.com/signup with an @nixos.org e-mail and putting that into vault.nixos.org? | 06:19:19 |
| Mic92 | nixos already seems to be used as a name, we got nixos-marketing? | 08:13:24 |
 tgerbet | I have the control of the nixos and nixpkgs orgs on npmjs.com due to some security incident handling in the past (someone had reserved yarn2nix name which could have lead to some dependency confusion...)
I fine with adding members of a team to it and dropping my access afterwards | 09:46:56 |
| tgerbet | * I have the control of the nixos and nixpkgs orgs on npmjs.com due to some security incident handling in the past (someone had reserved yarn2nix name which could have lead to some dependency confusion...)
I'm fine with adding members of a team to it and dropping my access afterwards | 10:11:46 |
| hexa | djacu: What is the idea behind infra managing that account? | 11:42:38 |
| hexa | not that I'd be opposed, just wondering | 11:42:48 |
| djacu | In reply to @hexa:lossy.network
not that I'd be opposed, just wondering Honestly I don't know what the process is for creating accounts. I thought this was an Infrastructure Team responsibility since you all provided the Vault Warden account.
Could the Marketing Team create the account, add it to the vault, and if other teams need access in the future then it gets shared? | 15:38:41 |
