How to start contributions to Summer of Nix

Hi everyone.
My name is Arsh Pratap,
I had contributed a lot towards the Software Discovery Tool (by Open Mainframe Project) and thats how I was introduced towards the world of software package-managers and also came across the Nix Community. I am a beginner at using Nix package manager (very recently started using it) and the NixOS, and
came across the Summer of Nix program conducted by the community. I was wondering about how I can start my journey towards contributing to Nix and how I can create a successful proposal.
I also wanted to know are they communication channels where I can discuss about any ideas/queries with members of the Nix community (potential mentors).

As mentioned above as well, I have had tons of experience contributing towards open source projects and have worked extensively with similar programs/internships like GSoC and LFX.

Looking forward to connecting and contributing towards the Nix project.
Thanks

2 Likes

Hi Arsh, thanks for reaching out! You can find up to date information on Summer of Nix here:

We’re planning to narrow down this year’s timeline around February 2025, and the idea is to open applications around April and have the contribution period somewhere between June and September.

For any detail questions you can contact me here via direct messages or on Matrix. For technical discussion related to developing the NGIpkgs monorepo, there’s a public Matrix room.

For initial orientation, please refer to the contributing guide on nix.dev. To make meaningful contributions, you should be somewhat proficient with basic concepts and workflows, which are outlined in the beginner tutorial series. The most important aspects are the Nix language, the various Nixpkgs mechanisms for constructing derivations to build software, and the module system.

Please note that for Summer of Nix our primary goal is packaging lots of software from a pool of projects funded through NGI. A good way to get one’s hands dirty with our slightly special environment is to add examples and tests for NixOS services where they’re still missing (check the sources code for each project).

And generally, a good way to make oneself visible and build up credibility in an open source software community is figuring out where one can add value with the least amount of effort for everyone involved. From experience, often it’s enough to try whether the software indeed does what documentation advertises, and then open pull requests to fix inconsistencies or make clarifications, one at a time.

Hope this helps, and hope to see you around!

Best

Valentin

3 Likes