element-hq / element-hq/element-meta
Mobile triage process feedback
- Dominant language
- No language data
- Stars
- 112
- Forks
- 25
- Avg merge
- 6h 6m
- Merged PRs (30d)
- 4
Description
An issue to track our thoughts/queries on triage process
From the Android perspective https://github.com/vector-im/element-android/projects/4
#### Board
- Should the triage board be removed when another project has been added to an issue?
- The `Triaged` column is never cleared, making the github project very slow! should we remove the triage project after applying the labels?
- Do we need the `Backlog` column?
#### Labelling
- When applying the `O - occurrence` label, are we favouring how often the issue actually happens (which is difficult to quantify without tracking) or how easy it is to reproduce/trigger
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the Android triage project linked in the issue, including its Board columns and the `O - occurrence` label. Resolve the listed process questions with the project owners, then document the agreed triage workflow and label definitions; the issue is done when those decisions are recorded and actionable.
Written by the indexing model from the issue text.
Assessment
- Domain
- developer-experience
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100