Skip to content

[Proposal] Establish issue claiming process to prevent duplicate workย #14898

Description

@cxhello

Background

Nacos currently lacks a formal issue claiming process. Contributors express interest via comments, but there is no standardized mechanism to track who is working on what. This leads to:

Industry Research

Project Mechanism Timeout Automation
Kubernetes /assign command via Prow Bot 90d stale โ†’ 30d rotten โ†’ close Heavy (Prow)
React Comment + CONTRIBUTING.md rules 14 days None (maintainer-enforced)
VS Code help wanted label + manual assign 7d info-needed Light
Rust @rustbot claim Triagebot managed Medium
Spring Boot ideal-for-contribution label 14d feedback Light
Dubbo / RocketMQ No formal process N/A None

Key takeaway: 14-day timeout is industry consensus. Documentation-first approach (React model) is low-cost and effective for mid-size communities.

Proposal

1. Add "Issue Assignment" section to CONTRIBUTING.md

## Issue Assignment

### How to claim an issue
- Comment on the issue expressing your intent (e.g., "I'd like to work on this")
- Briefly describe your approach so maintainers can provide early feedback
- Wait for a maintainer to assign the issue to you

### Expectations after claiming
- Submit a PR within **14 days** of being assigned
- If you need more time, comment on the issue to let others know
- If no PR or update is provided within 14 days, the issue may be unassigned
  and made available for other contributors

### Tips
- Check if an issue already has an assignee before claiming
- For complex issues, consider discussing your approach before starting
- It's okay to unassign yourself if you can't continue โ€” just leave a comment

2. Use GitHub Assignees

When a maintainer confirms a claim, set the GitHub Assignee (not just reply in comments). Benefits:

  • Issue list visually shows claim status
  • Filter unclaimed issues with no:assignee
  • Prevents duplicate claiming

3. (Optional, future) Lightweight automation

If the community grows, consider adding a GitHub Action for:

  • /assign comment command โ†’ auto-set assignee
  • 14-day timeout โ†’ auto-unassign + notify

This is not needed initially โ€” the documentation + Assignee approach is sufficient.

Activity

  1. KomachiSion commented on Apr 9, 2026

    @KomachiSion
    Collaborator

    Great idea, the assign before is depend maintainer and robot.

    might be we can do this by ai and github action.

    Please first change the imformation in CONTRIBUTING.md and I will try auto-assign with ai.

    you can help to research the bot or github action.

  2. cxhello commented on Apr 9, 2026

    @cxhello
    ContributorAuthor

    Thanks for the feedback! Here's the progress and plan:

    Current Progress

    Implementation Plan

    Phase 1: Command-based auto-assign (in progress)

    A GitHub Action workflow (issue-assign.yml) with two functions:

    1. Comment command handling โ€” contributors comment /assign to self-assign, /unassign to release. Runs via issue_comment trigger, no maintainer intervention needed.
    2. Stale assignment cleanup โ€” daily cron job checks for inactive assignments:
      • Day 11: warning comment + stale-assignment label
      • Day 14: auto-unassign + notification comment
      • Activity = assignee comment on issue OR linked PR

    Phase 2: AI intent recognition (future)

    Extend Phase 1 to detect natural language claiming intent (e.g., "I'd like to work on this", "ๆˆ‘ๆƒณ่ฎค้ข†่ฟ™ไธช") without requiring a fixed /assign command. This can be added as a branch in the existing workflow โ€” when a comment doesn't match /assign or /unassign, pass it to an LLM to classify intent.

    Will submit the Phase 1 PR soon.

  3. added 2 commits that reference this issue on Apr 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions