Skip to content

Latest commit

 

History

History
34 lines (22 loc) · 2.17 KB

PROJECT_MANAGEMENT.md

File metadata and controls

34 lines (22 loc) · 2.17 KB
Raw

Project Management for Kuma

Triage

The original doc for this is there.

Triaging happens on a weekly basis on Mondays Event invite.

In this meeting we will iterate over each repo in the kumahq github organization and take the following actions:

  • Look at all tickets with triage/pending and take the following actions:
    • Set accurate kind/* and area/* labels
    • If a ticket is unclear set triage/needs-information
    • If a ticket needs someone to try to reproduce triage/needs-reproducing
    • If a similar ticket already exists set triage/duplicated add a comment with the original ticket and close the newest ticket
    • If a ticket looks good, set triage/accepted. A ticket being accepted doesn’t mean someone will work on it, just that it’s looking good. However, a closed ticket with triage/accepted is work that was actually done. On these ticket we will often add information about possible implementations or area.

all triage/pending issues in kumahq github search

Stale tickets

It's the responsability of the maintainers to review tickets with triage/stale. Maintainers can do these things to deal with stale issues:

  • Close it with a comment explaining why it's being closed.
  • Remove the stale label if they think this issue is still releavant and not worth more discussion.
  • Replace triage/stale with triage/pending to have the ticket be rediscussed at the next triage meeting.

all triage/stale issues in kumahq github search

Tooling

In order to make this simple we've added some automation based mostly on github actions. You can very likely copy the file .github/workflows/lifecycle.yml to setup our default automation for project management.