Future of NixNG

[tkr-sh]

Hi!
It seems that there isn't a roadmap on which are the priorities of NixNG.
Would it be possible to have some, and to have a more detailed list of objectives to: what NixNG should be ?

• Is it just an experimental distribution to tests things ?
• Does it aim to be a distribution that boots on real hardware and to be a debloated replacement for NixOS ?
• What are the priorities for now ? Providing a kernel and initramfs ?
• If someone wants to help, what should they do ?

I think that the project, as it's core, is a wonderful thing and a good idea; tho seems a bit immature.

[MagicRB]

Hi!

• it did start of as an experimental distribution and I have made use of it as such. Some of the modules we have are quite substantially different from what you'd see in NixOS. But aside from that it is quite similar to NixOS. Though if you want to experiment I'm open to merging experimental stuff, the userbase is tiny and we can cope with some jank.
• It would perhaps be nice to get it to boot, maybe for really embedded usecases but that requires deep changes to nixpkgs among other things. Since I started this project I've also been forcibly fed the systemd pill so I don't have as much of a desire to get rid of systemd as I used to.
• currently it is in maintenance mode from my side. My usecase is running it inside containers as my config has grown larger a fully monolithic config started to become completely unreasonable so I split out some services into containers which currently reside inside a k3s cluster. Which means that, at least from my side, a kernel and initramfs are not high priority. Though again I'm always open to PRs.
• get to know the codebase, find their usecase and help me maintain this essentially. As you said the codebase is still immature after, uh, 3 years? so contributing isn't easy. Though as can be seen with Add dnsmasq service #35 it's doable and I'll happily accept PRs which follow a few basic rules.

That's about it from my side, apologies for the response delay, I'm currently very busy and reviewing&merging a PR is easier than writing out this response :)

[MagicRB]

@tkr-sh we just merged #41 #36 and #42 is in progress :)