-
Notifications
You must be signed in to change notification settings - Fork 28
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
Device management & UI polish in MAS #1492
Comments
I'd like to add this #1491 (can't edit OP). We need to give users the ability to change their email addresses, avatar and display name as part of the MVP. |
I'd like to add the cosmetic parts of this issue to the list: #1569 |
Closing this off as we have stopped the work a while ago. Any further work will be tracked under https://github.com/vector-im/wat-internal/issues/55. |
Overview
Create a minimal working session management interface and apply slight polish to the MAS UI overall.
The overall concept of device management in MAS is covered in https://github.com/vector-im/element-meta/blob/develop/docs/device_management.md. Out of the list in that document, we only consider the following requirements here:
name, app version, device ID, created date, web/mobile device type)Minimal changes on the backend will be required for these.
Designs
Figma: https://www.figma.com/file/40ucfibvabgbB1nXvAqxxz/Device-Management-for-EX-%26-MAS?type=design&node-id=97-7629&mode=design&t=HrWqpyBO6v0A0Xez-0
These mock-ups don't reflect the MVP work and will be used as a guideline only.
Compound components will be used where they exist. Due to the time restrictions involved in this project we cannot wait for new components to be created in Compound though. In cases where components have to be built on the MAS side, we've made an agreement to create tracking issues like this one in the Compound repository.
Timeline
We are aiming for the ESS release 23.09.01. The ESS release enters testing on Monday, September 4th, with the public release scheduled for Tuesday, September 12th. We'll need to tag a MAS release with the work we want to include in the ESS release by Friday, September 1st. Critical bug fixing can still happen in the week after.
For dependent projects like EW or Synapse, we need to get things into the RCs for the last release before September 12th.
Tracking
Work on this is tracked on this board. Anything in the To Do column is a requirement for the September 1st deadline. Anything in the Backlog column is nice to have for the deadline.
Scope
The list below is not ordered by priority. Sequencing is reflected in the board only.
Oauth2Client
#1498Time sheeting ⏱️
WEB: Device Manger (Build MAS UI)
The text was updated successfully, but these errors were encountered: