Make home-manager official

[infinisil]

As was approved by the @NixOS/steering, as well as the home-manager owners, see NixOS/steering-committee#30 🎉

Preparation checklist for repo transfer:

• GitHub transfer
  • Prepare: Ensure pages fallback redirects exist using a method like here. I've prepared this so that nix-community admins can just click here to create the https://github.com/nix-community/nix-community.github.io repo from https://github.com/nixos-test-org/nix-community.github.io as a template. Once deployed, https://nix-community.github.io/ should not be 404 anymore.
    • I tested this to the most part, but if it's important to have as little downtime of home-manager urls as possible, give @infinisil temporary access to the repo so I can fix things right away if there's a problem.
  • Prepare (some admin of the home-manager repo (@khaneliman or @rycee are listed as maintainers at least)): Add @infinisil (an org owner) as an admin to the home-manager repo
  • Afterwards: Enable Pages, trigger deploy, check that https://nixos.github.io/home-manager works, as well as links like this
• Cachix
  • Prepare: Create a new cachix for home-manager
  • Prepare: PR to switch cachix in .github/workflows
  • Afterwards: Set secret: CACHIX_AUTH_TOKEN
  • Afterwards: Merge the PR
• workflows
  • Prepare: PR to enable CI for nixos org in .github/workflows
  • Afterwards: Merge it
• Home-manager CI App
  • Prepare: Make @infinisil (or another org owner) owner of the Home-manager CI app
  • Afterwards: Transfer the App
  • Afterwards: Set secret CI_APP_PRIVATE_KEY
  • Afterwards: Set var CI_APP_ID
• Buildbot
  • In advance: Add NixOS/home-manager to allow-list: https://github.com/nix-community/infra/blob/master/modules/nixos/buildbot.nix
  • In advance: Make App public
  • Afterwards: Install App on the NixOS org, giving access to home-manager repo
• RFC39
  • In advance: Create @NixOS/home-manager-maintainers
  • In advance: Populate it automatically by integrating https://github.com/NixOS/infra/blob/main/modules/rfc39.nix and https://github.com/nix-community/infra/blob/7dc0562fbd33d8ffa56f8fb88d8683be46c4239c/modules/nixos/rfc39.bash#L20 into https://github.com/nix-community/infra/blob/master/modules/nixos/rfc39.nix

I believe once all advance tasks are done, I should be able to do the migration.

Other transfer tasks:

• Remove home-manager from .github/workflows
• Replace nix-community -> nixos treewide
• Transfer Weblate project
• Transfer Matrix rooms
• Transfer buildbot

[zowoq]

https://buildbot.nix-community.org/

Currently home-manager is using the community buildbot for CI, if the maintainers want to continue using it I'll need to make the github app public so it can be installed in the nixos org and update the allowlist after the repo is moved.

https://nixbot.nix-community.org/

Buildbot will be replaced by nixbot soon, probably in the next few weeks, the nixos org will need to install another github app for nixbot.

[zowoq]

Home-manager is also using the community rfc39 instance to send org invites to the unprivileged home-manager maintainer team, similar to the nixos nixpkgs-maintainers team. They won't be able to continue using the community rfc39 as it would require giving it permissions to manage nixos org members.

[winterqt]

Buildbot will be replaced by nixbot soon, probably in the next few weeks, the nixos org will need to install another github app for nixbot.

(I imagine it’s not worth it to reuse the same GitHub App?)

[zowoq]

Buildbot will be replaced by nixbot soon, probably in the next few weeks, the nixos org will need to install another github app for nixbot.

(I imagine it’s not worth it to reuse the same GitHub App?)

Correct.

[zowoq]

1. Ensure fallback redirects exist using a method like here. I've prepared this so that nix-community admins can just click here to create the https://github.com/nix-community/nix-community.github.io repo from https://github.com/nixos-test-org/nix-community.github.io as a template. Once deployed, https://nix-community.github.io/ should not be 404 anymore.

• I tested this to the most part, but if it's important to have as little downtime of home-manager urls as possible, give @infinisil temporary access to the repo so I can fix things right away if there's a problem.

https://github.com/nix-community/nix-community.github.io

@infinisil I've given you admin on the repo.

[Zimmi48]

What about coordinating this with the documentation team so that the move only happens when there is a clear plan on how to integrate Home Manager deeper into the NixOS website?
In other words, is there any rush to do the transfer now that it has been approved?

[infinisil]

There is no disadvantage to transferring already, it needs to happen at some point, and waiting for a clearer path on website integration doesn't make anything easier, nor is there anything particularly hard about doing the transfer now

[mweinelt]

Home-manager is also using the community rfc39 instance to send org invites to the unprivileged home-manager maintainer team, similar to the nixos nixpkgs-maintainers team. They won't be able to continue using the community rfc39 as it would require giving it permissions to manage nixos org members.

IMO we should unblock this part before we migrate anything.

[philiptaron]

That's referring to https://github.com/nix-community/rfc39-record, correct?

[khaneliman]

Home-manager is also using the community rfc39 instance to send org invites to the unprivileged home-manager maintainer team, similar to the nixos nixpkgs-maintainers team. They won't be able to continue using the community rfc39 as it would require giving it permissions to manage nixos org members.

IMO we should unblock this part before we migrate anything.

I agree, that part would be rather unfortunate to lose.

That's referring to nix-community/rfc39-record, correct?

Correct.

[infinisil]

I took a closer look and updated the PR description with a more complete checklist of everything that needs to be done before we can do a repo transfer.

@zowoq @khaneliman Can you take a look at that and let me know if something's missing or wouldn't work?

For the actual transfer I'd suggest we schedule a call once all preparation tasks are done

[Zimmi48]

There is no disadvantage to transferring already, it needs to happen at some point, and waiting for a clearer path on website integration doesn't make anything easier, nor is there anything particularly hard about doing the transfer now

The disadvantage that I had in mind is that you might end up having to manage two documentation website redirections instead of just one. But of course, that's really up to the implementors (such as you) to decide whether this is a real issue or not. This is not likely to create issues on the user side.