kubernetes / kubernetes/community

Checklist for KCEU Meet & Greet

Open
#8,854 3 comments 0 reactions 0 assignees View on GitHub
sig/contributor-experience
Dominant language
Jupyter Notebook
Stars
13k
Forks
5.4k
Avg merge
2d 17h
Merged PRs (30d)
29

Description

### Describe the issue

Checklist issue for the Meet & Greet Team, organized by week:

Week of February 16:

- [ ] Meet with Lindsay, go over logistics/requirements (see below)
- [ ] Merge [PR for M&G page](https://github.com/kubernetes/contributor-site/pull/657)
- [ ] Create issue for M&G attendees to "sign up"
- [ ] Announce M&G to appropriate channels (dev list, chairs-and-tech-leads, kubernetes-org-members, contributor-summit)

Logistics and requirements: need to check on the following things:

* which SIGs/WGs we have in The Box. We have a handful of new WGs, and we just recently retired several WGs.
* get a better map for our page that shows the path from the exhibit hall
* see what other things Lindsay needs

Week of February 23:

- [ ] Check on SIG/WG responses on the issue, make sure that we're not getting a delegation from a SIG/WG we don't have signage for
- [ ] Start trying to recruit 1-2 additional "room proctors" to help direct people as they come in

Week of March 2:

- [ ] Update the M&G handbook to make sure that all of this year's who-does-what is there

Week of March 16:

- [ ] Send out reminder announcement about M&G.
- [ ] Publicize M&G to potential contributors (socials, kubernetes-new-contributors, kubernetes-users)

During Kubecon:

- [ ] One more reminder about M&G on Wednesday morning

M&G Execution

- M&G Team to arrive in room at 11:40 am

/sig contributor-experience
attn: @reylejano

Contributor guide

Open the contributing guide

Research direction

Start by reviewing this checklist, the linked Meet & Greet page PR, and the Meet & Greet handbook. Work through the dated logistics, announcements, SIG/WG responses, and room-proctor coordination, then update the handbook with this year's responsibilities and mark completed items as done.

Written by the indexing model from the issue text.

Assessment

Domain
content, documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.