| 23 May 2025 |
 avocadoom | Hmm, I dont know what @djacu:matrix.org: s plans are for filepath stability tbh. | 21:22:50 |
 djacu | Whatever fixes the issue is fine for now. But this does give me something to think about.
The branding repo will have no logo files committed; everything is built from source. However, there will be releases. Using releases/latest vs releases/<version> is an interesting question.
| 21:46:25 |
| avocadoom | Whata about deploying the files to something like artwork.nixos.org? | 21:54:59 |
| djacu | Yeah this is the right solution. Duh 🤦 | 21:56:20 |
| avocadoom | This could be used in a similar style to a cdn | 21:58:09 |
| djacu | I was planning on having a media kit page anyway. With all the external logos and instructions. | 21:58:10 |
 SigmaSquadron | So, for now, do we revert to nixos-artwork or upload to nixos.org again? | 22:00:14 |
| SigmaSquadron | (since the artwork subdomain and the branding repo is a long-term solution) | 22:00:56 |
| djacu | I wouldn't rely on nixos.org being stable even short term. We are discussing changes to the website that could land before I finish branding v0. I would consider nixos-artwork more stable. | 22:02:08 |
 das-g | Reverting nixos-artwork to what? It's a change on nixos.org that broke the Nixpkgs README. | 22:02:10 |
| das-g | Oh, sorry, didn't see the "to". | 22:02:36 |
| das-g | * Oh, sorry, didn't see the "to" in "revert to nixos-artwork" | 22:03:25 |
| das-g | * Reverting nixos-artwork to what? It's a change on nixos.org that broke the Nixpkgs README. | 22:03:39 |
| djacu | * I wouldn't rely on nixos.org being stable in the short term. We are discussing changes to the website that could land before I finish branding v0. I would consider nixos-artwork more stable. | 22:06:48 |
 Sigmanificient | well waiting a bit, to see if someone yells to not merge the hotfix 👀 | 22:07:30 |
| 25 May 2025 |
 infinisil | NixCon ticket sales are open! https://discourse.nixos.org/t/ticket-sales-started-for-nixcon-2025/64756 | 15:33:25 |
| 26 May 2025 |
|  @federicodschonborn:matrix.org changed their display name from This LEGO® Worm™ is licensed under the terms of the he/him or they/them pronouns, at your choice to LEGO® Worm™ (Asbestos Flavored!). | 13:15:22 |
| 27 May 2025 |
| @federicodschonborn:matrix.org changed their display name from LEGO® Worm™ (Asbestos Flavored!) to LEGO® Worm™ (Now Only 1 krad!). | 14:45:43 |
|  @deeok:matrix.org joined the room. | 15:24:41 |
| 29 May 2025 |
|  @lennart:0520.ch joined the room. | 04:47:29 |
| @lennart:0520.ch | hej you all, thilobillerbeck (avocadoom) you merged a NixCon ticket sale announcement as the top banner on nixos.org two days after the 25.05 release announcement. I noticed because I had trouble finding the release notes. I guess few people know that you need to click "Blog", on the entry, etc. (as a helping hand at NixCon) I do understand the importance of selling tickets. but just two days for the release announcement is a bit troublesome because users might miss it (especially regarding our brief EOL timeframe). also as a release manager I would feel kinda disrespected. could we discuss possible solutions to this problem? https://github.com/NixOS/nixos-homepage/commit/95a7c1f2e0588cb2b2fe9bf877dea585031d1b3a | 04:50:47 |
| @lennart:0520.ch | * hej you all, thilobillerbeck (avocadoom) you merged a NixCon ticket sale announcement as the top banner on nixos.org two days after the 25.05 release announcement. I noticed because I had trouble finding the release notes. I guess few people know that you need to click "Blog", on the entry, etc. (as a helping hand at NixCon) I do understand the importance of selling tickets. but just two days for the release announcement is a bit troublesome because users might miss it (especially regarding our brief EOL timeframe). if I were a release manager I would feel kinda disrespected. could we discuss possible solutions to this problem? https://github.com/NixOS/nixos-homepage/commit/95a7c1f2e0588cb2b2fe9bf877dea585031d1b3a | 04:51:13 |
| @lennart:0520.ch | cc IdaBzo | 08:27:23 |
| @lennart:0520.ch | I'd propose working on multiple banners at the same time, if wanted and possible :) | 08:33:47 |
| avocadoom | In reply to @lennart:0520.ch
I'd propose working on multiple banners at the same time, if wanted and possible :) We need to find another solution for that. Having multiple banners will create a horrible UI and UX since it'll result in a lot of noise. | 09:40:59 |
| avocadoom | Banners are there to grab attention on their own. With every new one, the effect will be drastically reduced and just create a stack of mess and noise for the end user. | 09:42:51 |
| avocadoom | If you don't feel the need for the banner to be there I can take it down. | 09:43:42 |
| avocadoom | I'll just remove it for now | 09:45:27 |
| avocadoom | But in general communicating more clearly what is the current release and when the last release will be EOLed without a banner is something we can think about | 09:53:27 |
| avocadoom | Out of curiosity, can we infer the EOL date and the date of the current NixOS release from the current NixOS release nixpkgs? | 10:02:13 |
