microsoft / microsoft/winget-studio

Documentation on obvious missing resources

Open
#132 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Issue-Docs
Dominant language
C#
Stars
67
Forks
15
PR merge metrics
No merged PRs in 30d

Description

Brief description of your issue

There are some scenarios that on the surface seem perfectly reasonable.

  • I want to change my screen resolution
  • I want to change the value "foo" for some application "bar"

Some of these things are clearly resources that should just be a part of Windows.
Some of these things are third-party applications and we'd like to partner with them to support DSC.

Ideally, we would have or build v3 resources for them.
Some of them may have v2 resources available, but they aren't produced by Microsoft, or they have been abandoned.

We should offer some guidance on how to search for resources in WinGet Studio and outside of WinGet studio like how to use the PowerShell gallery to search for them and then go through the links to the project (assuming it's open source).

In some cases it may make sense to add functionality to a v2 resource, in others, it might make sense to build an application/package one could install with WinGet to enable these capabilities. There should be guidance to help folks get through the steep learning curves.

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 repository's documentation structure and the issue's proposed scenarios around screen resolution, application settings, DSC resources, WinGet Studio, and the PowerShell Gallery. Done means providing guidance for finding existing resources, evaluating linked projects, and deciding when to extend or build a resource.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.