Move the Dependency Proxy to Core
Problem to solve
When determining if a feature should be Paid-only or included in Core, we ask ourselves who benefits from this feature. When considering the Dependency Proxy, it's clear that proxying and caching images from Docker Hub is common practice for all types of organizations and buyers.
In fact, as we consider expanding this feature to allowing proxying and caching of packages from external repositories, such as npmjs.com or maven-central, this functionality should also be included in Core as these are common workflows for all individual contributors.
Ensure that proxying and caching images or packages from the most common public, remote repositories are included in Core, so that Developers can improve the reliability and performance of their builds.
- Docker Hub
- npmjs.com (proxying only)
In the future we'll also support
Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later.
Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/
- Delaney (Development Team Lead)
- Sasha (Software Developer)
- Devon (DevOps Engineer)
- [Simone (Software Engineer in Test)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#simone-
User experience goal
- All GitLab users can reliably proxy and cache images from Docker Hub using the Dependency Proxy