18 May 2022 |
Aminda | In reply to @clokep:matrix.org (But because it isn't specced, Element cannot depend on it so you could get weird situations.) So the bottom line is that it should be Specced for Element to rely on it? | 13:29:37 |
clokep | In reply to @Ciblia:matrix.org So the bottom line is that it should be Specced for Element to rely on it? Yes. Honestly it is probably like a 100 word MSC. ☹️ | 13:31:10 |
Aminda | In reply to @clokep:matrix.org Yes. Honestly it is probably like a 100 word MSC. ☹️ oh, thanks, that sounds great | 13:32:43 |
Aminda | this shall be my first attempt at a SMC | 13:38:41 |
Aminda | * this shall be my first attempt at a MSC | 13:38:49 |
andybalaam | Drop a draft here and people should be happy to help out | 13:39:41 |
clokep | Yep, would be happy to proof it for you, just don't have time to do it myself. ☹️ | 13:41:38 |
Aminda | https://github.com/matrix-org/matrix-spec-proposals/pull/3818 is the initial version, can I just erase the non-applicable sections? | 13:54:48 |
clokep | Usually it is best to leave most of them to show you've thought about it. 🙂 | 13:56:56 |
Cat | Rendered is missing | 14:05:21 |
Cat | So that is a part of the criticism i can issue to the MSC. | 14:05:39 |
Aminda | oh, I didn't see a PR template, I guess I will add it | 14:06:33 |
Aminda | I also opened https://github.com/matrix-org/matrix-spec/issues/1072 on the other problem | 14:06:50 |
andybalaam | In reply to @Ciblia:matrix.org https://github.com/matrix-org/matrix-spec-proposals/pull/3818 is the initial version, can I just erase the non-applicable sections? This looks good. Can you give a link to the exact part of the spec that needs changing, and suggest the exact wording that should go there? | 14:23:16 |
Aminda | I can try, I guess | 14:24:09 |
Aminda | In reply to @andybalaam:matrix.org This looks good. Can you give a link to the exact part of the spec that needs changing, and suggest the exact wording that should go there? I think the part in the spec that needs changing is somewhere in https://spec.matrix.org/v1.2/client-server-api/#room-upgrades, but I don't see where exactly or what should be added there | 14:28:06 |
Aminda | and I only find that because it was mentioned in https://github.com/vector-im/element-web/issues/19208#issuecomment-1130008275 | 14:28:42 |
andybalaam | In reply to @Ciblia:matrix.org and I only find that because it was mentioned in https://github.com/vector-im/element-web/issues/19208#issuecomment-1130008275 I think it would be somewhere in Server behaviour https://spec.matrix.org/v1.2/client-server-api/#server-behaviour-16 | 14:29:02 |
clokep | Providing exact wording of what needs to be changed shouldn't be necessary, but linking to the part of the spec is appreciated! 🙂 | 14:35:04 |
Aminda | oh, I already did that | 14:37:17 |
andybalaam | I left a small comment and a ✔️ | 14:43:48 |
mscbot | [MSC3818] "MSC3818: Copy room type on upgrade" has been created: https://github.com/matrix-org/matrix-spec-proposals/pull/3818 | 14:53:20 |
Aminda | Oh, is it a problem that this seems to be a subset of https://github.com/matrix-org/matrix-spec-proposals/pull/3385 or can that always be updated afterwards? | 14:55:57 |
clokep | Not a problem. 🙂 | 14:56:19 |
Aminda | clokep: regarding your change suggestion, is /latest/ ok or shouldn't it be /1.2/ ? | 15:16:21 |
clokep | Errr, probably 1.2 is a better idea. | 15:16:54 |
| ___nick___ left the room. | 17:14:31 |
| ___nick___ joined the room. | 17:16:22 |
| ___nick___ left the room. | 17:41:14 |
| ___nick___ joined the room. | 17:46:41 |