## Problem to solve The GitLab Package Registry is only available in GitLab Premium +, which limits the adoption and usage of this valuable feature. ### Background The goal of the GitLab Package Group is to have 90% of userbase rely on GitLab for all of their package management needs. In order to achieve this goal, we need to both [add support for a wide variety of package manager formats](https://gitlab.com/groups/gitlab-org/-/epics/1245) and build a robust set of features that will be sufficient for our customers to replace their existing package manager vendors. We would like to help drive the adoption of these features so that we can get more feedback on how to improve them and make them even more useful in your everyday workflows. And, as we've been working with the community on contributions for [Composer (PHP)](https://gitlab.com/gitlab-org/gitlab/issues/15886) and [Cargo (Rust)](https://gitlab.com/gitlab-org/gitlab/issues/33060), we've heard several requests move these features to core. ## Proposal As part of GitLab's [stewardship promises](https://about.gitlab.com/company/stewardship/#what-features-are-paid-only), we would like to move the basic functionality for each package manager format to the GitLab Core Edition. This means that for npm, Maven, NuGet, Conan and any future formats, you will be able to: - Establish GitLab as a private repository - Authenticate using your GitLab credentials, personal access or job token - Publish packages to GitLab - Pull packages from GitLab - Search for packages hosted on GitLab - Access an easy-to-use UI that displays package details and metadata and allows you to download any relevant files - Ensure that your contributions are available for ALL GitLab users This epic is intended to detail the work required to migrate the feature to CE and ensure that everything is working properly. ## Target audience * [Delaney (Development Team Lead)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead) * [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer) * [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer) * [Sidney (Systems Administrator)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sidney-systems-administrator) * [Simone (Software Engineer in Test)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#simone-software-engineer-in-test) ## What does success look like, and how can we measure that? Success looks like we increase adoption and usage of the Package Registry by 30% and that we see an increase in the number of community contributions. And that we use the increased feedback and contributions to define and reach a new level of category maturity by the end of 2020. ## Further Information ### Cross-stage benefits - This work will help support file upload for release API https://gitlab.com/gitlab-org/gitlab/issues/17838 in a way that will leverage all the work we did for workhorse object storage acceleration and the effort in https://gitlab.com/gitlab-org/gitlab-ce/issues/59232 ### Technical Requirements #### Front end #### Backend ## Links / references