matrix-doc/content
Andrew Morgan a7b344d45a
Clarify what happens when a concern is raised during FCP (#3180)
It wasn't entirely clear what should happen to the FCP timer (and state) when a concern is raised during FCP. After some discussion, we agreed that when a concern is raised:

1. FCP will continue to not conclude until at least 5 days have passed, but once those 5 days are up it *still* won't conclude until all concerns raised during FCP are resolved.
2. If a concern warrants a large enough change in the document, then the Spec Core Team may consider cancelling FCP and restarting the timer in order for people to have some time to think about and review the new changes.
2021-05-06 13:41:08 +01:00
..
client-server-api Merge pull request #3170 from matrix-org/travis/spec/msc2713-rm-v1-id 2021-05-04 09:59:27 -06:00
rooms Add knocking to the spec 2021-04-28 19:50:13 -06:00
_index.md Add knocking to the spec 2021-04-28 19:50:13 -06:00
appendices.md Remove group identifiers 2021-05-04 09:43:02 -06:00
application-service-api.md Update content to call the new template for HTTP APIs 2021-01-29 15:32:31 -08:00
changelog.md Add changelog page and templates 2021-02-02 20:47:18 -08:00
identity-service-api.md Merge pull request #3170 from matrix-org/travis/spec/msc2713-rm-v1-id 2021-05-04 09:59:27 -06:00
proposals.md Clarify what happens when a concern is raised during FCP (#3180) 2021-05-06 13:41:08 +01:00
push-gateway-api.md Update content to call the new template for HTTP APIs 2021-01-29 15:32:31 -08:00
server-server-api.md Add knocking to the spec 2021-04-28 19:50:13 -06:00