 | NixOS GSoC | 243 Members |
| 22 Servers |
| NixOS GSoC | 243 Members |
| 22 Servers |
| Sender | Message | Time |
|---|---|---|
| 20 Mar 2026 | ||
 LaLoutre joined the room. | 19:56:04 | |
| 21 Mar 2026 | ||
 Clumsily6239 | Yeah, that makes sense, especially around tracking patches that fix CVEs which aren’t explicitly referenced. I’ve been looking into extracting metadata from existing packages in nixpkgs (from URLs, comments, etc.). While that works to an extent, it clearly hits limits when the information isn’t present. Using Right now I'm trying to output a JSON file that downstream tools can use. Long term, however, standardizing patch metadata into nixpkgs itself would be ideal. | 04:32:57 |
 Tristan Ross | Yeah, I've written an SBOM generation tool at work and it works very well. It generates the CycloneDX vulnerabilities list and that seems to work well with grype. | 04:34:27 |
 AnnoyingRains joined the room. | 05:11:48 | |
| AnnoyingRains | Hey all, I'm interested in finding a mentor for reviewing nixpkgs PRs! As a note, I'm located in Australia, so finding someone near my timezone would be great! | 05:19:52 |
| AnnoyingRains | oh I think I am misunderstanding how this process works haha - first time doing gsoc | 05:22:54 |
 Mutsuha Asada | Hello, I'm Mutsuha Asada. I major in computer science at University of Tsukuba, and I've been using Nix and NixOS since three years and contributing to nixpkgs a little. Interested in the theme of "Testing Dynamic Derivation", I'm reading relevant pull requests and RFCs. | 05:27:05 |
| Mutsuha Asada | * Hello, I'm Mutsuha Asada. I major in computer science at University of Tsukuba, and I've been using Nix and NixOS for three years and contributing to nixpkgs a little. Interested in the theme of "Testing Dynamic Derivation", I'm reading relevant pull requests and RFCs. | 05:27:36 |
| AnnoyingRains | okay uh - take two: Hey all! I've been a nixos user for a couple years now, and have learnt the nix language fairly well in that time, and gotten used to the nix tooling. I love this project, and want to help give back to it! I've known about GSoC for a couple years now, but this will be my first time giving it a shot! I'm interested in helping out with the nixpkgs PR review queue! My current plan would be to start with reviewing PRs (with assistance from a mentor) and then, when I have a little more experience, moving on to onboarding new nixpkgs contributors / package maintainers. Please reach out if you're interesting in mentoring me for this - I'd love to help out the project that I gain so much from! | 06:07:49 |
| AnnoyingRains | I'd also like help in workshopping my proposal to be more interesting to Google | 06:08:20 |
 Srivatsa joined the room. | 10:31:41 | |
 Lisanna | Update on the remote building protocol refactor, after discussion with the Nix maintainers the project is being replaced with a tangential idea to extend stores and eliminate the build hook. See https://github.com/NixOS/GSoC/pull/45 | 14:47:55 |
| Srivatsa | Hi! just submitted my GSoC proposal for the Review Nixpkgs PRs project (350h). I've been using NixOS for about a year and have a couple of small contributions to nixpkgs and nix.dev. Would really appreciate connecting with a mentor and getting any feedback on my proposal. GitHub is github.com/Haschwalth00B | 16:12:43 |
 Daniel Lual Akoon joined the room. | 18:09:51 | |
| Daniel Lual Akoon | Hello everyone, My name is Daniel Lual from South Sudan but currently study in Indonesia doing a bachelor of Informatics Engineering in State University of Semarang. As the founder of Dann Foundation, I built a website where students from South Sudan have access to opportunities like scholarships but on the journey when I was building this website I have experience a lot of bugs and errors before my site was deployed. As a result of that, I debugged until my website was deployed online as per now. With due diligence, I am enthusiastically interested to work with NixOS in GSoC program. Get to expand my knowledge on how to be a best developer ever. this is the link of my website dannfoundation.net Thanks | 18:12:05 |
| LaLoutre | Hello everyone, My name is Bastien, and I’m very glad to meet you all. I am currently a French student at EPITA, in the major GISTRE (which focuses on low-level systems, operating systems, and systems programming). I also had the opportunity to contribute to an open source project during an internship last year, which was a small research project in the healthcare field. This gave me some initial experience with collaborative development. I have a few questions regarding GSoC, mainly to better understand my chances of being selected and how I can best prepare. I only discovered GSoC very recently (just yesterday, through my manager), so I haven’t had the opportunity yet to submit PRs or actively contribute to the NixOS project. However, I have been using NixOS for nearly four years now, and I’m involved in maintaining my school’s infrastructure with the intern team, which is fully based on NixOS. I’m genuinely motivated to start contributing to NixOS, and GSoC feels like a great opportunity for me to take that step and get more involved in the ecosystem. Could you please advise on what would be the best way for me to get started and improve my chances of being selected? Thank you very much for your time and guidance. | 18:28:45 |
| 22 Mar 2026 | ||
 Carter changed their profile picture. | 05:47:22 | |
 Olaleye Oyewunmi joined the room. | 16:15:15 | |
| Olaleye Oyewunmi | Hi everyone! I'm Olaleye, a DevOps engineer from Nigeria. I'm really interested in participating in GSoC 2026 with the NixOS Foundation! I've been into software development for about a whiles , and for the last 2 years, I've been working as a DevOps engineer focusing on cloud-native tech, Kubernetes, and infrastructure automation. I have also previously contributed to open-source projects like Envoy and kgateway. I've been using the Nix CLI for a while just for fun, and my background in infrastructure scaling has naturally drawn me to Nix's philosophy of declarative and reproducible builds. I am eager to start contributing here. Are there any specific areas around CI infrastructure or documentation that you'd recommend I look into for a good first issue? | 16:21:46 |
| Olaleye Oyewunmi | Hi Robert! I was just looking through the 2026 ideas list and the 'Migrate some NixOS modules to modular services' project caught my eye. Given my background managing systemd services and infrastructure configurations, this looks like a perfect match where I could hit the ground running. Is there a specific NixOS service or module implementation that you'd recommend I look at first to understand the current bottleneck and see what factoring it into a modular service would look like? | 16:30:26 |
 Ngozi joined the room. | 18:53:37 | |
| Ngozi changed their display name from Hannah to Ngozi. | 20:12:47 | |
| Ngozi | Hi NixOS team, I'm Ngozi, a Cloud Engineer and technical writer applying for GSoC 2026. I'm interested in the Improved Release Notes project. I'm still getting familiar with the Nix ecosystem, but the problem itself maps onto work I already do: I've been building documentation pipelines and working with docs-as-code tooling professionally, and the changelog fragment pattern (one file per entry, assembled at release time) is something I've seen solve exactly this class of merge conflict and structure problem in other projects. I've started reading through the Home Manager news module to understand the prior art and I'm working through the current nixpkgs release notes workflow to understand where the friction is. A few questions as I get oriented:
Happy to share early proposal drafts for feedback once I've done more groundwork. Ngozi | 20:51:50 |
| Ngozi | * Hi NixOS team, I'm Ngozi, a Cloud Engineer and technical writer applying for GSoC 2026. I'm interested in the Improved Release Notes project. I'm still getting familiar with the Nix ecosystem, but the problem itself maps onto work I already do: I've been building documentation pipelines and working with docs-as-code tooling professionally, and the changelog fragment pattern (one file per entry, assembled at release time) is something I've seen solve exactly this class of merge conflict and structure problem in other projects. I've started reading through the Home Manager news module to understand the prior art and I'm working through the current nixpkgs release notes workflow to understand where the friction is. A few questions as I get oriented:
Happy to share early proposal drafts for feedback once I've done more groundwork. | 20:52:03 |
 @mdaniels5757:matrix.org left the room. | 22:17:34 | |
 ruchit joined the room. | 23:08:36 | |
 Robert Hensing (roberth) | I don't know anyone by that handle. Are they an active contributor to Nixpkgs? | 23:10:10 |
| 23 Mar 2026 | ||
 Allan Dinakaran | Hi everyone , I reviewed PR #502399 (gemini-cli-bin update). Tested on x86_64-linux:
Observed a minor runtime warning due to missing ~/.gemini directory (resolved by creating it, likely upstream behavior) This is one of my first nixpkgs reviews and I've recently started using Nix, so I would really appreciate any feedback or suggestions. Thanks! | 05:58:33 |
 Swaraj | Hi Robert! raf mentioned they were a previous release editor for Nixpkgs. Here is their Matrix handle: @raf:notashelf.dev | 06:28:30 |
 Suryakant Subudhi joined the room. | 07:41:54 | |