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:

• Are there open issues or discussions I should read before reaching out to a potential mentor?
• Would small contributions (docs fixes, exploring the current release note structure) be a useful way to demonstrate fit before the proposal deadline?

Happy to share early proposal drafts for feedback once I've done more groundwork.

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:

• Are there open issues or discussions I should read before reaching out to a potential mentor?
• Would small contributions (docs fixes, exploring the current release note structure) be a useful way to demonstrate fit before the proposal deadline?

Happy to share early proposal drafts for feedback once I've done more groundwork.

Hi everyone , I reviewed PR #502399 (gemini-cli-bin update).

Tested on x86_64-linux:

• Initially tried using nixpkgs-review, but the full build caused high resource usage and made my system unresponsive
• Then tested using nix build on the specific package
• Build succeeded and the CLI runs correctly

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!

iirc
He's the creator of

1. nh(nix helper) ❤️
2. nvf - neovim framework 🔥

Hello!

My name is Clayton. I'm a junior in Computer Engineering at the University of Pennsylvania. I've been daily driving NixOS since I think sophomore year of high school. I've just found out that Summer of Code applications have started, so I'm sorry if I'm late.

I've been wanting multiple instance support for my own servers, so I think Migrate some NixOS modules to modular services sounds interesting.

I've started running some services that I trust less in Docker and trying to wrap some programs in Bubblewrap, but Provide support for Mandatory Access Control sounds like a better solution, so I'd like to work on it.

Greater usage of updateScript throughout Nixpkgs sounds like a good way to decrease the load on maintainers and seems easy to approach, so working on that sounds good.

Outside of the listed projects, I've been interested in getting my Pinephone Pro to work nicely with NixOS, especially because of recent threats from Google to lock down Android more. I know there is Mobile NixOS, but as far as I can tell, Pinephone Pro support has been borked for a long time, or at least, to get it working on a new version of Mobile NixOS/Nixpkgs is a lot work and undocumented (the installer hasn't worked for a long time). I think it's also no longer officially part of the NixOS project. I would like to help make its support simpler. I haven't gotten it to complie yet (only tried it once over spring break tbc), but I believe Megi's Kernel fork (which I think could be added to nixpkgs, similar to the RPI kernel) combined with the new standard "loader?", rk2aw, would make it so there doesn't have to be anything too special about creating a working NixOS configuration for it (other than enabling drivers). I'm not really familiar with the NixOS on ARM project, but I imagine it would fit into there. I know there aren't that many people using Pinephone Pros out there, and I would be cool to work on a different device if I could get one, but I think there would be benefits to building out a device as an example to others and just getting more users to make sure mobile services are working (like Phosh).

I'm not sure what I should do next, but I assume that's the point of this channel lol. In general, I'd be happy to work on NixOS through Summer of Code so I don't have to get an internship and can work on making NixOS better.