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 Taipei 2025 #606

Open
11 of 27 tasks
AudMonte01 opened this issue Nov 25, 2024 · 1 comment
Open
11 of 27 tasks

KCD Taipei 2025 #606

AudMonte01 opened this issue Nov 25, 2024 · 1 comment
Assignees

Comments

@AudMonte01
Copy link
Collaborator

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: July 5, 2025
  • Expected Number of Attendees: 200
  • Event cost per ticket:

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

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 kick-off meeting with CNCF

Team Roles

  • Team to discuss who owns which role in the planning
  • More volunteers from previous team
  • Audra to invite Fionn and Miku to Slack workspace and add them to the channel

Venue

  • No longer co-located with COSCUP
  • Audra provided insights into CNCF funding
  • Team looking for venue and will have more insights for next meeting (January 6)

Marketing

  • Audra showed page builder. Team to let Audra know who will need to have access to this feature
  • Discuss Logo - new logo to be designed by volunteers
  • Discuss registration platform for required usage (Stripe is connected through Bevy Pay). Otherwise KKTIX would be preferred by the team
    -- discounts to contributors and Ambassadors

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

No branches or pull requests

1 participant