Rename Auto DevOps
Description
Sid suggested renaming Auto DevOps to PaaS (or GitLab PaaS) as the current name is awkward and no one likes it, but PaaS is a well-known term and (potentially) more accurate. I'm not convinced, but I think it's worth discussing.
In particular, in what ways is Auto DevOps currently deficient to be called a PaaS? Can we get away with calling it a PaaS anyway and aspiring to fill in the rest? Is it just a bad PaaS today, and we'll iterate?
Missing
- Pod logs (MVC 10.7)
- Consolidated logs (not scheduled)
- Idling
- Domain name management
- Cluster experience
- Herokuish is slow (cloud native PaaS should build a native Dockerfile instead)
- It is not managed (although Deis and Cloud foundry are not managed as well)
In what ways is it more than a PaaS and calling it a PaaS wouldn't do it justice? Do those ways really matter? Or is it just a better PaaS?
One benefit of calling it a PaaS is that it clarifies its future direction. We'll know better how to evolve Auto DevOps. And the public will know where we're headed as well. I mean, internally, we've known we're going towards offering a PaaS, but it isn't exactly clear to everyone (internally or externally) that we're doing that, or how we're going to get there.
My gut feeling is that while shipping small iterations is great in general, Auto DevOps is so far away from a PaaS that it would actually backfire to call it that today.