Add frequently requested, coming soon package manager formats to the Package Registry UI

Problem to solve

As the PM for the Package stage, I frequently hear the same requests from users and customers for adding support for the most common package manager formats. Typically, I share the issue with them and invite them to upvote or start a community contribution. However, this only addresses the folks that will reach out and ask the question. We do not let users know in the application that these integrations are coming soon our that we are looking for contributions.

Intended users

• Delaney (Development Team Lead)
• Sasha (Software Developer)
• Devon (DevOps Engineer)
• Sidney (Systems Administrator)

Proposal

For our most commonly requested package manager formats, add in tabs to the Packages--> List view, link to the issues and invite contributions.

Data to include

• Title w/ Package Manager
• Current status
• Core issue (or epic?)
• Either an active MR related to it or "open for contributions"

Proposed list of formats

Add tabs for:

• Composer (PHP)
• PyPi (Python)
• Debian (Linux)
• RPM (Linux)
• Rubygems (Ruby)
• Go

Permissions and Security

• There are no permissions changes required for this change

Documentation

• There are no documentation changes required for this change

What does success look like, and how can we measure that?

• The goal of this will be to measure how often people are navigating to this page and clicking on the links to the issues and/or documentation. This will allow us to have an additional data point, other than upvotes or customer phone calls. And hopefully, we will drive community contributions.

Measurement

• Count page views over time for each tab
• Count number of clicks on links to issue and or documentation
• Use the above as an additional sensing mechanism.

Links / references