Staff Kubernetes Presence at Kubecon NA

We have a number of roles to organize Kubernetes' participation in Kubecon NA. This includes multiple activities, some of which are related to the maintainer summit and some are not. Some of these roles can even be staffed without being present in Salt Lake City.

For each role we want a lead and a shadow. The lead is expected to have some experience staffing Kubecons, but the shadow is not; they are there to learn the role and be emergency relief if something happens to the lead.

Some roles are currently documented and some are not. All leads & shadows will be responsible for updating or even writing handbooks for their roles.

If you are interested in a role, please reply to this issue with:

1. Which role(s) you are interested in
2. If you expect to be present at Kubecon
3. What previous experience you have at Kubecons/KCS/Maintainer Summit

Contribex will be choosing Leads/Shadows based on qualifications, so please do not hesitate to volunteer for a role that someone else has also already volunteered for.

Roles and shadows:

- [ ] Overall Coordinator/Lead
- [ ] Kubernetes Contributor Activity Comms Lead (remote OK)
- [ ] During Kubecon Social Comms Lead (remote preferred)
- [ ] Meet & Greet Coordinator
- [ ] Contributor Website (remote OK)
- [ ] Contributor Awards Coordinator
- [ ] Kiosk Coordinator (new role)
- [ ] Kubernetes Team F2F Coordinator
- [ ] Onsite NCO Presenter(s)/coordinator + 2 assistants

Some notes on the roles:

Overall Coordinator/Lead: needs prior experience working Kubernetes activities at a Kubecon. Must be at Kubecon. Work starts in June.

Both Comms leads work with all the other roles to help get their requests/messaging out. Comms leads coordinate work done by the whole ContribEx Comms team.

Kubernetes Contributor Activity Comms Lead: solicits participation and keeps community informed about the several contributor-specific activities at Kubecon such as M&G, Awards, etc. Does not need to be at Kubecon, work starts in July and most comms work is done before Kubecon.

During Kubecon Social Comms Lead: coordinates drafting of and publishes many [social media messages about activities during Kubecon](https://docs.google.com/spreadsheets/d/1Hi2K9YGCKceeqnJtO_H_LAUU536_PDRCnHvSuioHAyc/edit?gid=1287379#gid=1287379). It's better if this lead is not at Kubecon to optimize post timing. Lots of prep work in September-October, and then intense work during Kubecon itself.

Meet & Greet Coordinator: [Handbook](https://github.com/kubernetes/community/blob/main/events/events-team/content/meet-and-greet.md). Must be at Kubecon; role starts in July or August.

Contributor Website: Does not need to be at Kubecon. Captures all content, schedules, and changes to Kubecon activities and build out pages on kubernetes.dev to support them. Role starts work in June.

Awards: [Handbook](https://github.com/kubernetes/community/blob/main/events/events-team/content/awards-ceremony.md): Role starts in June/July. Should be present at Kubecon, but there's some flexibility. Could use 2 shadows given the amount of SIG Lead messaging.

Kiosk Coordinator: solicits and coordinates requests from SIGs and subprojects for Project Pavillion Kiosk time, and submits that to CNCF. Role starts in June.

Kubernetes Team F2F Coordinator: Solicits, and if scheduled, coordinates, one or more team/multi-team work sessions for Kubernetes groups and initiatives at Kubecon. Works with the CNCF staff to schedule. Role starts in June.

Onsite NCO Presenter/Coordinator: runs live New Contributor Orientation or related session at Kubecon. Schedule needs to be approved by CNCF. Role requires two assistants/shadows, and planning starts in July/August.

Start with the linked meet-and-greet and awards handbooks, then review the social-media schedule and the contributor website work described in the issue. Volunteer by replying with roles, KubeCon availability, and prior experience; done means assigned leads and shadows have coordinated the activities and updated or created the relevant handbooks.

Written by the indexing model from the issue text.