Identify who to nag about missing triage owners without using a team_manager mapping
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
We were discussing this the other day. By tracking changes in people.json, we can know who was the manager of a person who left Mozilla and is still triage owner of some component.
By doing this, we can also actively identify people who leave, without having to wait for their accounts to become inactive or disabled.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating how people.json changes are tracked and where triage owners are represented or processed. Trace the existing handling of departed or inactive people and determine how a former manager could be identified without team_manager mapping. Done means the tool can identify relevant departed triage owners and the person to notify, with coverage for the change-tracking behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100