KCD Istanbul 2025

[halil-bugol]

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 Details

• [ ] Event Location: TBD
• [ ] Event Date and Time: June 2025
• [ ] Expected Number of Attendees 450
• [ ] Event cost per ticket, and if you will have early bird pricing or not TBD

Event type:

• [ ] Virtual
• [ ] Hybrid
• [X] In person

Organizers Details (identify at least 3 organizers). Designate who will be the CFP admin, as well as the financial officer:

• [X] Organizer 1: Halil BUGÖL, Kubezy, Co-Founder, halil@kubezy.com, CNCF Slack: Halil (Financial Officer)
• [X] Organizer 2: Emin ALEMDAR, Spacelift, Solutions Architect, emnalmdr@gmail.com, CNCF Slack: Emin Alemdar (CFP Admin)
• [X] Organizer 3: Batuhan APAYDIN, Trendyol, Container Dude, batuhan.apaydin@trendyol.com, CNCF Slack: developer-guy
• [X] Organizer 4: Ali Ok, RedHat, Principal Software Engineer, ali.ok@redhat.com, CNCF Slack: Ali Ok
• [X] Organizer 5: Alp Kahvecioglu, Sufle, Cloud & Platform Engineer, aakahvecioglu@gmail.com, CNCF Slack: Alp Kahvecioglu
• [X] Organizer 6: Koray Oksay, Kubermatic, Site Reliability Engineer, koray@kubermatic.com, CNCF Slack: Koray Oksay

Terms

IMPORTANT: These are the terms within the checklist that must be abided by. Note - There are exceptions to these requirements in some jurisdictions due to applicable laws & regulations.

• [X] No other Kubernetes Community Day event in same major city (check with past organizers)
• [x] Minimum of 3 organizers from 3 different organizations
• [x] Every organizer has an account on Cloud Native Community Groups
• [x] Each organizer lives within the KCD city or just outside of it. For small countries, the organizers can live within the region, but must be able to easily travel to the KCD if it were in-person.
• [x] At least one organizer is a CNCF employee, CNCF ambassador, or CNCF project maintainer.
• [x] All organizers agree to follow the event guidelines and CNCF Code of Conduct
• [x] All organizer inquiries / communication for CNCF must be summarized via GitHub (comment under your KCD issue) for easy tracking
• [ ] All organizers have taken Inclusive Open Source Community Orientation (LFC102)
• [x] 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.
• [x] 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.
• [x] Agree to submit your final lineup to kcd@cncf.io for review, prior to publishing it
• [x] Agree to use Cloud Native Community Groups for registration, scheduling, and event website. If using a platform outside of Bevy, organizers must provide CNCF with a full list of attendees. -- Regardless of your platform choice, please use these questions to create your registration form
• [x] Agree to use Sessionize as the Call for Proposals (CFP) platform.
• [x] Agree to get logo creation and approval with and from CNCF. NOTE: a new logo will be created in an effort provide unity, and and official KCD stamp of approval.

Getting started checklist for organizers

• [ ] Schedule monthly check-ins with KCD Core Organizer(s) (kcd@cncf.io)
• [ ] Minimum of 3 sponsors committed (not required for virtual only events) Kubezy @kubezy Sponsor 2 Sponsor 3
• [X] 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 LinkedIn profile and/or Twitter handle specific to your KCD event (except for countries like China and Korea where Twitter is not used)

Getting started checklist for CNCF:

• [ ] Organizer email alias has been created
• [ ] Region created in Bevy
• [ ] Added to Bevy header
• [ ] CFP code given for Sessionize
• [ ] Marketing Plan shared

Organizer Planning Timeline

• [ ] 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.

Post event checklist for Organizers:

• [ ] Send CNCF event analytics
• [ ] Schedule post mortem meeting
• [ ] Send CNCF videos to be uploaded to YouTube
• [ ] Link videos from YouTube to event page
• [ ] Post event survey sent out
• [ ] Fill out Credly badge request form for 1 badge per KCD

Post event checklist for CNCF:

• [ ] Removed from Bevy header
• [ ] CFP deactivated
• [ ] Upload videos to YouTube
• [ ] Transparency report and YouTube playlist (if there is one) linked from cncf.io/kcds
• [ ] Bevy page marked as dormant

[AudMonte01]

Hello @halil-bugol - Thank you for submitting this issue, and your interest in hosting another KCD! Please do not confirm anything, which means no selling sponsorships, or signing of contracts until our team has met with you and approved. Please add a general date for this event in the meantime.

[halil-bugol]

@AudMonte01 We need to start the organization before August 1st. Otherwise, it will be postponed until the end of next year. We cannot announce the date because there is no guarantee.

[AudMonte01]

You may start organization efforts, but please do not sign any contracts ahead of our announcement of program changes.

[AudMonte01]

Thank you for your submission - we are now ready to accept official applications via an official application form. The deadline for submissions will be Wednesday September 11 at 11:59pm Pacific Daylight Time. More information and the application can be found via https://www.cncf.io/kcds/application/.

This GitHub issue is now closed. Should your KCD be accepted into the 2025 program, a core CNCF staff member will open a new issue for program tracking and transparency.