NixOS GSoC | 243 Members | |
| 22 Servers |
| Sender | Message | Time |
|---|---|---|
| 3 Mar 2026 | ||
| 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 | ||
| 8 Mar 2026 | ||
| 02:24:09 | ||
| 02:34:46 | ||
| 14:03:44 | ||
| A lot of students this year. Great to see.🤝 | 19:01:22 | |
| 23:32:01 | ||
| 9 Mar 2026 | ||
| 05:34:21 | ||
| 10 Mar 2026 | ||
| 04:50:47 | ||
| 11:06:30 | ||
| 11:08:10 | ||
| Hi! My name's Raf, and I'm currently studying for a masters in mathematics. I've been using Nix to manage my devices (laptops and self hosted infrastructure) for the past 5-6 years. I just came across the Discourse post about GSOC, and skimmed through the proposals. My attention was initially grabbed by the modular service project, although it seems other people have already talked about it / concerns have been raised a few messages above, so I'll see what else sounds interesting. | 11:22:21 | |
| 12:36:29 | ||