Remove `PaaS` category and add `Infrastructure as Code` for Configure stage
Remove the "PaaS" category and add a new Infrastructure as Code
category for the configure stage. Relevant discussion here https://gitlab.com/gitlab-org/gitlab-ce/issues/63151.
Summary for Removing PaaS
Product initially had intent to rename the PaaS
category to either Application Development Platform
or DevOps Platform
, in order to better align to its intent. In conversation between product and marketing (meeting notes), marketing expressed intent to use the verbiage "platform" to describe GitLab (ie. GitLab = DevOps platform delivered as a single application).
Because the PaaS
term incorrectly led some users to believe we were going to provide compute services and some of the features planned for it aligned better with other categories (such as Kubernetes
and Auto DevOps
) it will be better to re-distribute those features into existing categories and eliminate the PaaS
category. In conclusion, marketing will work to build on the "DevOps platform" messaging at a top level, PMM will publish "PaaS-like" use-cases, and product will remote PaaS
category and add a new Infrastructure as Code
category.
Summary for Adding Infrastructure as Code
After discussion with @sytses at investor meetings, we'd like to propose the replacement of PaaS with Infrastructure Management (later renamed directly to Infrastructure as Code) to cover IaC and integration with Terraform.
/cc @twbarr @markpundsack @sfwgitlab @williamchia
-
CEO - @sytses -
VP of Product - @sfwgitlab -
VP of Product Strategy - @markpundsack -
Director of Product - @kencjohnston -
Director of Engineering - @dhavens
Informed
- Senior Director of Development - @clefelhocz1
- Director of Quality - @meks
- VP of Engineering - @edjdev