microsoft / microsoft/winget-cli

Regulate tag usage

Open
#2,049 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Issue-Feature
Dominant language
C++
Stars
26.4k
Forks
1.8k
Avg merge
1d 11h
Merged PRs (30d)
15

Description

Description of the new feature / enhancement

I was wondering if I can install ffmpeg through winget, so I searched for ffmpeg and got this and this:

> winget search ffmpeg
Name    Id               Version Match       Source
---------------------------------------------------
Wav2Bar Picorims.wav2bar 0.3.0   Tag: ffmpeg winget
y2mp3   moshfeu.y2mp3    2.5.6   Tag: ffmpeg winget

The two packages that came up are not ffmpeg or alternative ffmpeg frontends.
They might utilize it at some point, but that doesn't mean they should come up when the user searches for ffmpeg.
If you look through the tag lists, there's:

  • audio
  • download
  • electron
  • ffmpeg
  • music
  • webpack
  • youtube
  • video

That almost feels like a form of advertisement?
"Add as many tags as possible to come up in as many searches as possible."

Proposed technical implementation details

Limit tag usage to 1, maybe 2.
Regulate tag usage.

Far as I can tell, tags were introduced to aid the issue of some packages having very specific names, meaning a user might not find it upon searching.
E.g. Foobar2000 could benefit from being searchable with a "foobar" tag, Geforce Now with "geforce," Docker Desktop with "docker."
How would "wav2bar" be useful popping up for "ffmpeg" or "flatpack" or "electron" or "audio"?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the search behavior that surfaces tags, using the cited manifests moshfeu.y2mp3.locale.en-US.yaml and Picorims.wav2bar.locale.en-US.yaml as examples. Define and agree on a tag-count or relevance policy, then verify that unrelated packages no longer appear for searches such as ffmpeg; the issue does not name tests or implementation files.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
cli, search
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.