kubernetes
[RFC] New Contributor Workshop for KubeCon NA 2022 scope reduction
Describe the issue
Past Up to (and including) 2019 we used to have a full day NCW at every KubeCon event. Slides Some of the challenges with that approach:
- Folks running NCW and Contributor Summit are mostly same people.
- A very small percentage of people attending the NCW ended up contributing later.
Current state There were no workshops in 2020/2021, and at this moment there are no plans to run it again in 2022. However, there's a (somewhat stale) initiative to update slides and create other ways to onboard new developers. (Katacoda, recorded video trainings etc).
Proposed change: Reduce the on-site workshop from a full day event to a 1-2 hour session. (The goal is to still give interested people at least some directions and a chance to ask questions)
Comments/ideas/suggestions? /sig contributor-experience /area new-contributor-track /cc @jberkus @alisondy (Sincere apologies if I've missed anyone else).
IMO, I'd leave this to the meet and greet during the event and NOT as part of the contrib summit proper. The other part of the logistics is having to do new / current contributor reg paths. We had a bunch of people sign up for the NCW in the past that didn't show up but were happy to come to the free social in the evening.
Generally, the Contributor Summit is a Day -1 (monday) event. What about running the NCW on Day 0 (Tuesday)? This would avoid any conflict with the Contributor summit. CNCF would have to have space for it, of course.
If there is room, enough volunteers and bandwidth to run it, I don't see a problem with running one - my gut is leaning towards there won't be though. I know a number of the usual suspects that have run it in the past have other responsibilities that day.
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
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
@jberkus: Closing this issue.
In response to this:
This is not planned for KCSNA 2022.
/close
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.
