-
-
Notifications
You must be signed in to change notification settings - Fork 15k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
team-list: establish categorization team #362938
team-list: establish categorization team #362938
Conversation
32b390d
to
c13c09b
Compare
This comment was marked as resolved.
This comment was marked as resolved.
c13c09b
to
a1c70d3
Compare
Added :) |
a1c70d3
to
77aadf3
Compare
Created a GitHub team and linked it to the team created by this PR. Update: winterqt has added it to the repository with the |
59c085b
to
c107d7c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Excited to see what comes out of this :)
Seems fine to me — but is everyone in the proposed team review-requested (or has already reacted here)? It looks like not enough review requests. |
I requested most of the reviews but missed one. If I recall correctly, the people added here have already expressed interest in joining the team, but let's wait for approvals from everyone before we merge this. |
c107d7c
to
30fa116
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
Would it be reasonable to remove anyone who doesn't respond by the start of next week (2024-12-15)? I think we're supposed to have the approvals of everyone listed on this team, but I'm not confident we'll get a response from everyone. We can always add people to the team after this PR. |
I look forward to seeing what we can accomplish here |
Currently just waiting on a response from @fgaz. |
I'll be on the team, if you'll have me. Information architecture is quite important. |
Per RFC 146: https://github.com/NixOS/rfcs/blob/master/rfcs/0146-meta-categories.md#categorization-team > "a team entrusted with authority to manage issues related to categorization and carry their corresponding duties"
30fa116
to
af682f3
Compare
Merging this as we have gathered all approvals 🚀 |
Important
If you want to be on the team initially, please comment by 2024-12-15 (we will remove non-responsive initial team members after this deadline). We can add interested people to the team later, if they are still interested.
Per RFC 0146:
https://github.com/NixOS/rfcs/blob/master/rfcs/0146-meta-categories.md#categorization-team
I added people to the team who were pinged in the below tracking issue, sorted alphabetically; the list of members is not set in stone.
Tracking: #360727
I requested reviews from the shepherd team for the RFC, as well as the creator of the above tracking issue.
I think it's reasonable to make shepherd reviews (at least from Raskin, the lead) blocking. Other reviews are, of course, appreciated.
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.