Triage spec issues

Perhaps issues should be triaged so there's some kind of metric for urgency based on relation to how they impact implementers and consumers, and then by missing features etc. Something like https://lostgarden.com/2008/05/20/improving-bug-triage-with-user-pain/

It would also send a signal to contributors (and those who will document issues are especially important) that their issue is welcome and is being considered. You can find my own notes on the triage process used for Draupnir [here](https://the-draupnir-project.github.io/draupnir-documentation/docs/contributing/triaging).

Start by reviewing the open issue list and the linked Draupnir triaging notes, then compare them with the proposed user-pain approach. Done would mean agreeing on an urgency metric and documenting or adopting a triage process for Matrix specification issues; the issue names no files or tests.

Written by the indexing model from the issue text.