Validate and update documentation for how to add new package managers to GitLab

Problem to solve

The goal of the Package group is to build a set of features that, within three years, will allow ninety percent of our customers to store all of their packages and artifacts in GitLab. In order to accomplish this goal we will need to continue to expand our list of supported package manager integrations.

However, we are limited in how many we can reasonably prioritize and build in a timely fashion. If we want to accomplish our aggressive goal, we will need to leverage the power of the GitLab community to help build new integrations. In order empower our users, we must create documentation that details how to add a new integration, expected challenges and key decisions.

Further details

• Epic for adding new package managers
• Existing documentation

Use cases

• A developer interested in adding a new package manager integration can discover and use the documentation to get started on an MR.
• GitLab identifies principles and best practices in implementing support for new package managers. (authentication, group v instance level, naming conventions)

Intended audience

• Software Developers

Proposal

Validate and update (if needed) and documentation that provides a step-by-step process for how to add a new package manager to GitLab. The documentation should clearly state our preferences for authentication, group/instance/sub-group support and how to best handle naming conventions.

Who can address the issue

• This will need to be created by the Package team, who are responsible for building and maintaining this code.

Other links/references