#725

Proposal: a read-only view of who works on what (experimental demo, no process change)

Openttd0xopened 11h ago

Claiming work in "Coordinating who works on what" works, but the threads are hard to follow at the current pace. The list has already moved twice because a thread reached 300 comments (#156 → #374 → #634). In the first three hours alone (2026-11-21, 20:25–23:30 UTC) there were 334 comments and 193 claiming: commands. 113 of those claims had no item ID, and three pairs of claims on the same item came within a minute of each other (15, 0 and 6 seconds apart). The board is kept current by hand. These numbers come from the saved copy of the comments in the demo repo, so anyone can reproduce them.

I built an experimental, read-only view of the same information, outside this repository:

It shows, with a link to every comment it used:

  • per item: owned, done, needs a check, or no observed claim;
  • where the comments and the board disagree, including items still listed as up for grabs that were already claimed;
  • a review list of unclear cases, such as a claim without an ID, or a status from someone with no claim on the item. These never change ownership automatically;
  • when the data was fetched. After an hour, everything is shown as "check".

In the snapshot fetched at 2026-11-22 02:15 UTC (board updated 02:12 UTC), 840 comments in #156, #374 and #634 since 20:25 UTC the day before:

  • the view agrees with the board on 42 owners, differs on 2, and sees 16 claims in comments that are not on the board yet;
  • 2 of the 11 items on the up-for-grabs list were already claimed or done in comments (BUILD-124, and TEST-71 done);
  • at that time it classified 89 items as owned, 132 as done, 17 as needing a check, and 10 as having no observed claim.

What it does not do. It changes nothing here: no comments, labels, PR changes or checks. The claiming: / status: / releasing: / done: / finding: lines stay as they are, and the comments and the board remain the source of truth. It does not prevent two people from taking the same item; it only shows it. It runs by hand, so it can be up to an hour old. It does not read PR states yet, and it sees free-text claims only occasionally. "No observed claim" is not permission to start. If it is wrong or stale, nothing breaks. It contains no game data.

If it is useful, possible next steps (details in ROADMAP.md):

  • Read-only, no change here. Link PR states to items, and compute the board's hand-kept sections from the PR API: files changed by more than one PR, several PRs for one item, needs a rebase, and claimed for 3+ hours without a PR. Overlapping files are a review signal only; they do not prove a conflict or duplicate work.
  • Only with your agreement: claims without comments, through a small claim API.
    • An agent sends POST /claims {"task": "SHADER-48"} and gets "claimed" or "already claimed by X" at once, before any work starts. Claims are short leases that are renewed, and this page stays the view on top of it.
    • It would need someone to run it, and your decisions on the transition: which wins when a claiming: comment and an API claim collide, when the API becomes the only channel, and that new claims pause rather than fall back to comments if the service is down.
    • Draft PRs as claims were considered, but at the current PR pace they would mostly add noise.

Questions for @ItsNotRexed and @KoertLichtendonk:

  1. Is a view like this useful to you, and would you want it linked from the coordination issue?
  2. If so, should it eventually run in this repository, or stay separate?
  3. Is any of the next steps above worth exploring? I would not start any of them without your agreement.

Happy to close this if it is not wanted.

AI-assisted (Claude Code).

Activity

1
ramenbellic11h ago

+1 to this. With this many people (and agents) working at once, the hard part of this project has become project management, not code: three coordination threads in a day, claims seconds apart, and a board someone has to keep current by hand. A read-only view is a good first step.

It also looks like a natural fit for a kanban board, perhaps a GitHub Project on this repository:

  • Columns that match the board's sections: Up for grabs → Claimed → PR open → Needs a check → Done. "Needs a rebase" and "Claimed 3+ hours without a PR" could be filtered views instead of hand-kept lists.
  • Custom fields for what's tracked in tables today: item ID, area (SHADER / D3D / ASSET / BUILD / TEST), size, and what a check needs (Win, GPU, AMD/32-wide, game copy). Testers could then filter for "GPU, no game copy, nobody has checked it".
  • Built-in workflows add new PRs automatically and move items when a PR is opened, merged or closed. That covers much of what is updated by hand now, and the project is queryable through the API, so tools like the one in this proposal could read it instead of parsing comments.

One caveat: on GitHub, only people with triage or write access can assign issues, and most contributors here have neither. So claiming would still need something like claiming: comments or the claim API proposed above, with the coordinator or a bot moving the card. Even so, a board everyone can see would make "is this already taken?" much easier to answer than scrolling through 300 comments.

(Drafted with Claude Code.)