Event Policies

Code of Conduct 

This code of conduct applies to all spaces the Cloud-Native Geo (CNG) manages, including public and private mailing lists, issue trackers, wikis, blogs, X (Twitter), LinkedIn, Discourse, Slack, and any other communication channels our communities use. A code of conduct specific to in-person events (ie., conferences) is in the CNG anti-harassment policy.

We expect everyone who participates in the CNG community formally or informally or claims any affiliation with CNG to honor this code of conduct in any CNG-related activities especially when representing CNG in any role.

This code is not exhaustive or complete. It distills our common understanding of a collaborative, shared environment and goals. We expect all members of the CNG community to follow it in spirit as much as in the letter so that it can enrich all of us and the technical communities in which we participate.

Specific Guidelines 

We strive to:

Be open. We invite anyone to participate in our community. We prefer to use public methods of communication for project-related messages unless discussing something sensitive. This applies to messages for help or project-related support, too; not only is a public support request much more likely to result in an answer to a question, but it also makes sure that the community notices and corrects any inadvertent mistakes people answering the query may make.

Be empathetic, welcoming, friendly, and patient. We work together to resolve conflicts, assume good intentions, and do our best to act in an empathetic fashion. We may all experience some frustration from time to time, but we do not allow frustration to result in a personal attack. A community where people feel uncomfortable or threatened is not a productive one. We should be respectful when dealing with other community members as well as with people outside our community.

Be collaborative. Other people will use our work, and we in turn depend on the work of others. When we make something for the benefit of the project, we are willing to explain to others how it works, so they can build on the work to make it even better. Any decision we make will affect users and colleagues, and we take those consequences seriously when making decisions.

Be inquisitive. Nobody knows everything! Asking questions early avoids many problems later, so we encourage questions, although we may redirect them to the appropriate forum. Those who receive a question should be responsive and helpful, within the context of our shared goal of improving the CNG community.

Be careful in the words that we choose. Whether we are participating as professionals or volunteers, we value professionalism in all interactions and take responsibility for our speech. Be kind to others. Do not insult or put down other participants. Harassment and other exclusionary behaviors are not acceptable. This includes, but is not limited to:

• Violent threats or language directed against another person.
• Sexist, racist, or otherwise discriminatory jokes and language.
• Posting sexually explicit or violent material.
• Posting (or threatening to post) other people’s personally identifying information (“doxing”).
• Sharing private content, such as emails sent privately or non-publicly, or from unlogged forums such as IRC channel history.
• Personal insults, especially those using racist or sexist terms.
• Unwelcome attention, sexual or otherwise.
• Excessive or unnecessary profanity.
• Repeated harassment of others. In general, if someone asks you to stop, then stop.
• Advocating for, or encouraging, any of the above behavior.

Be concise. Keep in mind that, over time, hundreds or thousands of people will read what you write. Writing a short message means people can understand the conversation as efficiently as possible. Short messages should always strive to be empathetic, welcoming, friendly, and patient. When a long explanation is necessary, consider adding a summary at the top of the message. Try to bring new ideas to a conversation so that each message adds something unique to the thread, keeping in mind that the rest of the thread still contains the other messages with arguments that have already been made.

Try to stay on topic, especially in discussions that are already fairly long.

Step down considerately. Members of every project come and go. When somebody leaves or disengages from the project they should tell people they are leaving and take the proper steps to ensure that others can pick up where they left off. In doing so, they should remain respectful of those who continue to participate in the project and should not misrepresent the project’s goals or achievements. Likewise, community members should respect any individual’s choice to leave the project.

Diversity Statement 

CNG welcomes and encourages participation by everyone. We are committed to being a community that everyone feels good about joining. Although we may not be able to satisfy everyone, we will always work to treat everyone well.

No matter how you identify yourself or how others perceive you, we welcome you.

Though we welcome people fluent in all languages, CNG discussions take place in English.

Reporting Guidelines 

While all participants should adhere to this code of conduct, we recognize that sometimes people may have a bad day, or need to be made aware of some of the code’s guidelines. When that happens, you may reply to them and point out this code of conduct. Such messages may be in public or in private, whatever is most appropriate. However, regardless of whether the message is public or not, it should still adhere to the relevant parts of this code of conduct; in particular, it should not be abusive or disrespectful.

Assume good faith; participants are likely unaware of their bad behavior than that they intentionally try to degrade the quality of the discussion. Should there be difficulties in dealing with the situation, you may report your compliance issues in confidence to leadership at Radiant Earth (parent organization of CNG):

• Executive Director: Jed Sundwall ( jed at radiant.earth )
• Director of Operations: Louisa Diggs (louisa at radiant.earth)

Notes 

This statement draws on the Apache Software Foundation Code of Conduct for content and inspiration. Please visit the Apache Software Foundation Code of Conduct for a list of other helpful codes of conduct.

Cancellation and Transfer Policy 

Ticket Transfers 

• Conference tickets may be transferred to another attendee at no additional cost
• All ticket transfers must be completed at least 14 days prior to the event
• To initiate a transfer, the original ticket should send a message to hello@cloudnativegeo.org with the name and email address of the new attendee
• The new attendee must provide their full contact information and accept the conference terms and conditions
• Once transferred, the original ticket becomes invalid

Cancellation and Refunds 

• Cancellation requests must be submitted in writing to hello@cloudnativegeo.org
• Refunds will be processed according to the following schedule:
  • 90+ days before the event: Full refund minus a $50 administrative fee
  • 60-89 days before the event: 75% refund
  • 30-59 days before the event: 50% refund
  • Less than 30 days before the event: No refund

Additional Terms 

• All cancellation requests must include the original booking confirmation number
• Refunds will be processed using the original payment method
• Processing time for refunds may take up to 30 business days
• No refunds will be issued for no-shows or partial attendance
• In case of emergency or unforeseen circumstances preventing attendance, cases will be reviewed individually

Conference Cancellation by Organizer 

• In the unlikely event that the conference is cancelled by the organizer:
  • All registered attendees will receive a full refund including any administrative fees
  • The organizer is not responsible for any travel, accommodation, or other costs incurred by attendees
  • Attendees will be notified immediately via email and the conference website

Virtual Component (if applicable) 

• If the conference includes virtual components, transfer and cancellation policies remain the same
• No refunds will be issued due to technical difficulties on the attendee’s end
• For any questions regarding cancellations or transfers, please contact hello@cloudnativegeo.org or call [phone number].

Note: This policy is subject to change at the organizer’s discretion. Any changes will be communicated to registered attendees.