see
1 Like
tl;dr: nix-community’s future is unclear, if they wanted to be in the nixos org I’d love to help, but I think that decision should be made by the maintainers, as there could be potential downsides and it’s their project.
fwiw home-manager is moving into the actual NixOS organization itself because the future of nix-community is up in the air. So perhaps nix-community wouldn’t be helpful.
If nix-darwin wanted to move into the NixOS org I wouldn’t mind that and would love to bring that to the Steering Committee and other teams. But it would of course depend on whatever they actually need, and whether there are any downsides they’d see with that.
Personally, I’m not a MacOS user yet, but I know that if I ever got an apple laptop, this would probably be one of the first things I’d install. I think that’s the case for a lot of users.
I would however also fully understand wanting to keep the project out of the NixOS org! Put if they were interested I’d at least like to put that on the table.
6 Likes
nix-community’s future is unclear
fwiw home-manager is moving into the actual NixOS organization itself because the future of nix-community is up in the air
could you elaborate on this a bit further?
if they wanted to be in the
nixosorg I’d love to help
thanks! from a users perspective i think doing this would bring a lot more attention to nix-darwin and the issues ive had (which prompted my proposal) should resolve on its own
I’d temper expectation to be honest. I think that just moving into the main org wouldn’t nescessarrily increast traffic drastically, albeit maybe I’m wrong.
I can imagine that the problem really is more that there is a limited bandwidth to work on this amongst the maintainers and that also makes it hard for them to onboard new people to the project. Being in the org doesn’t solve either of those on its own, I think it would likely require more interventions, and I’m not sure who’d be doing those.
I think you’re on the right track however to see if you can get more maintainers for that project. Ultimately, I think your solution here is to step beyond being a user and graduate into a contributor, it’s much easier to fix the problem via that route.
The maintainers even mention this as a route for e.g. you to get merge bits:
those of us who are active maintainers are fairly busy, yeah. I am trying to work through our backlog but there’s a lot there :). do feel free to request my review/ping me on PRs, and I will try to get to them.
To answer your question (and speaking only for myself here), I think we’re not necessarily against it. Part of gaining that trust would be through reviewing/testing other people’s PRs to this repo, which incidentally also helps make my limited review time more efficient.
You should pursue that! I see you already reviewed [Backport 26.05] homebrew: address new CLI flag requirements by Samasaur1 · Pull Request #1805 · nix-darwin/nix-darwin · GitHub, perhaps you should try a few more and ping samasaur1 after and see if they get merged faster.
5 Likes
I think that just moving into the main org wouldn’t nescessarrily increast traffic drastically, albeit maybe I’m wrong.
probably not getting more traffic but moving to nix-community or nixos org would allow nix-darwin to utilize pre-existing trust, e.g. give the well known nixpkgs darwin maintainers merge bits
there is a limited bandwidth to work on this amongst the maintainers
i totally understand that reviewers takes longer to response but for such a critical project the status quo is far from ideal, thus the proposal to move to new org 
Ultimately, I think your solution here is to step beyond being a user and graduate into a contributor
unfortunately im at capacity as well (my own work, nixpkgs, colmena, etc.)
2 of my oldest PRs to nix-darwin has been sitting idle for a bit over a year now. i’m fine with continue sending breaking change fixes like the homebrew new CLI/trust change and nixos build manual change if they are to occur in the future, but reviewing patches is definitely wayyyy more mentally straining
1 Like