Decision in brief
Make the handover decision in the project's documented governance process. Record which responsibilities move, who accepts them, and which systems users depend on. Have the incoming maintainers reproduce a test release and inspect the communication plan before changing live ownership. Consider an explicit maintenance pause or retirement when no team can take responsibility.

What belongs in an open source project governance checklist?
Inventory the canonical repository, package registry and namespace, domains, support channels, release workflow, moderation, and security contact. Identify the owners and who may approve changes. Ask contributors who rely on translation, accessibility or release support what still needs a named owner.
Platform transfers can carry access and settings with them. GitHub documents how repository redirects, permissions, and linked services behave after a transfer. Review installed applications and external package registries independently. Assign fresh role access through the normal owner-approved process and record who is authorized to update the release.
| Project condition | Handover decision | Evidence to require |
|---|---|---|
| Current maintainers can mentor a successor | Overlap for one release cycle | Incoming team can reproduce a test release and respond to triage |
| One implementation team is winding down | Identify which repositories and support duties are affected | A dated scope notice and maintained entrypoints for other implementations |
| Users consume packages or apps outside the repository | Plan each distribution channel separately | Registry owner, supported versions, test installation, and a canonical support pointer |
| No team can support a safe transfer | Publish a maintenance pause or retirement | Clear project status, archived artifacts, and guidance on alternatives or succession |
Two HN cases show where scope can get lost
In the Shipyard discussion, momack2 distinguished the maintenance team's announcement from the lifecycle of the wider IPFS project. Write the scope of a handover at the level of implementer, repository, and release channel so readers can see what changes.
In a separate discussion of a Syncthing Android maintainer change, bxparks highlighted confusing similarities among repository and app names. Make the canonical project and package identifiers explicit in your transition notice. The thread illustrates navigation and communication concerns.
Rehearse ownership and release before cutover
- Record the approval that authorizes the handover, names of the incoming owners, project scope, and owner for each repo, registry, domain, and support channel.
- Use an approved staging repository and test namespace. Ask the incoming team to build, tag, and publish a clearly marked test artifact and have another maintainer verify the installation.
- Check issue search, release links, permissions, translation workflows, and the support contact with a test identity. Review the announcement with a downstream user and confirm that the source and destination are unambiguous.
- Approve cutover only if owners are assigned, staging release and verification pass, and the old entrypoints have a checked migration or retirement message. Stop if approval, package ownership, or the release and recovery path is uncertain.