NixOS GSoC | 243 Members | |
| 22 Servers |
| Sender | Message | Time |
|---|---|---|
| 2 Mar 2026 | ||
| 17:34:54 | ||
| Hi everyone! I’m Nikita, a CS student with an interest in K8s/Docker and declarative infrastructure. I’ve recently started contributing to nixpkgs (PR #495749) and I'm looking into the Modular Services Migration project I’ve been diving into the Netdata module to see how it might fit the _class = "service" pattern. I hit a snag: Netdata uses security.wrappers and capabilities which seem to be global settings in NixOS. If we want to run multiple instances of a service, won't these wrappers conflict? Has anyone figured out a way to handle SUID wrappers for modular services yet, or is that still an open problem? @roberth: I’m curious if there’s a preferred pattern for this, or if high-privilege services are still a work-in-progress for the modular migration? | 17:41:31 | |
| Please do not look at the modular services project for now | 17:49:11 | |
| There have been concerns raised with it internally | 17:49:20 | |
| Understood, thanks for the heads-up @k900. I'll pivot my focus. Is there another area or a specific set of modules that the team is prioritizing for refactoring or migration right now? I'm still very interested in contributing to the NixOS service architecture. | 17:51:27 | |
| No, the question is generally whether modular services are even something we want | 17:54:37 | |
| oh okay, I'll stick to the current architecture | 18:01:09 | |
| 18:26:39 | ||
| 20:39:58 | ||
| K900: The idea was originally written in an overly optimistic way and I've updated it last Wednesday night. Please re-read if you haven't already. Progress on this project is meant to help us make an informed decision about broader adoption instead of going off vibes. | 21:09:53 | |
| 3 Mar 2026 | ||
| Hey everyone, my idea for a NixOS runtime drift detector and reconciler got accepted into the GSoC ideas list. Built a small prototype CLI that compares declared NixOS config against live system state, starting with services. Tested on a real NixOS 24.11 VM. Repo: https://github.com/ArkhamKnight25/nixos-drift-detector Open to feedback, and excited to connect with anyone interested in reviewing or mentoring this. | 08:57:34 | |
| 22:12:53 | ||
| 4 Mar 2026 | ||
| 06:10:38 | ||
| Hi!, I am Mayank using Nix Package manager on top of Ubuntu/Fedora and NixOS on my old machines for like 3 years now. I did like to participating in reviewing Nixpkgs PR as part of GSoC. Would love to connect with a mentor and any direction how can I work further on this. | 08:11:25 | |
| * Hi!, I am Mayank using Nix Package manager on top of Ubuntu/Fedora and NixOS on my old machines for like 3 years now. I did like to participate in reviewing Nixpkgs PR as part of GSoC. Would love to connect with a mentor and any direction how can I work further on this. | 08:11:42 | |
| * Hi!, I am Mayank using Nix Package manager on top of Ubuntu/Fedora and NixOS on my old machines for like 3 years now. I did like to participate in reviewing Nixpkgs PR as part of GSoC. Would love to connect with mentors and any directions on how can I work further on this. Thanks | 08:19:58 | |
| * Hi!, I am Mayank using Nix Package manager on top of Ubuntu/Fedora and NixOS on my old machines for like 3 years now. I did like to participate in reviewing Nixpkgs PR as part of GSoC. Would love to connect with mentors. | 08:20:07 | |
| * Hi!, I am Mayank using Nix Package manager on top of Ubuntu/Fedora and NixOS on my old machines for like 3 years now. I'd like to participate in reviewing Nixpkgs PR as part of GSoC. Would love to connect with mentors. | 09:37:54 | |
| 11:14:16 | ||
| 19:05:23 | ||
| 5 Mar 2026 | ||
| 00:59:47 | ||
| 06:21:51 | ||
| Hi everyone, Re=introducing myself I'm Bhuvan, a developer who's been contributing to the Nix Security Tracker over the past few months working on things like batching activity log queries, structured rejection reasons, the CVE deduplication migration, and a few bug fixes along the way. I'm planning to apply for GSoC 2026 with a focus on improving the tracker particularly around matching quality (version constraint evaluation) and data storage efficiency. I've been going through the codebase and open issues to get a better feel for where I can add the most value. I'd love to connect with @fricklerhandwerk if possible would really appreciate any guidance on shaping the proposal in the right direction. Happy to share what I have in mind :) | 13:44:42 | |
| * Hi everyone, Re=introducing myself I'm Bhuvan, a developer who's been contributing to the Nix Security Tracker over the past few months working on things like batching activity log queries, structured rejection reasons, the CVE deduplication migration, and a few bug fixes along the way. I'm planning to apply for GSoC 2026 with a focus on improving the tracker particularly around matching quality (version constraint evaluation) and data storage efficiency. I've been going through the codebase and open issues to get a better feel for where I can add the most value. I'd love to connect with @fricklerhandwerk if possible would really appreciate any guidance on shaping the proposal in the right direction. Happy to share what I have in mind :) | 13:44:59 | |
| * Hi everyone, Re=introducing myself I'm Bhuvan, a developer who's been contributing to the Nix Security Tracker over the past few months working on things like batching activity log queries, structured rejection reasons, the CVE deduplication migration, and a few bug fixes along the way.I'm planning to apply for GSoC 2026 with a focus on improving the tracker particularly around matching quality (version constraint evaluation) and data storage efficiency. I've been going through the codebase and open issues to get a better feel for where I can add the most value. I'd love to connect with @fricklerhandwerk if possible would really appreciate any guidance on shaping the proposal in the right direction. Happy to share what I have in mind :) | 13:45:24 | |
| * Hi everyone, Re=introducing myself I'm Bhuvan, a developer who's been contributing to the Nix Security Tracker over the past few days working on things like batching activity log queries, structured rejection reasons, the CVE deduplication migration, and a few bug fixes along the way.I'm planning to apply for GSoC 2026 with a focus on improving the tracker particularly around matching quality (version constraint evaluation) and data storage efficiency. I've been going through the codebase and open issues to get a better feel for where I can add the most value. I'd love to connect with @fricklerhandwerk if possible would really appreciate any guidance on shaping the proposal in the right direction. Happy to share what I have in mind :) | 14:26:58 | |
| 22:12:57 | ||
| 6 Mar 2026 | ||
| 16:12:32 | ||
| 16:27:24 | ||
| 16:44:18 | ||