| 30 Mar 2026 |
|  Saaid joined the room. | 12:26:48 |
| Saaid | /join #gsoc:nixos.org | 12:27:42 |
|  Madhur Chandran joined the room. | 16:31:10 |
|  RITISH DAS joined the room. | 17:11:50 |
 Allan Dinakaran | Hey, I've submitted my Gsoc 2026 proposal for the Nixpkgs PR review project.
I've been working on reviewing PRs and testing packages and I'll continue improving my workflow and contribution.
Feedbacks are always welcome. Thanks!!
| 20:50:09 |
| 31 Mar 2026 |
|  Nhat Minh Pham joined the room. | 04:03:03 |
|  @rohitth:matrix.org joined the room. | 08:52:33 |
| @rohitth:matrix.org left the room. | 09:04:57 |
 Jacobus Burger | I don't know who to tell this to | 09:22:05 |
| Jacobus Burger | But the NixOS GSoC has a typo in the Topics of its page | 09:22:23 |
| Jacobus Burger | InfrastrucutreAsCode should be InfrastructureAsCode | 09:23:05 |
| Jacobus Burger | Alright! I submitted my GSoC application for the Nixpkgs PR review project! | 10:47:48 |
|  Sanskar joined the room. | 13:04:49 |
|  Roshni Singh joined the room. | 14:00:31 |
 Yyovil | What if the selected project size is not enough to implement the proposed solution? My solution contains coordination with other NixOS members(not my mentors) + contributors to get couple of PRs merged first of all before I could even start contributing, and It(time to get merged) could vary for many reasons.
Robert Hensing (roberth)
| 14:34:24 |
 K900 | What is the project, exactly? | 14:36:51 |
| Yyovil | SBOMs (the proposed idea) | 14:37:36 |
| Yyovil | * What if the proposed idea size is not enough to implement the proposed solution? My solution contains coordination with other NixOS members(not my mentors) + contributors to get couple of PRs merged first of all before I could even start contributing, and It(time to get merged) could vary for many reasons.
Robert Hensing (roberth)
| 14:37:48 |
 Robert Hensing (roberth) | Yyovil : the size of the effort can be adjusted with your mentor | 15:02:03 |
|  Kwinsi Thakkar joined the room. | 16:34:17 |
| Yyovil | ADHD people? Anyone? | 19:06:50 |
| Jacobus Burger | huh? | 23:51:57 |
| 2 Apr 2026 |
| Sanskar set a profile picture. | 08:03:07 |
| Sanskar | Hey @roberth (and anyone else around), I'm looking into the Modular Services GSoC project and had a quick architecture question.
Since the project description explicitly requires keeping the user-facing options of the NixOS module the same, I’m curious about the intended migration strategy. Is the plan to manually wire up the legacy global options to the new modular backend for each service one-by-one? Or is the goal to build a standardized abstraction (like a mkModularService wrapper) that automatically bridges the legacy options to the new modular instances? | 10:20:41 |
| Sanskar | * Hey @roberthensing:matrix.org (and anyone else around), I'm looking into the Modular Services GSoC project and had a quick architecture question.
Since the project description explicitly requires keeping the user-facing options of the NixOS module the same, I’m curious about the intended migration strategy. Is the plan to manually wire up the legacy global options to the new modular backend for each service one-by-one? Or is the goal to build a standardized abstraction (like a mkModularService wrapper) that automatically bridges the legacy options to the new modular instances? | 10:21:35 |
| Sanskar | * Hey @roberthensing (and anyone else around), I'm looking into the Modular Services GSoC project and had a quick architecture question.
Since the project description explicitly requires keeping the user-facing options of the NixOS module the same, I’m curious about the intended migration strategy. Is the plan to manually wire up the legacy global options to the new modular backend for each service one-by-one? Or is the goal to build a standardized abstraction (like a mkModularService wrapper) that automatically bridges the legacy options to the new modular instances? | 10:22:03 |
|  @clay53:claytonhickey.me left the room. | 15:22:55 |
| Sanskar | * Hey @roberthensing:matrix.org (and anyone else around), I'm looking into the Modular Services GSoC project and had a quick architecture question.
Since the project description explicitly requires keeping the user-facing options of the NixOS module the same, I’m curious about the intended migration strategy. Is the plan to manually wire up the legacy global options to the new modular backend for each service one-by-one? Or is the goal to build a standardized abstraction (like a mkModularService wrapper) that automatically bridges the legacy options to the new modular instances? | 15:45:50 |
| Robert Hensing (roberth) | manual wiring at first to minimize impact on users as modular services gains traction | 18:27:52 |
| 5 Apr 2026 |
|  ritiek changed their profile picture. | 01:18:08 |
