Issue claiming: can we make ownership explicit and race-resistant?

[Zi-Yi-Ming]

Background

Right now, claiming an issue is informal: a contributor comments “please assign me”, and a maintainer assigns by hand. That is fine at low volume, but it produces races when two people show up at once (#1246, #1266), and ownership lives in comment text rather than in real issue state.

What we actually need

Not a project-management system. Just three machine-enforceable rules:

1. Maintainer decides acceptance — /accept marks an issue ready for public work.
2. Contributor decides whether to claim — /assign on a claimable, unassigned issue.
3. Bot enforces ownership — first valid claim wins; never overwrite an existing assignee; /unassign to release.

Proposed commands (minimal)

Command	Who	Effect
/accept	write/maintain/admin	add accepted
/assign	anyone	assign commenter if open + claimable + unassigned
/unassign	assignee or maintainer	clear assignee

Claimable = accepted, or already good first issue / help wanted (so newcomer issues stay easy to take).

Hard rules: closed issues ignore commands; unknown commands are no-ops; the bot never revokes a manual maintainer assignment.

Why not something bigger

A full lifecycle bot (workgroups, prow commands, PR admission) does not match this repo’s fast-response, good-first-issue culture. We only want the smallest ownership protocol that removes ambiguity.

Labels

Only two new ones: accepted, in-progress. Existing type labels from issue forms stay as they are.

Implementation shape (if maintainers want this)

One workflow, actions/github-script, ~150–200 lines. No Python stack, no prow action, no CI changes.

Questions

1. Should good first issue / help wanted be claimable without /accept?
2. Who may /accept — write/maintain/admin only?
3. Any objection to slash commands vs free-form comments?
4. Worth a tracking issue + PR, or is the current manual process enough?

Happy to turn this into a tracking issue and a small PR if the direction looks right.