Specifying codeowners?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- developer-experience
Research direction
Start with the linked pull request discussion, especially the point raised by @Smaug123, and review how nixpkgs models maintainers and codeowners. Determine what ownership model this repository should adopt and document or implement the agreed approach.
Written by the indexing model from the issue text.
Description
Looking at https://github.com/NixOS/templates/pull/58#discussion_r1065174752, @Smaug123 raises a good point. It doesn't make sense for folks submitting a new template to add themselves as a codeowner unless they're also given commit access to this repo. Would it make more sense to adopt the maintainer's model that nixpkgs uses?
- Dominant language
- Nix
- Stars
- 768
- Forks
- 104
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from NixOS/templates
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
[Rust template] Clang errorPossibly taken @tomberek claimed this 55 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/vscode-containers#655 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
pylint-dev/pylint#11791 ·
Maintainers usually reply within 1 day
-
Document and enforce pull request review guidelinesPossibly taken @dashorst claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
bug implicit-state
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Misleading 'Update → Config → Hyprland' menu item silently resets user configs without confirmationOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day