Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

make a non azure referance implementation

Open
#204 5 comments 10 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
backend, cloud

Research direction

The issue names no files, tests, or entry points. Start by reviewing the repository's REST-source implementation and its Azure dependencies, then define the scope of a self-hosted reference implementation that can be installed without Azure and can serve manifests from a local or specified location.

Written by the indexing model from the issue text.

Description

Issue-Feature
Simplify and homogenize selfhosing

The whole point of winget is to simplify and homogenize the process of packages in windows.
having it rely on azure is counter productive.

should be as simple as installing (either via winget or flathub) and putting the manifest in a location.
Not making ppl feel smart about jumping trough meaningless hoops and venderlocking.

Dominant language
C#
Stars
317
Forks
79
No merged PRs in 30d

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.

More from microsoft/winget-cli-restsource

All issues in microsoft/winget-cli-restsource

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.