In order to remain a strong and active community, we believe CNCGs are successful with 2 or more organizers with responsibilities divided among each other. Ideally there is no more than 5 organizers for virtual chapters, and no more than 7 for in-person. Please refer to the roles below. NOTE: This organizer capacity does not apply to parent chapters that are country-wide or regional chapters (i.e. LATAM or EU).
You are already donating your time to further the knowledge and awareness of Cloud Native technologies, likely in addition to a full-time job. In addition, people may fall ill, get injured, or have new deadlines. With that, it will benefit you to have backup to avoid cancellations of your meetups.
Each team should have no more than 50% of organizers from the same company. This is to assure fair voting practices, what's more --> vendor nuetrality.
IMPORTANT: Cloud Native Community Groups are NOT to be used for self benefit. In an effort to avoid monopolizing practices, organizers cannot belong to more than two (2) community groups as an organizer. You may of course help advise other groups, but will not be recognized as an organizer on the front-end of said chapter page if you do not reside in, or travel to that chapter location 50% of the calendar year.
Thank you in advance for not assuming lead organizer roles, as Bevy can be confusing with the permission sets.
We do however, suggest your team figure out who has more experience organizing different facets of community groups like:
- Sponsorships
- Speakers
- F&B (Food and Beverage)
- A/V (Audio & Video)
- Swag
- On-site emcee
- Attendee marketing and communications
NOTE: If your team is small, it is common to have 1-2 assignments per person.
If you wish to add someone or multiple people to your team, you may submit an organizer GitHub issue/request on behalf of these co-organizers and have that person (or people) comment on the issue agreeing the the organizer terms. Or this peron / these people can submit on behalf of themselves and at least 50% of organizers shall comment with affirmation of said person being added as a co-organizer.
If someone on your team wishes, or agrees to step down as an organizer, please have them submit a GitHub issue via the organizer request form here. You may submit an issue on their behalf, but that team member will still need to comment affirming their resignation. This is to assure communication among the team, and transparency to the rest of your local community.