FinOps Weekly Slack Community: Code of Conduct & Guidelines

1. Our Mission: Welcome to the Community

Welcome! The FinOps Weekly community is a space for professionals to connect, share knowledge, and ask questions about all things FinOps. Our goal is to make “FinOps for Everyone” a reality, foster a vibrant, collaborative environment where everyone can learn and grow. To ensure this is a welcoming and productive space for all, we ask that you agree to and abide by this Code of Conduct.

2. Community Values: Our Pledge

By joining this community, you pledge to contribute to a positive and harassment-free environment for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.

We expect all members to be:

• Respectful and Inclusive: Treat everyone with respect. Healthy debates are encouraged, but kindness is required.
• Collaborative: Share what you know and be open to learning from others.
• Mindful: Be aware of your language and how it might impact others.

3. Community Guidelines: The Rules of the Space

To keep our community focused and valuable, please adhere to the following guidelines.

3.1 General Communication

• Use Threads: Please use threads to reply to messages. This keeps channels clean and conversations easy to follow.
• No Harassment: Harassment, discriminatory language, personal attacks, and trolling will not be tolerated.
• Keep it Professional: This is a professional community. Avoid sharing NSFW (Not Safe For Work) or offensive content.

3.2 Channel Usage

Proper channel usage is key to keeping our community organized.

• #general: For general FinOps discussions, questions, and announcements that don’t fit into a more specific channel. When in doubt, start here.
• #vendors: This is the only channel for promotional content. If you represent a FinOps provider, you may share information about sponsored events, lead generation activities, product updates, and other commercial content here.
• Topic Channels (e.g., #aws, #gcp, #azure, #focus): Share information, articles, and questions related to a specific topic in the relevant channel.
• Community content should always be shared in the most relevant topic-specific channel. Defaults to #general

3.3 Spam and Promotion

• No Spam: Unsolicited promotion outside of the #vendors channel is considered spam and will be removed.
• No Unsolicited DMs: Directly messaging users for the purpose of sales or promotion is strictly prohibited. If you receive an unsolicited sales DM, please report it to an admin.
• No Data Scraping: You are not permitted to scrape, export, or otherwise collect data about community members for any reason.

4. Reporting a Violation

If you witness or are the subject of behavior that violates this Code of Conduct, please report it immediately. All reports will be handled with discretion.

• Direct Message an Admin: Send a DM to a community administrator (they will be identifiable by their user role).
• Include Details: Please provide a screenshot and/or a brief description of the incident so we can take appropriate action.

5. Enforcement and Sanctions

The community administrators (the FinOps Weekly and SmartClouds team) will enforce this Code of Conduct at their discretion. Violations will result in the following sanctions:

• First Minor Offense: You will receive a private, written warning from an administrator, and the offending content will be removed. This typically applies to posting in the wrong channel or a first-time minor promotion.
• Repeated Minor Offenses or a Serious Offense: A second violation, or a first-time serious violation (e.g., a direct sales DM, a hostile comment), will result in a temporary suspension from the community for 7 days.
• Severe Violation: Harassment, repeated spamming, data scraping, or other severe breaches of conduct will result in an immediate and permanent ban from the community.

We thank you for helping us build a respectful and valuable community for everyone in the FinOps space.