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

Proposal for improving authorization for the matrix profile API #3805

Closed
turt2live opened this issue Jun 13, 2018 · 4 comments
Closed

Proposal for improving authorization for the matrix profile API #3805

turt2live opened this issue Jun 13, 2018 · 4 comments
Labels
client-server Client-Server API kind:maintenance MSC which clarifies/updates existing spec needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. obsolete A proposal which has been overtaken by other proposals proposal A matrix spec change proposal

Comments

@turt2live
Copy link
Member

Documentation: https://docs.google.com/document/d/1G7JjyTuJlZHieuAflGFWmdKyNViGGLRTWON7AMl0wrM/edit#
Addresses: matrix-org/matrix-spec#168

@turt2live
Copy link
Member Author

turt2live commented Jun 13, 2018

@erikjohnston I'm told this may be of interest to you or be in your sphere of knowledge. When you get a chance, please take a look :)

@ara4n ara4n added the proposal A matrix spec change proposal label Jun 13, 2018
@turt2live turt2live added the client-server Client-Server API label Sep 6, 2018
@turt2live turt2live added the kind:maintenance MSC which clarifies/updates existing spec label Apr 21, 2020
@turt2live turt2live added the needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. label Jun 8, 2021
@richvdh richvdh transferred this issue from matrix-org/matrix-spec-proposals Mar 1, 2022
@ara4n ara4n transferred this issue from matrix-org/matrix-spec May 9, 2022
@richvdh
Copy link
Member

richvdh commented Aug 14, 2024

This seems to have bitrotted, and is now superceded by #4170. I suggest closure.

@mscbot fcp close

@mscbot
Copy link
Collaborator

mscbot commented Aug 14, 2024

This FCP proposal has been cancelled by #3805 (comment).

Team member @mscbot 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 proposed-final-comment-period Currently awaiting signoff of a majority of team members in order to enter the final comment period. disposition-close labels Aug 14, 2024
@turt2live
Copy link
Member Author

as author, I'll just close this.

@mscbot fcp cancel

@mscbot mscbot added proposal-in-review and removed proposed-final-comment-period Currently awaiting signoff of a majority of team members in order to enter the final comment period. disposition-close labels Aug 14, 2024
@turt2live turt2live added obsolete A proposal which has been overtaken by other proposals and removed proposal-in-review labels Aug 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
client-server Client-Server API kind:maintenance MSC which clarifies/updates existing spec needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. obsolete A proposal which has been overtaken by other proposals proposal A matrix spec change proposal
Projects
None yet
Development

No branches or pull requests

5 participants