KCD Islamabad 2024

[Saim-Safdar]

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

• [x] Event Location: Islamabad
• [x] Event Date and Time: April 2024
• [x] Expected Number of Attendees: 300
• [x] Event cost per ticket, and if you will have early bird pricing or not

  Event type:

• [ ] Virtual
• [x] Hybrid
• [ ] In person

  Organizers Details (identify at least 3 organizers). Designate 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

Terms

• [x] No other Kubernetes Community Day event in the same major city (check with past organizers)
• [x] If there is already a KCD in your country, you agree to schedule your KCD at least two months apart from that pre-planned KCD.
• [x] Minimum of 3 organizers from 3 different organizations
• [x] Every organizer has an account on Cloud Native Community Groups
• [x] Each organizer lives in or just outside of the KCD location
• [x] At least one organizer is a CNCF member employee, CNCF ambassador, or CNCF project maintainer
• [x] All organizers agree to follow the event guidelines and CNCF Code of Conduct
• [x] 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)
• [x] Agree to offer at least 3 complimentary tickets to increase diversity for the event
• [x] 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 SM Apply for CFP and to close it at least 6 weeks before the event

Getting started checklist for organizers

• [x] 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 WeChat handle specific to your KCD event

Getting started checklist for CNCF:

• [ ] Region created in Bevy
• [ ] Added to Bevy header
• [ ] CNCF China team introduced for marketing amplification, and review of program

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 Organizer:

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

Post event checklist for CNCF:

• [ ] Removed from Bevy header
• [ ] CFP deactivated
• [ ] Upload videos to YouTube

[AudMonte01]

Closing this issue, due to another being opened and properly filled. https://github.com/cncf/kubernetes-community-days/issues/535