Skip to content

chore: define issue assignment policy #709

@andreahlert

Description

@andreahlert

Part of #690

Problem

Issues get assigned but stay inactive indefinitely. This blocks other contributors from picking up work and gives a false sense of progress. Several open issues have been self-assigned for 12+ months with no PR or visible activity.

Proposed policy

  1. Assignee = actively working. Only assign yourself if you have a PR open or are about to start coding.
  2. 14 days without visible activity (PR, commit, comment) → triager comments asking for a status update.
  3. 7 more days without response (21 days total) → assignee is removed and help wanted is added.
  4. Re-assignment is welcome. If someone else wants to pick it up, they comment and get assigned.
  5. Umbrella/tracking issues are exempt (marked with lifecycle/frozen).

Applies to everyone

This policy applies equally to maintainers, committers, and external contributors. Consistency builds trust.

Current backlog to review

Several open issues have been self-assigned for over a year with no linked PR or recent activity. Once this policy is agreed upon, a first pass should review all assigned issues and apply the 21-day rule.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions