Align terminology between Pods, Workspaces, and Remote Development
Problem to solve
We have four groups working on features or areas that deal with some aspect of a "space" as it relates to an organizational concept.
- The Manage::Workspaces group working on creating a top-level organizational structure that will organize and control the inheritance of settings/features and consolidating groups and projects.
- The Pods group working on a long-term horizontal scaling solution
- The Remote Development category bringing on-demand development environments to the cloud
- Fulfillment is working on a proposal for a data architecture that would need to align to the same concepts
Proposal
Align on distinct and descriptive terminology for each group to prevent customer confusion.
As proposed by @fzimmer in gitlab-org/gitlab!102172 (comment 1152645763), we would end up with something like
graph TD
subgraph two[Remote Development]
G[Workspace]
H[Workspace]
end
subgraph one[GitLab Hierarchy]
A[Organization] --> B
A --> C
B[Group] --> E
C[Group] --> D
D[Sub-group]
E[Sub-group] --> F
F[Project]
end
The current Pods and Workspaces groups would align on Organization
as the term for the top-level construct. Remote Development would adopt the term Workspace
to describe the individual development environments.
Approvals
-
@fzimmer -
@ofernandez2 -
@lohrc -
@uchetta -
@sarahwaldner -
@ericschurter -
@ogolowinski -
@david -
@mnichols1 -
@mvanremmerden
Links
- More details on the proposal by the Remote Development group to adopt the term
Workspace
can be found in Proposal: Adopt Workspace terminology for Remot... (#5129 - closed) - User research on naming was completed and reinforces the proposed terminology
Edited by David DeSanto