microsoft / microsoft/winget-cli

Tracking issue for DSC Resources

Open
#3,769 0 comments 8 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-External Command-Configure DSC-Resource Issue-Docs
Dominant language
C++
Stars
26.4k
Forks
1.8k
Avg merge
1d 11h
Merged PRs (30d)
15

Description

Brief description of your issue

As we continue to see more customers using WinGet configuration, there is plenty of external work necessary to have DSC resource for all the packages someone would want to configure on their device(s). I've started to make Issues for some of these projects. I'm also looking longer term into the WinGet Configuration export scenario:

Please add your👍to these issues to show your support/interest, and don't add comments like "+1" or "me too". GitHub issues trigger e-mail notifications, and most users don't want to get e-mail spam if they are following them.

Current requests as of January 17, 2024:

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

Review the linked WinGet Configuration export issue (#3274) and the listed external DSC resource requests. This tracking issue does not identify a repository file, test, or specific implementation target; completion is not defined beyond coordinating or supporting the linked requests.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
cli, devops
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.