### Problem to solve The GitLab Package Registry allows users to integrate with various package manager clients so they can build, publish and share packages, right from within GitLab. We currently offer support for Maven and npm, but will be adding support for several others, such as NuGet, Conan, rubygems, Linux. We currently leave all of the setup to the user, who may struggle to configure and adopt the integrations due to that extra complexity. ### Intended users - [Software Developer](https://design.gitlab.com/getting-started/personas#persona-sasha) - [DevOps Engineer](https://design.gitlab.com/getting-started/personas#persona-devon) - [Systems Administrator](https://design.gitlab.com/getting-started/personas#persona-sidney) - [Security Analyst](https://design.gitlab.com/getting-started/personas#persona-sam) ### Proposal We will create an easy way to configure and manage package manager integrations for our users. ### Further details <!-- Include use cases, benefits, and/or goals (contributes to our vision?) --> ### Permissions and Security <!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)? --> ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements --> ### Testing <!-- What risks does this change pose? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? See the test engineering process for further guidelines: https://about.gitlab.com/handbook/engineering/quality/guidelines/test-engineering/ --> ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> ### Links / references