Becoming a Maintainer #79979
-
Hi @ItzLevvie it's been a while, I know it's a bit awkward posting this due to the fact that I asked this question 3 months ago. I now have a bit of free time on my hands though, which is why I wanted to ask if it's possible for me to become a maintainer of the WinGet repository? Why Do I Want to Do This?I've really open and wanting to do this for a while now because I like the idea of communities and giving back to people. Why Do I Think I'm Suitable for This?I'm great at following specifications, directions and love looking over what people have done and giving feedback to them. If you have any thoughts just leave them below because I'd love to hear them. Looking forward to discussing this with and hearing from you or one of the other maintainers, |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 5 replies
-
If you want to help the community and want to approve PRs, you might have to use the term, "Moderator". Here, a maintainer is referred to as a person/organization who maintains a particular application/software/package, its versions, and metadata. You can also get help at the chat: https://gitter.im/Microsoft/winget-pkgs. Related Discussions:
|
Beta Was this translation helpful? Give feedback.
-
@AlexDev404 welcome to the Windows Package Manager community! There are many different ways to contribute. These range from helping to support users who are reporting bugs or helping us to reproduce errors (if we don't have good steps) through to making product contributions in the form of Pull Requests (PRs) to implement Issues (features) or fixing bugs. And it's not limited to just those activities. There are many different facets to the product. We have repositories for generating manifests with the Windows Package Manager Manifest Creator, submitting packages to the Windows Package Manager Community Repository, a reference implementation for a REST source, and the WinGet client. There are also several tools utilities and documents distributed throughout these repositories. There are no requirements to become a moderator or a maintainer in order to make an impact on the product or the catalog of packages available for customers. In fact, we've had several important contributions from the community at large. All we ask is to adhere to our code of conduct and the contributing guidelines (usually CONTRIBUTING.md in the root directory for each repository). Some of my favorite contributions have come from someone simply noticing a typo or an ambiguous sentence in documentation here at GitHub and at Microsoft Docs. Another important area is helping triage new Issues. Sometimes a duplicate Issue is being reported, and it helps to let the author know where to put their 👍 to help raise priority. Other times, there may already be a workaround or a solution to a problem. We welcome constructive feedback on the product, the specifications, and PRs. |
Beta Was this translation helpful? Give feedback.
@AlexDev404 welcome to the Windows Package Manager community! There are many different ways to contribute. These range from helping to support users who are reporting bugs or helping us to reproduce errors (if we don't have good steps) through to making product contributions in the form of Pull Requests (PRs) to implement Issues (features) or fixing bugs. And it's not limited to just those activities.
There are many different facets to the product. We have repositories for generating manifests with the Windows Package Manager Manifest Creator, submitting packages to the Windows Package Manager Community Repository, a reference implementation for a REST source, and the WinGet client. There…