Skip to content
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

Add Unconscious Bias Training requirement for Release Team Lead Onboarding #1251

Closed
jeremyrickard opened this issue Sep 21, 2020 · 3 comments · Fixed by #1270
Closed

Add Unconscious Bias Training requirement for Release Team Lead Onboarding #1251

jeremyrickard opened this issue Sep 21, 2020 · 3 comments · Fixed by #1270
Assignees
Labels
area/release-team Issues or PRs related to the release-team subproject kind/feature Categorizes issue or PR as related to a new feature. needs-priority sig/release Categorizes an issue or PR as relevant to SIG Release.
Milestone

Comments

@jeremyrickard
Copy link
Contributor

What would you like to be added:

Add CNCF inclusive speaker training to release lead on-boarding Github issue template.

Additionally, I think we should consider making this a requirement for leads for the other release team roles (enhancements, etc).

Why is this needed:

Ref: kubernetes/community#4940

Steering has added a requirement that chairs and tech leads need to take the CNCF inclusive speaker training:

As you are all aware, the Kubernetes community is both large and diverse. We have folks working on the project from many different backgrounds. Inclusivity is a core value[1] of our project, and we recognize the strength and success that comes from having an environment that is welcoming and respectful to that diversity.

The release team is a small part of the community, but mirrors the diversity of the community. With this in mind, I propose that we add this requirement to release lead on-boarding (and maybe for all sub-team leads?) to help ensure that the release team models these same behaviors.

/area release-team
/milestone 1.20

@jeremyrickard jeremyrickard added kind/feature Categorizes issue or PR as related to a new feature. sig/release Categorizes an issue or PR as relevant to SIG Release. labels Sep 21, 2020
@k8s-ci-robot k8s-ci-robot added the area/release-team Issues or PRs related to the release-team subproject label Sep 21, 2020
@k8s-ci-robot
Copy link
Contributor

@jeremyrickard: The provided milestone is not valid for this repository. Milestones in this repository: [next, v1.16, v1.17, v1.18, v1.19, v1.20, v1.21, v1.22]

Use /milestone clear to clear the milestone.

In response to this:

What would you like to be added:

Add CNCF inclusive speaker training to release lead on-boarding Github issue template.

Additionally, I think we should consider making this a requirement for leads for the other release team roles (enhancements, etc).

Why is this needed:

Ref: kubernetes/community#4940

Steering has added a requirement that chairs and tech leads need to take the CNCF inclusive speaker training:

As you are all aware, the Kubernetes community is both large and diverse. We have folks working on the project from many different backgrounds. Inclusivity is a core value[1] of our project, and we recognize the strength and success that comes from having an environment that is welcoming and respectful to that diversity.

The release team is a small part of the community, but mirrors the diversity of the community. With this in mind, I propose that we add this requirement to release lead on-boarding (and maybe for all sub-team leads?) to help ensure that the release team models these same behaviors.

/area release-team
/milestone 1.20

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.

@jeremyrickard
Copy link
Contributor Author

ooops!

/milestone v1.20

@k8s-ci-robot k8s-ci-robot added this to the v1.20 milestone Sep 21, 2020
@savitharaghunathan
Copy link
Member

As you are all aware, the Kubernetes community is both large and diverse. We have folks working on the project from many different backgrounds. Inclusivity is a core value[1] of our project, and we recognize the strength and success that comes from having an environment that is welcoming and respectful to that diversity.

The release team is a small part of the community, but mirrors the diversity of the community. With this in mind, I propose that we add this requirement to release lead on-boarding (and maybe for all sub-team leads?) to help ensure that the release team models these same behaviors.

+1 to adding the training as a requirement 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/release-team Issues or PRs related to the release-team subproject kind/feature Categorizes issue or PR as related to a new feature. needs-priority sig/release Categorizes an issue or PR as relevant to SIG Release.
Projects
None yet
3 participants