matrix-org / matrix-org/matrix-spec
Specify the default power levels during creation better
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
**Link to problem area**: https://spec.matrix.org/v1.15/client-server-api/#creation
**Issue**
Currently, the spec is light on details for what the initial power levels event should include. Aside from `state_default` and creator permissions, we should also specify which `events` are restricted, the defaults for `ban`, `redact`, etc, and any other semantic behaviour.
Without this, clients are essentially forced to always use `power_level_content_override` to achieve deterministic power levels. If the spec was clear on what the defaults are, most clients could then rely on `/createRoom` doing the "right" thing.
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 with the Matrix client-server API creation section linked in the issue and review the initial power levels event. Define the documented defaults for restricted events, ban, redact, and related semantic behavior; done means clients can rely on /createRoom without needing a power_level_content_override for deterministic defaults.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100