KCD Organizer Checklist

Please fill in information, organizers, and sponsors as you assemble them, and then make a new comment when this application is ready for review.

[ ] Event Location:
[ ] Event Date and Time:
[ ] Expected Number of Attendees
[ ] Event cost per ticket, and if you will have early bird pricing or not
Event type:
[ ] Virtual
[ ] Hybrid
[ ] In person
Organizers Details (identify who will be the CFP admin, as well as the finanical officer)
[ ] Organizer 1: First and Last Name, Company, Title, Email, CNCF Slack Username
[ ] Organizer 2: First and Last Name, Company, Title, Email, CNCF Slack Username
[ ] Organizer 3: First and Last Name, Company, Title, Email, CNCF Slack Username

[ ] No other Kubernetes Community Day event in same major city (check with past organizers)
[ ] Minimum of 3 organizers from 3 different organizations
[ ] Every organizer has an account on Cloud Native Community Groups
[ ] Each organizer lives in or just outside of the KCD location
[ ] At least one organizer is a CNCF member employee, CNCF ambassador, or CNCF project maintainer
[ ] All organizers agree to follow the event guidelines and CNCF Code of Conduct
[ ] All inquiries / communication to come via GitHub (comment under your KCD issue) for easy tracking
[ ] All organizers have taken Inclusive Open Source Community Orientation (LFC102)
[ ] Agree to offer at least 3 complimentary tickets to increase diversity for the event
[ ] Share the sponsor prospectus with CNCF via your GitHub issue, and link it on your website.
[ ] Agree to ensure the final program schedule is diverse (e.g., not all speakers of one gender, one culture, or from 1 or 2 of the same company). Here are some tips on how to create a diverse lineup.
[ ] Agree to submit your final lineup to kcd@cncf.io for review, prior to publishing it
[ ] Agree to use Cloud Native Community Groups for registration, scheduling, and event website
[ ] Agree to use SM Apply for CFP and to close it at least 6 weeks before the event
[ ] Agree to provide registration list to the CNCF if using a ticket-sale platform outside of Bevy or provided platform

[ ] Schedule monthly check-ins with KCD Core Organizer(s) (kcd@cncf.io)
[ ] Minimum of 3 sponsors committed (not required for virtual only events) Sponsor 1 Sponsor 2 Sponsor 3
[ ] Identified fiscal sponsor that can accept payments such as from sponsorships and pay out expenses Fiscal sponsor that will accept payments
[ ] Added usernames for CNCF Slack for all organizers so that we can add you to the #kcd-organizers channel
[ ] Create a Twitter handle specific to your KCD event (except for countries like China and Korea where Twitter is not used)
[ ] Provided CNCF access to all event social handles

[ ] Make a copy of this timeline based on whether your event is In-person, Hybrid, or Virtual and link your own spreadsheet here ().
[ ] To assure you have a diverse lineup, you are required to send a copy of your program to kcd@cncf.io before you publish it.

cncf / kubernetes-community-days