The flake registry currently only has you, @edolstra, as a maintainer. It doesn't see much traffic, but when something comes up, like the proposed tarball migration (#62) and future release entry additions, we need a reliable team, that responds within the timeline of the NixOS release process.
The Nix team is already responsible for the implementation that parses and uses this format, so it would seem like a natural fit to broaden repository maintenance by delegating maintenance to the Nix team. This is especially relevant, since the registry format currently lacks detailed documentation, that would allow others to easily fill that role.
Delegating maintenance would improve continuity, and better align repository ownership with the team responsible for the corresponding implementation. You are already a member of the Nix team, so this wouldn't exclude existing involvement while making maintenance responsibilities more resilient.
WDYT?
The flake registry currently only has you, @edolstra, as a maintainer. It doesn't see much traffic, but when something comes up, like the proposed tarball migration (#62) and future release entry additions, we need a reliable team, that responds within the timeline of the NixOS release process.
The Nix team is already responsible for the implementation that parses and uses this format, so it would seem like a natural fit to broaden repository maintenance by delegating maintenance to the Nix team. This is especially relevant, since the registry format currently lacks detailed documentation, that would allow others to easily fill that role.
Delegating maintenance would improve continuity, and better align repository ownership with the team responsible for the corresponding implementation. You are already a member of the Nix team, so this wouldn't exclude existing involvement while making maintenance responsibilities more resilient.
WDYT?