## Problem to solve Developers rely on a variety of language-specific package manager clients to access, build and publish packages. Our vision is to provide a universal package manager, one that integrates with the most commonly used clients and makes them accessible in a single, shared location. Success is defined by our ability to not only support a wide variety of package manager clients, but to provide a consistent, delightful user experience with each integration. ### Goals 1. Ensure we maintain a prioritized, discoverable list of planned integrations for the GitLab Package Registry 1. Expand our list of supported package managers to include the most common programming languages 1. Standardize the implementation and user experience for each integration ## Target audience and experience * [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) ## Outcomes - Increase adoption of the GitLab Package Registry by 30% by covering the most common programming languages ## Further details ### Important decisions - Based on customer requests, we decided to prioritize [Conan](https://gitlab.com/gitlab-org/gitlab/issues/8248) ahead of [NuGet](https://gitlab.com/gitlab-org/gitlab/issues/20050). ### Community contributions - [Composer](https://gitlab.com/gitlab-org/gitlab/issues/15886) is our first integration that is being completed by a member of the GitLab community. We will use this issue as an example and will aim to improve the process to drive future community contributions.