Below is our guidance for how to report issues, propose new features, and submit contributions via Pull Requests (PRs).
The Windows Package Manager team is active in this GitHub Repository. In fact, we live in it all day long and carry out all our development in the open!
When the team finds issues we file them in the repository. When we propose new ideas or think-up new features, we file new feature requests. When we work on fixes or features, we create branches and work on those improvements. And when PRs are reviewed, we review in public - including all the good, the bad, and the ugly parts.
The point of doing all this work in public is to ensure that we are holding ourselves to a high degree of transparency, and so that the community sees that we apply the same processes and hold ourselves to the same quality-bar as we do to community-submitted issues and PRs. We also want to make sure that we expose our team culture and "tribal knowledge" that is inherent in any closely-knit team, which often contains considerable value to those new to the project who are trying to figure out "why the heck does this thing look/work like this???"
The team triages new issues several times a week. During triage, the team uses labels to categorize, manage, and drive the project workflow.
We employ a bot to help us automate common processes within our workflow.
We drive the bot by tagging issues with specific labels which cause the bot engine to close issues, merge branches, etc. This bot engine helps us keep the repository clean by automating the process of notifying appropriate parties if/when information/follow-up is needed, and closing stale issues/PRs after reminders have remained unanswered for several days.
Therefore, if you do file issues, or create PRs, please keep an eye on your GitHub notifications. If you do not respond to requests for information, your issues/PRs may be closed automatically.
Please do not report security vulnerabilities through public GitHub issues. Instead, please report them to the Microsoft Security Response Center (MSRC). See SECURITY.md for more information.
Please follow this simple rule to help us eliminate any unnecessary wasted effort & frustration, and ensure an efficient and effective use of everyone's time - yours, ours, and other community members':
👉 If you have a question, think you've discovered an issue, would like to propose a new feature, etc., then find/file an issue BEFORE starting work to fix/implement it.
Before filing a new issue, search existing open and closed issues first: This project is moving fast! It is likely someone else has found the problem you're seeing, and someone may be working on or have already contributed a fix!
If no existing item describes your issue/feature, great - please file a new issue:
- Don't know whether you're reporting an issue or requesting a feature? File an issue
- Have a question that you don't see answered in docs, videos, etc.? File an issue
- Want to know if we're planning on building a particular feature? Create a discussion
- Got a great idea for a new feature? File an issue/request/idea
- Don't understand how to do something? Create a discussion
- Found an existing issue that describes yours? Great - upvote and add additional commentary / info / repro-steps / etc.
When you hit "New Issue", select the type of issue closest to what you want to report/ask/request:
Complete the information requested in the issue template, providing as much information as possible. The more information you provide, the more likely your issue/ask will be understood and implemented. Helpful information includes:
👉 Tip: Run the following command
winget --info
If the report is related to a specific DSC Resource, it is also helpful to specify the PowerShell version, PowerShell module and DSC resource as well as any additional information regarding how the resource is being called (winget configure, Invoke-WinGetConfiguration,etc.). The calling context is also important (system context "session 0", "user", "elevated user").
- What tools and apps you're using (e.g. VS 2019, VSCode, etc.)
- Don't assume we're experts in setting up YOUR environment and don't assume we are experts in
<your distro/tool of choice>. Teach us to help you! - We LOVE detailed reproduction steps! What steps do we need to take to reproduce the issue? Assume we love to read reproduction steps. As much detail as you can stand is probably barely enough detail for us!
- Prefer error message text where possible or screenshots of errors if text cannot be captured.
- We MUCH prefer text command-line script than screenshots of command-line script.
- If you intend to implement the fix/feature yourself then say so! If you do not indicate otherwise we will assume that the issue is our to solve, or may label the issue as
Help-Wanted.
⚠ DO NOT post "+1", "me too", or similar comments - they just add noise to an issue.
If you don't have any additional info/context to add but would like to indicate that you're affected by the issue, upvote the original issue by clicking its [+😊] button and hitting 👍 (+1) icon. This way we can actually measure how impactful an issue is.
For those able & willing to help fix issues and/or implement features ...
Some issues/features may be quick and simple to describe and understand. For such scenarios, once a team member has agreed with your approach, skip ahead to the section headed "Fork, Branch, and Create your PR", below.
Small issues that do not require a spec will be labelled Issue-Bug or Issue-Task.
However, some issues/features will require careful thought & formal design before implementation. For these scenarios, we'll request that a spec is written and the associated issue will be labeled Issue-Feature.
Specs help collaborators discuss different approaches to solve a problem, describe how the feature will behave, how the feature will impact the user, what happens if something goes wrong, etc. Driving towards agreement in a spec, before any code is written, often results in simpler code, and less wasted effort in the long run.
Specs will be managed in a very similar manner as code contributions so please follow the "Fork, Branch and Create your PR" below.
To write/contribute to a spec: fork, branch and commit via PRs, as you would with any code changes.
Specs are written in markdown, stored under the /doc/specs folder and named [issue id] - [spec description].md.
👉 It is important to follow the spec templates and complete the requested information. The available spec templates will help ensure that specs contain the minimum information & decisions necessary to permit development to begin. In particular, specs require you to confirm that you've already discussed the issue/idea with the team in an issue and that you provide the issue ID for reference.
Team members will be happy to help review specs and guide them to completion.
Once the team have approved an issue/spec, development can proceed. If no developers are immediately available, the spec can be parked ready for a developer to get started. Parked specs' issues will be labeled "Help Wanted". To find a list of development opportunities waiting for developer involvement, visit the Issues and filter on the Help-Wanted label.
Once you've discussed your proposed feature/fix/etc. with a team member, and you've agreed an approach or a spec has been written and approved, it's time to start development. There are two flows you can follow depending on the proposed feature or fix.
If you're feature (or module) has not yet been created, follow these steps:
- Fork the repository if you haven't already.
- Clone your fork locally.
- Open a PowerShell terminal session and execute:
.\utilities\tools\New-DscResourceModule.ps1 -DscResourceModule '<moduleName>' -Description 'DSC Resource for <description>' - Work on your changes and write tests.
- Build and test to see if it works.
- Create & push a feature branch.
- Create a Draft Pull Request (PR).
- If you are finished with your changes and you want a review, change the state.
Tip
Don't forget to add the DscResourcesToExport and Tags.
When you are working on a fix or you want to add additional features to an existing module, you can follow the below steps:
- Fork the repository if you haven't already.
- Clone your fork locally.
- Work on your fix or feature, and optionally write tests
- Build and test to see if it works.
- Create & push a feature branch.
- Create a Pull Request (PR) when you are finished with your changes
Testing is a key component in the development workflow.
When you'd like the team to take a look, (even if the work is not yet fully-complete), mark the Draft PR as 'Ready For Review' so that the team can review your work and provide comments, suggestions, and request changes. It may take several cycles, but the end result will be solid, testable, conformant code that is safe for us to merge.
Caution
Remember: changes you make may affect both the Windows Package Manager and the schema support implemented in our validation pipelines! Because of this, we will treat community PR's with the same level of scrutiny and rigor as commits submitted to the official Windows source by team members and partners.
Once your code has been reviewed and approved by the requisite number of team members, it will be merged into the main branch. Once merged, your PR will be automatically closed.
Thank you in advance for your contribution! Now, what's next on the list? 😜