| 26 Sep 2025 |
 Taeer Bar-Yam | Ah, thanks for the tip! I'll try to look into it soon. Though I'm kind of wary of stuff that is automagical with my git history 😅 | 20:09:03 |
 magic_rb | It says it will only create fixup commits by default so you can review them | 20:10:29 |
| Taeer Bar-Yam | oh i see. that's much better | 20:10:55 |
| 27 Sep 2025 |
|  @meltymeli:catgirl.cloud joined the room. | 10:59:50 |
| @meltymeli:catgirl.cloud | Hi. I'm on Void Linux. I really like how Nix handles configuration, but am worried I have to hop to get the full experience. Is this the case? | 11:01:25 |
 K900 | The full experience being full system config, yes | 11:04:53 |
| K900 | Also wrong room kinda | 11:04:57 |
| K900 | You probably want #users:nixos.org | 11:05:05 |
| @meltymeli:catgirl.cloud | Thank you. Yes meaning I have to hop? | 11:06:22 |
| K900 | Yes meaning you have to run NixOS | 11:06:41 |
|  volth joined the room. | 18:40:20 |
 John Ericson | https://github.com/NixOS/nix/pull/14063 is ready for review | 19:13:31 |
| John Ericson | fixed the GCC only issues | 19:13:36 |
| John Ericson | Sergei Zimmerman (xokdvium): so it occured ot me that we can (de)serialize entire dummy stores to JSON | 21:10:36 |
| John Ericson | and this is, naturally, the grand culmination of my JSON issue | 21:10:53 |
| John Ericson | :) | 21:10:54 |
| 28 Sep 2025 |
| John Ericson | Martin Schwaighofer: https://github.com/NixOS/nix/pull/13942 JSON for the entire dummy store | 06:59:02 |
| John Ericson | this will hopefully allow us to unit the the substitutor | 06:59:21 |
| John Ericson | * this will hopefully allow us to unit the the real substitutor | 06:59:29 |
| John Ericson | and show how "build" (mocked up insertions) caching works | 06:59:44 |
| @meltymeli:catgirl.cloud left the room. | 09:54:14 |
|  stratospher joined the room. | 17:20:18 |
|  bit-aloo joined the room. | 17:21:20 |
| bit-aloo | Hey everyone! Hope this is the right channel for asking. I've been using nix at work and understand its basics. I would love to dive deeper and contribute meaningfully to the project. It would be awesome if someone could guide me in which direction or resources to look for. | 17:27:51 |
 WeetHet | If you want to contribute to nix the package manager (which I'm really not sure you want to if you only understand the basics), you can look at the contributing guide here:
https://github.com/NixOS/nix/blob/master/CONTRIBUTING.md
If you don't want to work with the (not so great) C++ code of nix the package manager you can go and contribute to nixpkgs:
https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md
You can help with fixing reproducibility of a package, add a new one, write a nixos module for a missing program/service or work on more fundamental stuff like the stdenv or any of the language ecosystems. Personally, these two are interesting for me, but you might wanna search yourself:
https://github.com/NixOS/nixpkgs/issues/334195
https://github.com/NixOS/nixpkgs/issues/333702
If you don't want to write nix either, there are outside issues like
https://github.com/NixOS/nixpkgs/issues/424345
decentralized binary caching, etc
You can also help around on discourse or in #users:nixos.org
| 17:54:04 |
| WeetHet | There's also a ton of community projects you can contribute to:
https://github.com/nix-community | 17:54:59 |
| Taeer Bar-Yam | John Ericson You were talking about getting rid of the std::enable_shared_with_this for SourceAccessor. We should talk at some point about
- Why you want to get rid of it
- If you have any ideas about how to get rid of it
- How you feel about
boost::intrusive_ptr
Because it's currently driving me up a wall
| 21:46:01 |
| John Ericson | @shine:proqqul.net: I thought it was only needed for path values. If you do something else for path values, then we can like have a separate source accessor address spaces with indices | 21:52:58 |
| John Ericson | And index regular shared pointers | 21:53:16 |
| John Ericson | No need to do shared from this | 21:53:22 |
