-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
KubeCon EU Maintainer Summit 2025 - Team Staffing #8217
Comments
@mfahlandt: The label(s) 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-sigs/prow repository. |
We might need a new label |
I can lead the SIG Meet & Greet, I shadowed SIG Meet & Greet for KubeCon NA 2024 |
I'd like to shadow for SIG Meet and Greet :) I'll be present at London. |
@lauralorenz was shadowing awards at NA24 and I'd like to nominate Laura as a lead for Awards in EU25. Happy to shadow awards/registration and/or anywhere else. |
I'd like to shadow for SIG Meet and Greet :) |
I am very much Interested to volunteer on the KubeCon EU. I will be
attending the event and a Kubestronaut.
…On Tue, Dec 17, 2024, 2:15 AM Lavish Pal ***@***.***> wrote:
I'd like to shadow for SIG Meet and Greet :)
However, I won’t be able to attend KubeCon in person this time. I’m still
very eager to contribute and learn through the process remotely, if that’s
possible
—
Reply to this email directly, view it on GitHub
<#8217 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFYTJL5XIBH6PUVETAYGQJ32F7MTZAVCNFSM6AAAAABTXHKK22VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBXG43DIMRUGI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Will there be a need for Operations folks this time around? |
The 2025 NA Maintainer Summit in London will need staffing for its roles and shadows.
It will happen at 31st of March 2025 in London Excel London
Royal Victoria Dock, 1 Western Gateway, London E16 1XL, United Kingdom
Event Lead will be @mfahlandt
We will also need shadows that could potentially take on leading those roles in the future. Roles and shadows will be listed below when they are filled out. With limited exception, shadows must have Kubernetes org membership. Shadows will be accepted at the discretion of the lead.
To clarify roles and responsibilities, we are adding a role of "Volunteer" under each area. The Shadow bears expectations to lead one of the events-team roles in an upcoming summit and to handle all lead related activities in the absence of the Lead. It may be helpful to think of the Shadow role as an understudy position. Volunteers are helpers that may be assigned tasks from the Lead. Shadows and Volunteers, with limited exception, must be members of the Kubernetes GitHub organization. Leads are still responsible for accepting shadows and volunteers for their area. Volunteers, please communicate your desire to be a Shadow to the Lead of your area. Leads will inform me of their Shadows and I will update the issue.
As this will be a first time Maintainer Summit we still will need to figure out certain roles and what to do about it. Comments and critique is welcome.
For now, we decided to go with a smaller stack of roles.
The need for a meeting is still to be discussed.
@natalisucks & @angellk & @mfahlandt are the overall chairs for the maintainer summit.
Thank you for your willingness to help out. We could not hold these events without you.
The program committee for the Kubernetes track was pre chosen by ContribEx
Committee Chairs: @katcosgrove, @jberkus
Committee Members: @ArvindParekh, @jeremyrickard, @tabbysable, @qedrakmar, @sandeepkanabar, @savitharaghunathan, @soltysh, @stmcginnis
Comms
Lead:
Shadow: @wendy-ha18
Volunteers:
Website:
Design:
TBD Awards
Lead:
Shadow:
SIG Meet & Greet (Preferred onsite in London)
Lead:
Shadow:
Volunteers:
Emeritus Advisor:
/assign @mfahlandt
/sig contributor-experience
/area maintainer-summit
/area EU-summit
The text was updated successfully, but these errors were encountered: