community
community copied to clipboard
kubernetes
Leadership Training Topics and Possible Trainers
Building off of this #3662 issue. We have the channels and platforms now but we don't really have the training program just yet. If you are a chair or tech lead that would be interested in any of the below topics, please comment so we can gather interest.
Channels/Platforms: #chairs-and-techleads (k8s slack) monthly sig/wg chair/tl meeting (kubernetes) maintainers circle (cncf; all maintainers) zoom KubeCon
Each has a thread of leadership training, peer mentoring, and minor activities that you would get with a program but it's still not a substitute for deep dives on concepts and paid training.
Possible trainers:
- https://www.zingtrain.com/training/ - recommended; has done OSS training before. ~30 people per round.
- https://growthcoachinginstitute.io - past KubeCon talks; currently has an open proposal to do maintainers circles for cncf - up to 50 per round
- Dr Jill Castro, umich counselor that specializes in these topics and has experience in open source; tbd on capacity
- @LappleApple - tbd
- https://techlead.academy/p/systems-thinking-fundamentals
Topics/Concepts/Deep Dive areas:
- consent
- code of conduct response training
- managing during grief and loss
- consensus building and decision making
- community building and outreach
- unconscious bias
You might also want to check out Patrick Kua's offerings:
- https://techlead.academy/p/systems-thinking-fundamentals
- https://www.thekua.com/tech-lead-course/
I suggested Patrick earlier ^^. This looks good: https://techlead.academy/p/systems-thinking-fundamentals
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Mark this issue or PR as rotten with
/lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
Since the general interest seems high: Do we have any update on this?
/remove-lifecycle stale
@saschagrunert I'm swamped but if anyone reading this would like to help out, please do. The next steps would be to get a quote from the above and work out a package. After, we will need to do a funding request through Steering Committee.
/help new contributors may have a hard time with this one and thus not putting good-first-issue
@parispittman: This request has been marked as needing help from a contributor.
Guidelines
Please ensure that the issue body includes answers to the following questions:
- Why are we solving this issue?
- To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
- Does this issue have zero to low barrier of entry?
- How can the assignee reach out to you for help?
For more details on the requirements of such an issue, please see here and ensure that they are met.
If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.
In response to this:
@saschagrunert I'm swamped but if anyone reading this would like to help out, please do. The next steps would be to get a quote from the above and work out a package. After, we will need to do a funding request through Steering Committee.
/help new contributors may have a hard time with this one and thus not putting good-first-issue
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
/assign @tpepper @parispittman
...to add some effort focus as the new year starts.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Mark this issue or PR as rotten with
/lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale