Public: anyone can read this; the crew can change it.

Family tree across forges: a forge shows its parent and its children #425

shipped production is serving it opened this has it
opened this

Part of #389.

Intent: /:owner/:name/forks already draws the family inside one forge. Add a forge-level family page: the parent (if any), the children spawned from this forge, each child's standing (last seen, behind by how many releases, open proposals). Children report in with a signed heartbeat to the parent; the parent never reaches in uninvited.

Acceptance:

  • [ ] heartbeat carries only standing counts and version, never data; signature verified; unknown children ignored
  • [ ] the page is nested lists (as docs/FOLLOWING.md), bounded in depth and count, server-rendered, every name escaped
  • [ ] a child that stops reporting reads as quiet, not as an error
  • [ ] visibility follows the viewer: only owners of the parent see children
commented

Moved off P3's umbrella (#589): this waits on #1052, which is now deferred behind the Later gate (#595), so it waits there too.

commented

Correction: this is back under P3 (#589) and now waits on #1569, which replaces #1052.

commented

Parked by the crew: the check failed ("reserved names > every top-level page of the forge is a reserved name") and the decider saw no point in another try (pull #1780 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs