Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add and Remove Organizers from CNCG Bogota

Open
  • Is something wrong?
#847 5 comments 2 reactions 1 assignee View on GitHub

@FedericaLinux is already working on this.

Since Oct 13, 2026.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
20/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Domain
documentation

Research direction

This is an administrative request to the CNCF maintainers, not a code change: @AudMonte01 and @hspease99 must confirm removal of @Ángel-Ramírez, @Samantha-Upegui and @Iván-Camargo from the Cloud Native Bogotá organizer charter at ocgroups.dev/cncf/group/g9bdkpk. Done means the charter's organizer list is updated; the two existing comments should be read first for confirmations from the tagged organizers. A code newcomer has nothing to submit here.

Written by the indexing model from the issue text.

Description

Name of chapter inquiring about

Cloud Native Bogota

Tell us about yourself. List your name, email, company, GitHub URL, LinkedIn URL, and CNCF Slack workspace name (or if you need to be invited), and a required profile link on community.cncf.io

My name is Cristher Castro. I have been a CNCF Ambassador for the past four years and an active organizer across Cloud Native Colombia, including Medellín, Bogotá, and Cali. I have also co-organized KCD Colombia 2023, 2025, and 2027. I’m supporting the restructuring of Cloud Native Bogotá to re-engage the local community and support its growth going forward.

Tell us why you want to be added or removed from the chapter

@AudMonte01 & @hspease99, I’d like to request an update to the current Cloud Native Bogotá organizer charter: https://ocgroups.dev/cncf/group/g9bdkpk

Due to changes in availability and other professional commitments, we propose removing @Ángel-Ramírez, @Samantha-Upegui, and @Iván-Camargo as active chapter organizers. We are very grateful for the time, leadership, and contributions they have made to create and support the community, as well as for their support in strengthening the Cloud Native ecosystem in Bogotá and across Colombia.
I’m tagging them here so they can confirm and approve this transition, if they are available to do so. Thank you all for your contributions and for the impact you have created within the community.

The remaining organizer, @Johan-Prietro, @Jheimar and I will continue working closely on reactivating the local chapter, strengthening community participation, and inviting new leaders to join. Our goal is to keep creating meaningful opportunities for learning, collaboration, and growth while continuing the impact that Cloud Native Bogotá has built over the past six years.

We welcome new leaders focused on community impact, sharing knowledge, and creating better opportunities for the region.

Code of Conduct
Where organizer resides
  • I confirm I am local to or live near the city of the above-proposed chapter (do not mark if not relevant to request)
Organizers companies/affiliations
  • I come from xyz company which is differing from that of the current organizers (do not mark if not relevant to request)
Inclusive
Link to your LFC102 Credly Badge

No response

Vendor Neutral
  • I have read what vendor-neutrality means, and I agree the main content of our meetups will remain vendor-neutral (do not mark if not relevant to request)
Remain an active chapter
  • I understand the activity level standards of all CNCF chapters (do not mark if not relevant to request)
Collaboration with other chapters
  • I acknowledge the CNCF right to approve additional chapters in my area based on this criteria (do not mark if not relevant to request)
Aim to have a diverse representation of speakers in your meetups
  • I will do my best to host diverse speakers throughout the year (do not mark if not relevant to request)
Dominant language
No language data
Stars
230
Forks
60
Avg merge
17h 32m
Merged PRs (30d)
2

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cncf/communitygroups

All issues in cncf/communitygroups

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.