| 17 Sep 2023 |
 Guillaume Desforges | feedback is very welcome and will be noted down for next year | 14:45:19 |
 garbas | IdaBzo: we need to schedule above discourse post in buffer. | 16:42:19 |
|  0xMRTT [envs.net] changed their display name from 0xMRTT (Old) to 0xMRTT [envs.net]. | 16:58:52 |
| 19 Sep 2023 |
| garbas | jonge: avocadoom: sorry for late work, but after Thursday I got some family matters to attend. I finally post the github issue I promised: https://github.com/NixOS/nixos-homepage/issues/1125 | 08:25:35 |
| garbas | I | 08:25:40 |
| garbas | * I'll review the PR that is open and fix the CI so we are having a preview of our work somewhere. | 08:26:19 |
| garbas | I've also just merged origin/master to main I'll try to do this once a week or we can do it when we need it. | 08:38:30 |
| garbas | https://github.com/NixOS/nixos-homepage/pull/1126
This should fix the CI | 09:43:15 |
| garbas | (on main branch, since on master is working as before) | 09:43:33 |
| garbas | jonge: I was thinking how to handle SVG that you've added in the PR. You think we could create a custom local icon pack as described in https://github.com/natemoo-re/astro-icon/tree/main#local-icons? Or maybe this is premature optimisation and we should fix this later once we have few SVGs | 10:18:06 |
 jonge | before knowing how and where this is used other than at this spot, this idea indeed smells a little bit like premature optimization. | 11:02:31 |
| jonge | but being the marketing team, we could upstream the logo anyway... | 11:12:09 |
 avocadoom | In the Header I started just importing the SVG as an Image. Maybe not the most optimized way, but works the best regarding quick changes. | 11:24:32 |
| avocadoom | I agree woth jonge, this can be done when the base has gotten more mature | 11:25:28 |
 Jonas Chevalier | just noticed today: we have https://mobile.nixos.org but no Mobile team in the teams page | 17:05:57 |
 @kranzes:matrix.org | It's just Samuel I think | 17:23:48 |
| 20 Sep 2023 |
|  nbathum (he or they) changed their display name from nbathum (he or they) to nbathum. | 04:58:33 |
| nbathum (he or they) removed their profile picture. | 04:58:42 |
|  philippe joined the room. | 10:15:14 |
| garbas | Jonas Chevalier: yes, this is samueldr's team. I'm not sure who is part of it. | 19:55:54 |
| garbas | jonge: avocadoom: (or anybody else) I'll be hacking on the website and hanging around here (https://meet.jit.si/ToyInjusticesProhibitTerribly) if somebody want to join.
also if you're online can you review -> https://github.com/NixOS/nixos-homepage/pull/1126
| 19:57:52 |
|  Hubble the Wolverine (they/them) joined the room. | 22:16:23 |
| 21 Sep 2023 |
 Pol | I hope this is the appropriate channel for my request.
I am currently working on writing a document aimed at introducing the concept of "reproducibility" in software development within the European Commission. The ultimate goal of this document is to advocate for the authorization and official recognition of Nix as a tool at the EC.
Would you happen to have any existing materials that could assist me in this endeavor, such as presentations or PDFs? | 08:48:51 |
|  Matthias Meschede joined the room. | 09:33:34 |
| Matthias Meschede | Pol: just some that come to mind immediately. For research there is a presentation here (maybe you saw it) https://toot.aquilenet.fr/@civodul/111097781066920677 . Konrad Hinsen and Nicolas Rougier, who you may know, have lots of other articles about this subject and also some nice references such as a Nature paper. They are more active in the Guix world if but maybe that doesn't hurt.
Andreas from our Scalable Builds Group just gave a talk about the role of build systems that touches reproducibility as well. https://media.ccc.de/v/all-systems-go-2023-219-fast-correct-reproducible-builds-with-nix-bazel#t=1288 .
"The motivation behind the Reproducible Builds project is therefore to allow verification that no vulnerabilities or backdoors have been introduced during this compilation process. By promising identical results are always generated from a given source, this allows multiple third parties to come to a consensus on a “correct” result, highlighting any deviations as suspect and worthy of scrutiny." This has been cited from https://reproducible-builds.org/ . Nix has the Trustix project around this idea and jfrog this one: https://pyrsia.io/ .
I have a whole long list of references about reproducibility from an old grant consortium somewhere. If it's really required I can try digging it up.
| 09:41:51 |
| Pol | Nice ! Thanks I will check everything out. Regarding the definition of reproducible build, I already have this in my document: | 09:43:00 |
| Pol | 
Download image.png | 09:43:04 |
| Matthias Meschede | Nice. I would try to hammer out that eproducibility greatly enhances:
- collaboration and code sharing
- speed and quality of development
- trust in the security of your binaries and all of their dependencies (supply chain attacks).
| 09:47:35 |
| Matthias Meschede | * Nice. I would try to hammer out that reproducibility greatly enhances:
- collaboration and code sharing
- speed and quality of development
- trust in the security of your binaries and all of their dependencies (supply chain attacks).
| 09:47:45 |
| Pol | It's done already somewhere else :D | 09:48:10 |
