matrix-org / matrix-org/matrix-spec
Membership should be transferred when upgrading a room
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
Joins should be automatic where possible. Invite-only rooms are a bit of a questionable one though (https://github.com/matrix-org/matrix-doc/issues/1864).
For joins, we might be able to work around the complexity by abusing Matrix: when upgrading the room, send invites to all the current members and servers can be expected to auto-accept following the verification of the invite being for an upgraded room. Or possibly not auto-accept?
Starting point for the discussion is here: https://github.com/matrix-org/matrix-doc/pull/1930#discussion_r268027969
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 discussion linked from matrix-doc issue 1864 and the discussion on Matrix spec PR 1930. Clarify the intended membership-transfer behavior for room upgrades, including invite-only rooms and automatic acceptance. Done means the protocol behavior is agreed and reflected in the relevant Matrix specification text.
Written by the indexing model from the issue text.
Assessment
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100