-
Notifications
You must be signed in to change notification settings - Fork 61
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
Process for Travel support for Kubernetes Contributors #109
Comments
So let's request sig-contribex to come up with a plan: Already requested them on slack: |
@parispittman has a write up in kubernetes/community#3783 |
Thanks for this initiative. :) 💙 |
Draft: #114 |
next steps: @kubernetes/steering-committee - please review |
aim to merge this by August 21st. |
@kubernetes/steering-committee -- let's talk about costs and where funding comes from. Could come from KCS fund. Depends on how things work out for KCS funding. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Travel will be important again one day! |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
/lifecycle frozen |
@idvoretskyi - the last thing I remember here is there was a new box to check on the diversity form that included contributors - what is the current status of this? Is it still a thing? Should we have a separate form for contributors? Let's try and have something in place for May in Valencia. Will put this on the agenda for SC Meeting Monday to get a SC owner to help drive with CNCF. |
@parispittman honestly I don’t recall what was the last status on this - it was years ago :) Let’s catch up on Monday, happy to kick this for Valencia in advance! |
/assign |
cc: @eddiezane |
/assign @parispittman |
Looks like we didn't do this for KubeconEU and ended up with adhoc servicedesk ticket with a bunch of folks. Let's do this for Detroit please? |
CNCFSD-1309 was filed that includes this ask + leads ask for promo codes to give away for recognition to contributors, etc. |
I think we can close this now with the maintainers now being listed as an option under scholarships: what does everyone else think? |
+1 from me too! /pony yay |
In response to this:
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. |
+1 nice! |
See thread:
https://groups.google.com/a/kubernetes.io/d/msg/steering/12g6Ra1fDEs/9v07uRVDBQAJ
The text was updated successfully, but these errors were encountered: