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

[Organizer Request] Add Co-Organizer Vikas

Open Beginner friendly
  • Is something wrong?
#862 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
72/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Domain
content

Research direction

Start by reading the chapter organizer request process and the existing Cloud Native Indore organizer records; this issue names no code files or tests. Check the request details against the repository’s documented requirements, then update the chapter’s organizer information if the request is accepted. Done means Vikas is recorded as a co-organizer in the project’s expected location.

Written by the indexing model from the issue text.

Description

Name of chapter inquiring about

Cloud Native Indore

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

Name Vikas Ratnawat
Email :- [email protected]
Company :- PWC india
LinkedIn URL:- https://www.linkedin.com/in/vikasratnawat/
GitHub URL:- https://github.com/vikas4cloud
CNCF Slack workspace:- Vikas Ratnawat
profile link on community.cncf.io:- https://openprofile.dev/profile/vikas4cloud

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

We would like to add Vikas Ratnawat as a co-organizer of Cloud Native Indore. With his 15+ years of experience in Cloud, DevOps, and AI, we believe he can bring valuable industry insights, mentorship, and community-building experience to help us grow the chapter and create more learning and networking opportunities for developers and students in Indore.

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

https://www.credly.com/badges/360d48cc-649f-4c5a-9e7c-7979eeeae2f4/public_url

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 Content issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.