/communitygroups

πŸ‘©πŸΏβ€πŸ’»πŸ‘¨πŸΏβ€πŸ’»πŸ‘©πŸΎβ€πŸ’»πŸ‘¨πŸΎβ€πŸ’»πŸ‘©πŸ½β€πŸ’»πŸ‘¨πŸ½β€πŸ’»πŸ‘©πŸΌβ€πŸ’»πŸ‘¨πŸΌβ€πŸ’»πŸ‘©πŸ»β€πŸ’»πŸ‘¨πŸ»β€πŸ’»CNCF Community Groups (formerly meetups)

Apache License 2.0Apache-2.0

Cloud Native Community Groups

Program description

The Cloud Native Computing Foundation supports the worldwide community of Cloud Native Community Groups (CNCGs) - community.cncf.io. CNCF is currently working on expanding the Cloud Native community worldwide, and we are happy to accept any new local communities to join our network. If you are interested in joining the list of official CNCF Community Groups, please review the information below. As of 2021, Cloud Native Community Groups program is powered by the Bevy platform, and managed by the CNCF staff.

Benefits of joining the CNCF Community Groups Program

For all Cloud Native Community Groups, CNCF offers the following benefits:

  • One-time complimentary swag coupon of $100 USD to the CNCF Store provided to each community group (not to each organizer), is available after hosting 2 successful events per chapter within 3 months/90 days. NOTE: Registration must happen within the Bevy platform for this coupon to be earned. Requesting your voucher - write to meetups@cncf.io with your linked Bevy event pages.
  • Joining the CNCF organizer-exclusive Slack channel for collaboration
  • Boosting the visibility of your community group and events. See below under the β€œCommunication” section for more details.
  • 25% discount to Linux Foundation training exams for CKAD and KCNA.
  • Cost coverage for the hosted community platform, Bevy
    • This includes support from CNCF (Audra Montenegro and Katie Greenley)
    • And quarterly tips and tricks session hosted by Bevy expert Maia Walshe

βœ’οΈ NOTE: With over 150 global chapters, w cannot monetarily support your community group with sponsorships outside what is listed above.

Best Practices

Please check out our best_practices.

How to apply?

Please fill out this request form in its entirety. If you do not hear back within 30 days, please reach out to meetups@cncf.io Please do not fill out the form more than once for the same chapter/city request.

Bevy Training

Support

  • If you have any technical difficulties with the platform itself, please reach out to the [Bevy platform support by clicking the purple question mark in the bottom right corner of your Bevy chapter dashboard.
  • Troubleshooting: The troubleshooting guide by Bevy is available here: help.bevylabs.com/article/499-troubleshooting
  • Last resort, you can reach out to Audra Montenegro in the CNCF Slack workspace to help you, especially if it is time senstive.

Naming your chapter

Please use "Cloud Native CITY NAME" when naming your chapter. We ask that you avoid using "CNCF" in the naming convention, as it can misslead people into think CNCF has employees in that location. You may, however, use a tag line that states something similar to, "An official CNCF community group (or chapter)."

"CNCG" is an internal acronym we currenyly use at CNCF and among organizers, but it has not yet gained traction. So we encourage people to avoid using it in the names of their chapters, as of 2023.

Communication

Please reach out to us on the #communitygroups channel on the CNCF slack. Please avoid using direct messages unless strictly necessary as doing so both has the potential of overwhelming project maintainers and others with similar questions lose the benefit of public discussion.

It's best if you use a public communication channel whenever possible; however, if you need to communicate in private, please feel free to send the program admins a note via meetups@cncf.io (please use the public channels for any program-related discussion).

The #socialmedia channel via the CNCF slack workspace is a great place to post your social media efforts requesting assistance from CNCF to amplify. Just tag Katie Meinders and Jessie Adams-Shore to help amplify your social post.

Community Group Inactivity

If your group has more than 90 days of inactivity in the number of events/meetups being help, then you will be deemed an β€œInactive” group via the Cloud Native Computing Foundation and removed from community.cncf.io

Should a community group violate vendor neutrality, a CNCF core value, the following path towards deactivation will ocur.

  • 1st offense = a written violation via email
  • 2nd offense = a community meeting with organizers for final warning
  • 3rd offense = disabling your chapter

Code of Conduct

Cloud Native Community Groups follow the CNCF Code of Conduct.