matrix-org / matrix-org/matrix-spec
We need an m.call.ringing state to map SIP 180 to (SPEC-199)
Open
Nobody has claimed this yet.
A-Client-Server
feature
p2
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
(Imported from https://matrix.org/jira/browse/SPEC-199)
(Reported by @ara4n)
Contributor guide
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 reading the Matrix call-state definitions and the imported SPEC-199 report to determine how SIP 180 is currently represented. Locate the specification section defining m.call states; done means documenting and consistently mapping SIP 180 to a new m.call.ringing state, with any required examples or validation updated.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100