Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] MSC3068: Compliance tiers #3068

Closed
wants to merge 9 commits into from
Closed

[WIP] MSC3068: Compliance tiers #3068

wants to merge 9 commits into from

Conversation

erkinalp
Copy link

@erkinalp erkinalp commented Mar 18, 2021

This MSC defines several tiers of complying to Matrix specification.
Rendered

Signed-off by: Erkin Alp Güney <erkinalp9035@gmail.com>
Signed-off by: Erkin Alp Güney <erkinalp9035@gmail.com>
@turt2live turt2live added kind:maintenance MSC which clarifies/updates existing spec proposal A matrix spec change proposal proposal-in-review labels Mar 18, 2021
Signed-off by: Erkin Alp Güney <erkinalp9035@gmail.com>
@turt2live turt2live marked this pull request as draft March 18, 2021 15:57
@turt2live turt2live changed the title MSC3068: Compliance tiers [WIP] MSC3068: Compliance tiers Mar 18, 2021
@turt2live
Copy link
Member

@erkinalp I've reclassified this as a work in progress. There's several pieces missing from this proposal, such as a justification and rationale for the change. A change as critical as this should have a lot of rationale to back it up.

@erkinalp
Copy link
Author

such as a justification and rationale for the change

So, you consider this change as normative?

@turt2live
Copy link
Member

It's hard to classify this MSC as anything until it's been written out more completely, other than being a work in progress. At the moment I can't judge the MSC on its merits given it does not present a justifiable case for its own consideration.

Signed-off by: Erkin Alp Güney <erkinalp9035@gmail.com>
@richvdh
Copy link
Member

richvdh commented Mar 18, 2021

I'm unclear what area of the spec this is seeking to change.

I'm also unclear what purpose the change would serve.

This PR smells of timewasting.

Signed-off by: Erkin Alp Güney <erkinalp9035@gmail.com>
@erkinalp
Copy link
Author

I'm unclear what area of the spec this is seeking to change.
what purpose the change would serve.

This MSC seeks to define a standard terminology for how compliant a client or a server is.

@erkinalp erkinalp marked this pull request as ready for review March 18, 2021 16:29
Signed-off by: Erkin Alp Güney <erkinalp9035@gmail.com>
@turt2live
Copy link
Member

There's still no justification for why we need this.

@turt2live turt2live marked this pull request as draft March 18, 2021 16:35
Signed-off by: Erkin Alp Güney <erkinalp9035@gmail.com>
Signed-off by: Erkin Alp Güney <erkinalp9035@gmail.com>
@erkinalp
Copy link
Author

still no justification for why we need this

Added it.

@erkinalp erkinalp marked this pull request as ready for review March 18, 2021 16:39
@turt2live
Copy link
Member

I'm not convinced that this MSC is founded upon the best intentions to improve Matrix and instead appears as time wasting.

@mscbot fcp close

@mscbot
Copy link
Collaborator

mscbot commented Mar 18, 2021

Team member @turt2live has proposed to close this. The next step is review by the rest of the tagged people:

Once at least 75% of reviewers approve (and there are no outstanding concerns), 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 information about what commands tagged team members can give me.

@mscbot mscbot added disposition-close proposed-final-comment-period Currently awaiting signoff of a majority of team members in order to enter the final comment period. labels Mar 18, 2021
@turt2live turt2live added this to Ready for FCP ticks in Spec Core Team Backlog Mar 18, 2021
Signed-off by: Erkin Alp Güney <erkinalp9035@gmail.com>
@erkinalp erkinalp closed this Mar 18, 2021
@turt2live turt2live added abandoned A proposal where the author/shepherd is not responsive and removed disposition-close proposed-final-comment-period Currently awaiting signoff of a majority of team members in order to enter the final comment period. labels Mar 18, 2021
@turt2live turt2live removed this from Ready for FCP ticks in Spec Core Team Backlog Mar 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
abandoned A proposal where the author/shepherd is not responsive kind:maintenance MSC which clarifies/updates existing spec proposal A matrix spec change proposal
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants