Add community health files (#26)

* Add community health files

* update docs

* add banner

* add emphasis

* add emphasis

* fix formatting

* fix formatting

* fix formatting

* fix formatting

* formatting

* fix formatting

* fix formatting

* add missing file

* add labels

* add labels

* add labels

* add labels

* add labels

* add labels

* add labels

* Update CONTRIBUTING.md

Co-authored-by: Joe Niland <[email protected]>

* Update CONTRIBUTING.md

Co-authored-by: Joe Niland <[email protected]>

* chore: update org banner image

* chore: update repo banner image

* Update SUPPORT.md

* Update CODE_OF_CONDUCT.md

* Update CODE_OF_CONDUCT.md

Co-authored-by: Andriy Knysh <[email protected]>

* Update CODE_OF_CONDUCT.md

Co-authored-by: Andriy Knysh <[email protected]>

* Update CODE_OF_CONDUCT.md

Co-authored-by: Andriy Knysh <[email protected]>

* Update CODE_OF_CONDUCT.md

Co-authored-by: Andriy Knysh <[email protected]>

* Update CODE_OF_CONDUCT.md

Co-authored-by: Andriy Knysh <[email protected]>

---------

Co-authored-by: Joe Niland <[email protected]>
Co-authored-by: screenshot-action 📷 <[email protected]>
Co-authored-by: Andriy Knysh <[email protected]>

CODE_OF_CONDUCT.md

@@ -0,0 +1,150 @@
+# Code of Conduct
+
+This code of conduct governs the [SweetOps Slack Community](https://slack.sweetops.com/) and related [Open Source Projects](https://github.com/cloudposse). SweetOps is operated by Cloud Posse, a [DevOps Accelerator](https://devopsaccelerator.com/) based in Houston, TX.
+
+> [!IMPORTANT]
+> **SweetOps is a collaborative DevOps community for engineers of all skill levels.**
+>
+> We want to make sure our community is as constructive as possible in order to help each other solve cool DevOps problems. 
+> Anything that goes against the spirit of this, isn’t cool. If you see something suspicious, derogatory, or 
+> otherwise inappropriate, etc. please send an email to [[email protected]](mailto:[email protected]) with details.
+>
+
+## Introduction
+
+We strive to be inclusive to the largest number of contributors, with as diverse backgrounds as possible. That is why we are committed to providing an environment that encourages friendly, safe and welcoming discussions for everyone interested in learning and sharing.
+
+This code of conduct outlines our expectations for all those who participate in our community, as well as the consequences for unacceptable behavior.
+
+We invite all those who participate in SweetOps to help us create safe and positive experiences for everyone.
+
+## Etiquette
+- Do not cross-post questions across multiple channels (pick one)
+- Do not ask questions in  `#general`. Search channel instead or suggest one, if you can’t find one.
+- Use the professional language you would use at work. Avoid using profanity in any language.
+- Praise publicly (with tons of emojis!)
+- Criticize constructively, but never disparagingly (e.g. there are no “stupid” questions)
+- Practice empathy (e.g. “Ahk, that shouldn’t happen”)
+- Correct delicately (e.g. “Have you considered…”)
+- Avoid sarcasm, or feigning surprise (e.g. Don’t say “I’m surprised you didn’t know that”)
+- Seek to understand, not to embarrass, discredit or humiliate (e.g. “Hrmm… could you explain that another way? I’m not following.”)
+- When posting for the first time, review the channel history to get a sense of how others interact. Also, check out our “Guidelines When Asking for Help.”
+- Check out the channel’s topic and purpose in order to stay on point
+- Use the `#random` channel if nothing else fits
+- Use threads when responding, especially in busy channels
+- Don’t use `@channel` and `@here` (we’ve disabled them)
+
+
+## Unacceptable Behavior
+
+The following are behaviors we consider forms of harassment that are unacceptable within our community:
+- Comments that may be considered sexist, racist, homophobic, transphobic or otherwise discriminatory or offensive in nature. (Everything you say in public is on the record)
+- Usernames that contain unwelcome, suggestive, derogatory or inappropriate terms.
+- Disrespect towards others is not tolerated.
+- Unprofessional jokes, innuendo, dismissive attitudes. 
+- All forms of intimidation or harassment are prohibited. 
+- Foul or obscene language (in any language!) 
+- Disrespect towards differences of opinion.
+- Disparagement.
+- Deceptive or fraudulent activity. 
+- Sustained disruptions (like spamming channels).
+- All forms of violence, threats of violence or violent language.
+
+This is not an exhaustive list of things we prohibit. In order to preserve the spirit of this community, we reserve the right to use our discretion when applying disciplinary actions to behaviors we deem inappropriate.
+
+## Solicitation
+
+We only permit companies or individuals to solicit work, post jobs, or engage in self-promotion in the [#jobs](http://archive.sweetops.com/jobs/) channel [(archive)](http://archive.sweetops.com/jobs/). It is not acceptable to engage in this behavior in any other channel or to send unsolicited direct messages concerning job opportunities or job marketplaces. Under no circumstances is it acceptable to solicit payment from members for any reason (e.g. recruiting fees). The intent for the [#jobs](http://archive.sweetops.com/jobs/) channel [(archive)](http://archive.sweetops.com/jobs/) is for companies looking to make a direct-hire without intermediaries such as recruiters. Additionally, the promotion of any kind of third-party job marketplaces is not permitted. Any direct messages to members should be in relation to specific messages posted about job opportunities or candidates seeking work, but absolutely not for promoting other services. Recruiters may only reach out to individual candidates who have posted in the `#jobs` channel, but are not permitted to directly solicit members or companies in this community.
+
+> [!IMPORTANT]
+> If you’ve received an unwelcome solicitation, please email [[email protected]](mailto:[email protected]) with details including screenshots.
+
+## Privacy
+
+All conversations that happen in our public Slack channels are published regularly to our [online archive](https://archive.sweetops.com/) and indexed by web crawlers like Google. For this reason, community members should not have any expectation of privacy in their use.
+
+It’s the responsibility of our members to avoid sharing any information that might lead to loss or damages, such as breach of their company’s security protocols or sharing of intellectual property.
+
+All direct messages are private. They not accessible by anyone on the Slack team, including moderators and administrators.
+
+Your email address is private and will not be shared with anyone outside of Cloud Posse. From time to time, Slack (the Company) or Cloud Posse may send you notifications. If you are unable to opt-out for any reason, please let us know at [[email protected]](mailto:[email protected]).
+
+Additionally, Slack (the Company) has its own [Privacy Policy](https://slack.com/privacy-policy) which affects all communities hosted on the platform.
+
+## Logs and Records
+
+> [!IMPORTANT]
+> **Please be mindful that anything you say in our community is a matter of public record**.
+
+We publish all conversations in public channels to our [public archive](https://archive.sweetops.com/). We cannot prevent people from taking screenshots or otherwise logging conversations in this slack team.
+
+We also can’t guarantee that every member’s login credentials and logged-in devices are secure and not compromised.
+
+Keep in mind that all files uploaded to this slack team can be viewed and downloaded by anyone both via Slack and our archives.
+
+Please exercise caution and refrain from sharing sensitive information that could harm you or others if it became public.
+
+## Message Retention
+
+Because this is a free slack team, online scrollback is restricted, but Slack (the company) retains a complete log of all channels and direct messages back to the inception of the SweetOps Slack team.
+
+Slack is a U.S. company and therefore subject to subpoenas from U.S. courts. Our logs may be subject to subpoena and could become public as part of legal proceedings.
+
+## Reporting Guidelines
+
+Please let us know if you encounter any unacceptable behavior by sending us an email at [[email protected]](mailto:[email protected]). We would appreciate it if you would include any screenshots that provide a full context of whatever transpired. We might not be able to see what you see, especially if what was sent was in a private direct message.
+
+## Moderation
+
+We perform both automated and human moderation. To some degree, we expect our community to self-moderate and let us know when they see unacceptable behavior.
+
+Moderators reserve the right to delete excessive self-promotional or commercial posts. Similarly, any objectionable, inappropriate or off-topic comments may be deleted. Members posting this content will receive a warning and risk being blocked from the team if the unacceptable behavior persists.
+
+Official moderators of our Slack community are:
+- Erik Osterman ([@osterman](https://github.com/osterman))
+- Andriy Knysh ([@aknysh](https://github.com/aknysh))
+
+
+## Enforcement & Consequences
+
+Any unacceptable behavior will not be tolerated.
+
+If you are the subject of or witness to any violations of this Code of Conduct, please email us at [[email protected]](mailto:[email protected]).
+
+If violations occur, our community moderators will take necessary and appropriate actions, up to and including expulsion from the community.
+
+## Membership
+
+Our community is public and free-for-everyone to join. In fact, we encourage you to share our community with everyone you know that might benefit. Our goal is to facilitate collaboration across organizational boundaries so we can achieve SweetOps.
+
+If you would like to invite someone to the team, they may join here:
+
+[https://slack.sweetops.com](/https://slack.sweetops.com/)
+
+## Open Source Collaboration
+
+One of the big goals of our community is to increase the amount of Open Source collaboration in the DevOps community. We hope that by encouraging participants to recognize and strengthen the relationships between companies, organizations and individuals that their effects on our community will be amplified. This is why we go the extra mile to ensure our community is open, welcoming, friendly, and encourages all participants to contribute to the fullest extent possible.
+
+## “Office Hours” Support
+
+Every week we hold public [community “office hours”](https://cloudposse.com/office-hours) which are an opportunity for members to get to know each other face-to-face, ask questions, and get help. These sessions abide by this Code of Conduct.
+
+These sessions may be recorded, published and shared.
+
+## Projects
+
+We support a lot of Open Source projects. These projects abide by this Code of Conduct.
+
+- [https://github.com/cloudposse](https://github.com/cloudposse)
+
+
+## Contact
+
+We want to hear from you. Please let us know if there’s something we should add, amend or update as part of our Code of Conduct.
+
+| Contact Method      | Details                                                     |
+|---------------------|-------------------------------------------------------------|
+| **Email**           | [[email protected]](mailto:[email protected]) |
+| **Phone**           | [+1 800-358-9018](tel:+18003589018)                         |
+| **Mailing Address** | 440 N Barranca Ave #1430, Covina, CA 91723                  |
+

CONTRIBUTING.md

@@ -0,0 +1,70 @@
+# Contributing
+
+First off, thank you for considering contributing to Cloud Posse! It's people like you that make our community great.
+
+## Code of Conduct
+
+Cloud Posse has adopted a Code of Conduct that we expect project participants to adhere to. Please read [the full text](CODE_OF_CONDUCT.md) so that you can understand what actions will and will not be tolerated.
+
+## What Should I Know Before I Get Started?
+
+### Cloud Posse Projects
+
+Each Cloud Posse project is hosted in its own repository on GitHub. Before contributing, familiarize yourself with the specific project you are interested in. Each repository typically contains a [`README.md`](README.md) with an overview of the project, and instructions for setting up your development environment and running tests.
+
+## How Can I Contribute?
+
+### Reporting Bugs
+
+This section guides you through submitting a bug report. Following these guidelines helps maintainers and the community understand your report, reproduce the behavior, and find related reports.
+
+Before creating bug reports, please check the Github Issues as you might find out that you don't need to create one. When you are creating a bug report, please include as many details as possible. Fill out issue template as the information it asks for helps us resolve issues faster.
+
+### Suggesting Enhancements
+
+This section guides you through submitting an enhancement suggestion for Cloud Posse, including completely new features and minor improvements to existing functionality. Following these guidelines helps maintainers and the community understand your suggestion and find related suggestions.
+
+### Your First Code Contribution
+
+Unsure where to begin contributing to Cloud Posse? You can start by looking through issues with the following labels:
+
+| Label                                                              | Usage   |                                                         
+|:-------------------------------------------------------------------|:--------|
+| ![`help-wanted`](https://img.shields.io/badge/help_wanted-388bfd)  | issues which should only require a few lines of code, and a test or two. |
+| ![`beginner`](https://img.shields.io/badge/beginner-388bfd)        | issues which should be a bit more involved than issues. |
+
+### Pull Requests
+
+The process described here has several goals:
+
+- Maintain Cloud Posse's quality
+- Fix problems that are important to users
+- Engage the community in working toward the best possible Cloud Posse
+- Enable a sustainable system for Cloud Posse's maintainers to review contributions
+
+Please follow these steps to have your contribution considered by the maintainers:
+
+1. Follow all instructions in Pull Request template
+2. Follow the [styleguides](#styleguides)
+3. After you submit your pull request, verify that all status checks are passing
+4. If you need to request a review on your PR, please do so in the #pr-reviews Slack channel
+
+While the prerequisites above must be satisfied prior to having your pull request reviewed, the reviewer(s) may ask you to complete additional design work, tests, or other changes before your pull request can be ultimately accepted.
+
+## Styleguides
+
+### Git Commit Messages
+
+- Use the present tense ("Add feature" not "Added feature")
+- Use the imperative mood ("Move resource to..." not "Moves resource to...")
+- Limit the first line to 72 characters or less
+
+### Pull Requests
+- Reference GitHub Issues and Pull Requests liberally in a `## References` section. 
+- Use `Closes #1234` to indicate when a PR fixes an issue.
+
+### Terraform Styleguide & Best Practices
+
+All Terraform should adhere to our [Terraform Best Practices](https://docs.cloudposse.com/reference/best-practices/terraform-best-practices/).
+
+

GOVERNANCE.md

@@ -0,0 +1,51 @@
+# Governance
+
+## Introduction
+
+This document outlines the governance structure for the Cloud Posse GitHub organization. Cloud Posse, LLC, a DevOps Accelerator, governs all the projects under this organization. Our governance model is designed to be inclusive and to support the growth and sustainability of the projects.
+
+## Governance Structure
+
+### Cloud Posse, LLC
+
+Cloud Posse, LLC is responsible for the overall governance of the projects within this GitHub organization. The company makes final decisions on the technical and organizational direction of the projects.
+
+### Community Involvement
+
+While Cloud Posse, LLC holds the governance of the projects, we highly value the input and contributions from our community. The community plays a crucial role in the following ways:
+
+- **Proposing Changes and Enhancements:** Community members are encouraged to propose changes and enhancements to the projects. This can be done through GitHub issues and pull requests in the respective project repositories.
+
+- **Feedback and Discussion:** Community feedback is invaluable for the continuous improvement of the projects. We encourage active discussion and feedback through GitHub Discussions, community forums, or designated channels.
+
+- **Contributions:** Contributions from the community, in the form of code, documentation, design, or other forms, are crucial to the success of the projects. All contributions are reviewed and discussed within the community and the Cloud Posse team.
+
+### Decision Making
+
+Decisions are made through a collaborative process involving both Cloud Posse, LLC and the community. The process typically involves the following steps:
+
+1. **Proposal:** Proposals for changes or enhancements are submitted through GitHub issues or pull requests.
+2. **Discussion:** Proposals are discussed openly with the community. The discussion aims to reach a consensus among community members and the Cloud Posse team.
+3. **Decision:** After sufficient discussion, decisions are made by Cloud Posse, LLC in consideration of community feedback and the best interests of the project.
+
+### Conflict Resolution
+
+In case of disagreements or conflicts, the Cloud Posse team will work with the community members involved to resolve the issues. Our goal is to reach a solution that is acceptable to all parties and in the best interest of the project and community.
+
+## Contribution Guidelines
+
+Please refer to the `CONTRIBUTING.md` file in the respective repositories for guidelines on how to contribute to the projects.
+
+## Code of Conduct
+
+All participants in the Cloud Posse organization are expected to adhere to the Code of Conduct, which is outlined in the `CODE_OF_CONDUCT.md` file in the respective repositories.
+
+## Changes to the Governance Document
+
+This governance document may be amended or replaced from time to time. Changes to the document will be discussed and agreed upon by Cloud Posse, LLC in consultation with the community.
+
+---
+
+We, at Cloud Posse, LLC, are committed to fostering an open, collaborative, and inclusive environment. We value the participation and contributions of our community members and look forward to growing our projects together.
+
+Thank you for being part of our community!