Proposal to create a pattern name in the cloud native chapters

[krol3]

Overview

As the Cloud Native ecosystem continues to grow, the establishment of a standardized naming pattern for Cloud Native Chapters is essential. This proposal aims to introduce a consistent, scalable, and intuitive naming convention to improve discoverability, organization, and community engagement across regions.

1.	Uniformity: Ensure a unified naming pattern for the Cloud Native "Local" Chapters worldwide.
2.	Clarity: Provide clear identification of chapters based on geography and context.
3.	Scalability: Enable easy addition of new chapters as the community expands.
4.	Localization: Respect regional and cultural preferences in naming while maintaining global consistency.

Proposal

The naming pattern will follow the structure:
CloudNative [CityName] [CountryISOCode]

1.	Prefix: CloudNative
        - Identifies the chapter as part of the Cloud Native ecosystem.
2.	City Name: [CityName]
       - Represents the primary location of the chapter.
       - Use the most common name for the city in English or its native spelling if well-recognized globally.
3.	Country Code: [CountryISOCode]
       - Uses the official ISO 3166-1 alpha-2 country code for geographical clarity.
       - Example: CO for Colombia, US for the United States.

Examples:
• CloudNative Medellin, CO
• CloudNative Cartagena, CO
• CloudNative San Francisco, US
• CloudNative Bengaluru, IN
• CloudNative Sao Paulo, BR
• CloudNative Rio de Janeiro, BR

[AudMonte01]

Thank you for submitting this issue, @krol3 . I will bring this to the organizer community to review based on regions. We ask that reviews/comments on this issue are read ahead of adding another comment.

One may...

• simply upvote someone's comment by a thumbs-up
• consider regional constraints and comment here with key differences by country