Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KCD Bogota 2025 #607

Open
18 of 35 tasks
AudMonte01 opened this issue Nov 25, 2024 · 3 comments
Open
18 of 35 tasks

KCD Bogota 2025 #607

AudMonte01 opened this issue Nov 25, 2024 · 3 comments
Assignees

Comments

@AudMonte01
Copy link
Collaborator

AudMonte01 commented Nov 25, 2024

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 type: In person
  • Event Venue:
  • Event Date and Time: August 29, 2025
  • Expected Number of Attendees: 500
  • Event cost per ticket:

Organizers Details (identify at least 3 organizers). For example - designate who will be the program chair, marketing lead, financial officer, etc.:

  • Team email alias is [email protected]
  • Marketing: CristherCastro | [email protected] | COO | Delray Beach, Florida | @cristhercastro | @cristhercastro
  • Marketing: Carlos Bedoya | [email protected] | Solutions Architect, Soaint | DevOps & CNCG Cali | SLACK: carlos_bedoya | GitHub: bedoyacloud
  • Sessions & Volunteer: Elias Quintero | [email protected] | CTO | Medellin Colombia | @elias quintero | @elias quintero
  • Sponsors: Johan Pietro | [email protected] | DevOps Lead, CursaCloud | SLACK: Johan Prieto | GitHub: jheimar
  • Venue & Logistics + Operations: Luis Ariza | [email protected] | Beanters SAS | SLACK: lfarizav | GitHub: lfarizav
  • Venue & Logistics + Operations: Laura Castro (Comunicadora, Cuemby)
  • Sessions: Angel Ramirez | [email protected] | CEO, Cuemby | SLACK: ar4mirez | GitHub: ar4mirez
  • Sessions: Jaime Cubillos | [email protected] | K8s SME, Globant | SLACK: Jaime Cubillos | GitHub: jaimecubillos
  • Volunteer: Carlos Arturo Quiroga | [email protected] | SLACK: Carlos Arturo Quiroga Quiroga | GitHub: carlosaq
  • Volunteer: Ivan Camargo | [email protected] | Customer Engineering, Public Sector LATAM Google | Bogota, Colombia | @ivan camargo | @ivan camargo

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.

  • This team's fiscal sponsor has signed the terms & conditions set forth by the Linux Foundation
  • This team has gone through a formal review process, where standards on timing, organizers requirements, and location collaboration have been reviewed, and approved.
  • Every organizer has an account on Cloud Native Community Groups
  • The majority of the organizers live 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.
  • All organizers agree to follow the CNCF Code of Conduct
  • 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)
  • Agree to get logo creation and approval with and from CNCF. NOTE: Previously existing KCDs ideally use their previous year's logo
  • Agree to use the designated CNCF registration platform
  • Offer at least 3 complimentary tickets to increase diversity for the event
  • Share the sponsor prospectus with CNCF via [email protected].
  • Agree to use Sessionize for CFP and to close it at least 8 weeks before the event, and launch the agenda at least 6 weeks prior to your event. CNCF will provide an event code so Sessionize is free to use if you are charging an event fee.
  • 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.
  • Submit your final speaker lineup and schedule to [email protected] for review, prior to publishing the agenda.
  • Produce a transparency report after your KCD (template below).

Resources & Templates

@AudMonte01 AudMonte01 self-assigned this Nov 25, 2024
@AudMonte01
Copy link
Collaborator Author

AudMonte01 commented Nov 25, 2024

NOVEMBER 25 CNCF KICK-OFF MEETING

Team

  • [email protected] create forwarding alias with this
  • Working on a GitHub repo will highlight efforts around roles
  • For now, team is working within this document to initiate roles and responsibilities

Venue

  • University in Bogota will be the "Conference Sponsor"
  • Central location with security, and a hospital near by

Sponsorships

  • Working on prospectus this week

Insurance

  • Insurance can cost around $2,500 USD in Colombia
  • TEAM IDEA: Have attendees and sponsors sign a waiver where they agree to be responsible for their themselves and their belongings

@AudMonte01 AudMonte01 moved this to Need to Secure Venue in Event Formation Dec 11, 2024
@jthan24
Copy link

jthan24 commented Jan 6, 2025

Hi team, could I help on this?

@AudMonte01
Copy link
Collaborator Author

JANUARY 9 CNCF SYNC

Team

  • Luis - Venue
  • Daniel - Sponsorships
  • Audra to set a meeting for the same time on February 6

Insurance

  • Team can provide a letter from the University on extended insurance for CNCF to review (but this is concerning because it can take 2.5 months)
  • The university is extending the logistics team as their contribution to the community
  • Audra to see if CNCF can use a Spanish-speaking business development team member to help review the contract
  • Security team, room setup, A/V

Sponsorships

  • team has added a clause in contracts about CNCF and LF not being responsible for organizing the event

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Need to Secure Venue
Development

No branches or pull requests

2 participants