microsoft / microsoft/winget-pkgs
Identify community members that usually update specific packages.
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 11.1k
- Forks
- 9.7k
- Avg merge
- 1h 32m
- Merged PRs (30d)
- 376
Description
I like the idea of having designated community members that usually update specific packages. Some people here know a lot about how certain apps install (Visual Studio and Python are two example off the top of my head) and it would be nice to have that written down somewhere. Not to pin responsibility on anyone, of course (anyone can open a PR for anything they want presuming the ISV hasn't claimed the ID), but having a designated .package or .maintainer file that says "@jedieaston knows about this, mention them in issues" wouldn't be a bad idea.
Chocolatey has something similar, see the "Package Maintainers" section to the left of this page.
Originally posted by @jedieaston in https://github.com/microsoft/winget-pkgs/issues/29258#issuecomment-933615046
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the proposed .package or .maintainer file idea and the linked Chocolatey package page for the maintainer information it is intended to capture. The issue names no existing files, tests, or entry points, so determine where package metadata is defined before proposing an implementation and validation approach.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100