Skip to content

Remove workspace class preference from user settings and only allow them on project settings #15080

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

Closed
gtsiolis opened this issue Nov 30, 2022 · 0 comments · Fixed by #15091
Closed
Assignees
Labels
component: dashboard feature: workspace classes team: webapp Issue belongs to the WebApp team type: improvement Improves an existing feature or existing code

Comments

@gtsiolis
Copy link
Contributor

Problem to solve

Following up from the relevant RFC (internal) about setting workspace class preference, let’s remove the possibility of setting workspace classes in the user settings and only allow them on projects.

Cc @svenefftinge @jldec @atduarte @Furisto

Proposal

This issue is focusing on the first step described in the relevant RFC:

MVC (Minimal Viable Change)

Step 1) Remove user-level setting for workspace classes, so project-level settings are the only way to change what is picked by default when starting a workspace.

Next Steps

Step 2) Introduce “Start with Options …” where we ask the user on a workspace class to start, to overrule whatever is in project settings.

Step 3) Have .gitpod.yml specify minimum requirements and in case the selected workspace class doesn’t fulfill them ask the user to pick a better one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: dashboard feature: workspace classes team: webapp Issue belongs to the WebApp team type: improvement Improves an existing feature or existing code
Projects
Status: In Validation
Development

Successfully merging a pull request may close this issue.

2 participants