-
Notifications
You must be signed in to change notification settings - Fork 7
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
governance role invitations #10
Comments
Hello, I accept all role invitations. Thank you.
|
Thanks for preparing this @jacobweinstock! I accept all role invitations. Thanks. |
Happy to review Infrastructure 💯 |
I the invitation to be a maintainer of Tink! If we're short on folks for any role in cluster-api, I'm happy to help there too |
I accept the reviewer nomination for tinkerbell-docs. |
I accept reviewer invitations for pbnj, ipxedust, hook and lint-install. Thank you! |
I accept being a reviewer for hook. |
awesome, thank you. @displague, you are a maintainer for CAPT, up to you if you would like to nominate. No objections from me. See the FAQ above on "What should be done if a role or roles in a repo are "short-staffed"?" |
Definitely appreciated and accepted, @micahhausler |
I accept being a reviewer for Tink |
Hey. @displague. To which role in CAPT would you like me to add Micah? |
I can definitely help out with docs! I accept being a maintainer for |
I accept my roles. |
I accept being |
I accept the following role invitations:
|
I accept review |
I accept review For |
I accept the approver role for |
@micahhausler's interest in maintainership of capt matches the commitment level on tink - it's great to see! (sgtm) |
I formally accepted my roles ! |
I'd like to tender myself for consideration as a maintainer of Hegel. I recognize its slightly premature but figured I would throw it out there given the refactoring I'm doing (lots more to come). |
I'm all for it! The process during this one time bootstrap event calls for the maintainers (@nshalman and @mmlb) to make this type of call though. |
I accept my role invitations for boots and hook. |
I accept for boots & dhcp. |
I accept the reviewer nomination for hegel. :) |
I accept my role invitations |
I accept my role invitations. |
Hi Jacob - I accept my reviewer role for |
I accept my role invitations.
|
I accept my role nomination for hub reviewer. Thanks! |
This is needed to enable the repo roles defined by the community here: tinkerbell/org#10 Signed-off-by: Jacob Weinstock <[email protected]>
This is needed to enable the repo roles defined by the community here: tinkerbell/org#10 Signed-off-by: Jacob Weinstock <[email protected]>
This is needed to enable the repo roles defined by the community here: tinkerbell/org#10 Signed-off-by: Jacob Weinstock <[email protected]>
This is needed to enable the repo roles defined by the community here: tinkerbell/org#10 Signed-off-by: Jacob Weinstock <[email protected]>
This is needed to enable the repo roles defined by the community here: tinkerbell/org#10 Signed-off-by: Jacob Weinstock <[email protected]>
This is needed to enable the repo roles defined by the community here: tinkerbell/org#10 Signed-off-by: Jacob Weinstock <[email protected]>
## Description This is needed to enable the repo roles defined by the community here: tinkerbell/org#10 ## Why is this needed Fixes: # ## How Has This Been Tested? ## How are existing users impacted? What migration steps/scripts do we need? ## Checklist: I have: - [ ] updated the documentation and/or roadmap (if required) - [ ] added unit or e2e tests - [ ] provided instructions on how to upgrade
## Description This is needed to enable the repo roles defined by the community here: tinkerbell/org#10 ## Why is this needed Fixes: # ## How Has This Been Tested? ## How are existing users impacted? What migration steps/scripts do we need? ## Checklist: I have: - [ ] updated the documentation and/or roadmap (if required) - [ ] added unit or e2e tests - [ ] provided instructions on how to upgrade
## Description This is needed to enable the repo roles defined by the community here: tinkerbell/org#10 ## Why is this needed Fixes: # ## How Has This Been Tested? ## How are existing users impacted? What migration steps/scripts do we need? ## Checklist: I have: - [ ] updated the documentation and/or roadmap (if required) - [ ] added unit or e2e tests - [ ] provided instructions on how to upgrade
## Description This is needed to enable the repo roles defined by the community here: tinkerbell/org#10 ## Why is this needed Fixes: # ## How Has This Been Tested? ## How are existing users impacted? What migration steps/scripts do we need? ## Checklist: I have: - [ ] updated the documentation and/or roadmap (if required) - [ ] added unit or e2e tests - [ ] provided instructions on how to upgrade
## Description This is needed to enable the repo roles defined by the community here: tinkerbell/org#10 ## Why is this needed Fixes: # ## How Has This Been Tested? ## How are existing users impacted? What migration steps/scripts do we need? ## Checklist: I have: - [ ] updated the documentation and/or roadmap (if required) - [ ] added unit or e2e tests - [ ] provided instructions on how to upgrade
## Description This is needed to enable the repo roles defined by the community here: tinkerbell/org#10 ## Why is this needed Fixes: # ## How Has This Been Tested? ## How are existing users impacted? What migration steps/scripts do we need? ## Checklist: I have: - [ ] updated the documentation and/or roadmap (if required) - [ ] added unit or e2e tests - [ ] provided instructions on how to upgrade
This is needed to enable the repo roles defined by the community here: tinkerbell/org#10 Signed-off-by: Jacob Weinstock <[email protected]>
This is needed to enable the repo roles defined by the community here: tinkerbell/org#10 Signed-off-by: Jacob Weinstock <[email protected]>
## Description This is needed to enable the repo roles defined by the community here: tinkerbell/org#10 ## Why is this needed Fixes: # ## How Has This Been Tested? ## How are existing users impacted? What migration steps/scripts do we need? ## Checklist: I have: - [ ] updated the documentation and/or roadmap (if required) - [ ] added unit or e2e tests - [ ] provided instructions on how to upgrade
## Description This is needed to enable the repo roles defined by the community here: tinkerbell/org#10 ## Why is this needed Fixes: # ## How Has This Been Tested? ## How are existing users impacted? What migration steps/scripts do we need? ## Checklist: I have: - [ ] updated the documentation and/or roadmap (if required) - [ ] added unit or e2e tests - [ ] provided instructions on how to upgrade
## Description <!--- Please describe what this PR is going to change --> This is needed to enable the repo roles defined by the community here: tinkerbell/org#10 ## Why is this needed <!--- Link to issue you have raised --> Fixes: # ## How Has This Been Tested? <!--- Please describe in detail how you tested your changes. --> <!--- Include details of your testing environment, and the tests you ran to --> <!--- see how your change affects other areas of the code, etc. --> ## How are existing users impacted? What migration steps/scripts do we need? <!--- Fixes a bug, unblocks installation, removes a component of the stack etc --> <!--- Requires a DB migration script, etc. --> ## Checklist: I have: - [ ] updated the documentation and/or roadmap (if required) - [ ] added unit or e2e tests - [ ] provided instructions on how to upgrade
Signed-off-by: Micah Hausler <[email protected]> ## Description Add CODEOWNERS based on tinkerbell/org#10 ## Why is this needed Allows additional folks to review and approve changes
@jacobweinstock What's left to do so we can close? |
The previously maintained (now outdated) GitHub Teams for The probot monitored .github/settings.yml lists are now authoritative. |
We'll want to add https://github.com/tinkerbell/tinkerbell.org to the list of projects under governance. |
This is needed to enable the repo roles defined by the community here: tinkerbell/org#10 Signed-off-by: Jacob Weinstock <[email protected]>
## Description This is needed to enable the repo roles defined by the community here: tinkerbell/org#10 ## Why is this needed Fixes: # ## How Has This Been Tested? ## How are existing users impacted? What migration steps/scripts do we need? ## Checklist: I have: - [ ] updated the documentation and/or roadmap (if required) - [ ] added unit or e2e tests - [ ] provided instructions on how to upgrade
Tinkerbell Role Bootstrapping
The following is the proposal for role bootstrapping. See the governance (here) for definitions, details, responsibilities, etc on each role.
Response Requested
To accept or decline a role, please comment in this issue with the repository and role name, and whether you accept this role or not.
Implementation Details
Each person was selected for a role based on their contributions and history in the repo. Load in other areas of the Tinkerbell project was also taken into account. Contributions were pulled from the CNCF's devstats tool. The script found here was used to get the data.
FAQ
What if I don't want to have a role?
What if I wanted to have a specific role but I'm not?
What if I'm not even a member of the Tinkerbell org?
What should be done if a role or roles in a repo are "short-staffed"?
Response Tracking
List of all people invited to a role. A checked box indicates the individual has responded to the invitation.
The text was updated successfully, but these errors were encountered: