Create a common vocabulary for Remote Development
Problem
Language controls how we think, and it would be a fantastic aid for the team to unify the language we use around Remote Development. We need to be careful not to dictate the future architecture with the terms, but I think the following suggestions might be generic enough.
Suggestion
- legacy WebIDE - the current production Web IDE https://docs.gitlab.com/ee/user/project/web_ide/
- Standalone WebIDE - VS Code for web - replacement of our current legacy WebIDE - not connected to any VS Code server
- Remote Development WebIDE - VS code for web configured in a way that it connects to the remote development environment rather than only using the browser
- RemoteDevelopment Extension for Desktop - something that plugs into the desktop IDE and connects you to the Remote Development Environment
- Remote Development Environment (RDE) - Container or VM that runs in the cloud and it is hosting our IDE server
- Remote Development Environment (RDE) Orchestration - K8S operator or another tool that can spawn new Remote Development Environments
Supporting argument for unifying our vocabulary
-
this will allow us to say things like:
- Tomas is going to focus on understanding how could we connect WebIDE Remote Development Extension to our Remote Development Environment
- Vishal had a look at coder and found out they they solve the Problem of Remote Development Orchestration
- We have a preferred solution for how our Remote Development Environments should look like but we don't know how to Orchestrate them
-
Sources
/cc @ericschurter @oregand @vtak @pslaughter @cwoolley-gitlab
Edited by Tomas Vik