MSC2002: Proposal for adopting MSC1884 as v4 rooms#2002
Conversation
|
@mscbot fcp merge we want to get this and 1884 merged asap and released in prep for 1.0 |
|
Team member @ara4n has proposed to merge this. The next step is review by the rest of the tagged people: No concerns currently listed. Once a majority of reviewers approve (and none object), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! See this document for info about what commands tagged team members can give me. |
|
#1884 - link for the lazy |
|
I think what happens for room v5 / matrix 1.0 and beyond are somewhat orthogonal here. +1 to getting features out into the wild rather than sitting on them until they form a huge batch, so I am happy with this. |
|
🔔 This is now entering its final comment period, as per the review above. 🔔 |
I think the proposed longer-term context is fairly important to try to understand how this fits in, but agreed it's technically orthogonal to the MSC itself. |
|
@matrix-org/core-team I'd like to propose an expedited FCP for this, so we can merge this (and #1884) into the spec and ship it in synapse (matrix-org/synapse#5210) asap, so that when 1.0 rolls around we have as many servers talking v4 rooms in the wild as possible and we can enable creating v4 rooms by default. I suggest we reduce FCP to 1 day - i.e. aim to merge this around 15:00 GMT+1 tomorrow, unless someone finds a last minute problem with MSC1884 (or this). |
|
Impl is at matrix-org/synapse#5217, ready to merge when this completes FCP. |
|
as per #2002 (comment), we are declaring FCP to be complete here. |
|
cancelling the bot's FCP to stop it "helping" @mscbot fcp cancel |
|
@richvdh proposal cancelled. |
|
Spec PR: #2019 |
|
merged 🎉 |
Rendered: https://github.com/matrix-org/matrix-doc/blob/matthew/room_v4/proposals/2002-rooms-v4.md