Consider moving opencode and openchamber forks to developing-today-forks organization #157

Activity

1. github-actions

   assigned

   dezren39

   on Oct 12, 2026
2. dezren39

   added

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   on Oct 29, 2026
3. dezren39 commented on Oct 29, 2026

   

   dezren39

   on Oct 29, 2026

   MemberAuthor

   More actions

   🤖 Agent note · escalated

   • Agent: queue worker (repo-worker-code, lane B)
   • Session / ID: queue task 2008 (triage)
   • Found via: queue claim
   • Task: Triage verdict: premise CONFIRMED, but the route is a decision only Drew can make — escalating with the substance below.
   • Expectation: Drew picks an option; implementation (if "move") is mostly an owner-only org transfer plus a reference sweep.

   Verified at 2026-10-29T00:51:31Z: developing-today/opencode and developing-today/openchamber both still live under developing-today and both are forks; developing-today-forks exists (87 public repos) and does not hold either repo. Reference surface in this repo alone: flake.nix inputs plus 30+ files citing developing-today/opencode and 24+ citing developing-today/openchamber, before counting fleet automation outside this repo (queue/sweep jobs, laptop clones, skills) that hardcodes both names.

   The decision — move the two fork repos to the developing-today-forks org, or keep them where they are?

   • Option A — Move both: org tidiness; developing-today shows only first-party work. Ramifications: GitHub redirects keep old git/issue URLs working, but a transfer does not carry CI secrets/Actions config, and every hardcoded reference (flake inputs, docs, fleet jobs, local clones) needs a sweep; only an org owner can do the transfer itself, so no agent can execute this unilaterally.
   • Option B — Keep, declared as exceptions: zero churn and zero risk to the live fleet that builds on both forks daily. Ramification: the org stays "untidy" by the stated convention — but these two are not passive mirrors like the forks-org residents (e.g. server.nix); they are actively developed, load-bearing products of this fleet.
   • Recommendation: Option B. The benefit of moving is cosmetic; the cost/risk lands on working automation, and the premise that these are ordinary forks is weak — they are developed here, not mirrored. Revisit only if the forks go quiet.

   Escalated: swapping to user/escalated and blocking queue task 2008 pending Drew's call.
4. dezren39

   added

   user/escalatedQueue or user escalation stateQueue or user escalation state

   queue/blockedQueue or user escalation stateQueue or user escalation state

   status/blockedQueue or user escalation stateQueue or user escalation state

   and removed

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   on Oct 29, 2026
5. dezren39 commented on Oct 29, 2026

   

   dezren39

   on Oct 29, 2026

   MemberAuthor

   More actions

   DREW DECISION (2026-10-29, main chat; he notes he has answered this before — treat as settled, do not re-escalate): KEEP the forks in developing-today as declared exceptions for now. Long-term ideal only, NOT near-term: (1) first move everything that is NOT an actual fork into the archive organization; (2) once only real forks remain, reconsider moving the forks to a forks org. No action on this until that sequence is ever started; the exceptions stand.
6. dezren39

   removed

   user/escalatedQueue or user escalation stateQueue or user escalation state

   queue/blockedQueue or user escalation stateQueue or user escalation state

   status/blockedQueue or user escalation stateQueue or user escalation state

   on Oct 29, 2026
7. dezren39 commented on Oct 29, 2026

   

   dezren39

   on Oct 29, 2026

   MemberAuthor

   More actions

   BOARD CLEARING (2026-10-29): DECIDED by Drew — KEEP the opencode and openchamber forks in developing-today as declared exceptions. His ruling is recorded on this issue (comment 6491369933): settled, answered before; long-term ideal only is non-forks to an archive org first, then reconsider the forks. Closing: the question this issue asked is answered outright. Removed from the needs-Drew board.
8. dezren39

   closed this as completedon Oct 29, 2026
9. developing-today

   added

   status:done

   on Oct 29, 2026