diff --git a/.github/banner.png b/.github/banner.png index 0b1603c3..f6f0493f 100644 Binary files a/.github/banner.png and b/.github/banner.png differ diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md new file mode 100644 index 00000000..c6055f6d --- /dev/null +++ b/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 [abuse@cloudposse.com](mailto:abuse@cloudposse.com) 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 [abuse@cloudposse.com](mailto:abuse@cloudposse.com) 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 [abuse@cloudposse.com](mailto:abuse@cloudposse.com). + +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 [abuse@cloudposse.com](mailto:abuse@cloudposse.com). 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 [abuse@cloudposse.com](mailto:abuse@cloudposse.com). + +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** | [community@cloudposse.com](mailto:community@cloudposse.com) | +| **Phone** | [+1 800-358-9018](tel:+18003589018) | +| **Mailing Address** | 440 N Barranca Ave #1430, Covina, CA 91723 | + diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 00000000..3ef5a04a --- /dev/null +++ b/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/). + + diff --git a/GOVERNANCE.md b/GOVERNANCE.md new file mode 100644 index 00000000..f31d0b62 --- /dev/null +++ b/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! diff --git a/README.md b/README.md index 764a661c..0106f619 100644 --- a/README.md +++ b/README.md @@ -26,15 +26,16 @@ --> -This repository fulfills several unique functions functions for Cloud Posse. - 1. It can contain special org-level files that provide functionality for our organization on GitHub. These files include: - - `profile/README.md` - 2. It can also act as a source for defaults of some repo-level files that might be found in a new GitHub repo's `.github` folder. In the event that a new repo is initialized without these files, the repo will behave on github.com as those the default copies of these files were present in the repo. These files include: - - `.github/CODEOWNERS` - - `FUNDING.yml` - - `.github/ISSUE_TEMPLATE/*` +This repository fulfills several unique functions functions for the Cloud Posse GitHub Organization. + +1. It can contain special org-level files that provide functionality for our organization on GitHub. These files include: + - [`profile/README.md`](profile/README.md) +2. It can also act as a source for defaults of some repo-level files that might be found in a new GitHub repo's `.github` folder. In the event that a new repo is initialized without these files, the repo will behave on github.com as those the default copies of these files were present in the repo. These files include: + - [`.github/CODEOWNERS`](.github/CODEOWNERS) + - [`FUNDING.yml`](FUNDING.yml) + - [`.github/ISSUE_TEMPLATE/*`](.github/ISSUE_TEMPLATE/) - `.github/PULL_REQUEST_TEMPLATE.md` - 3. In addition to these GitHub-mediated functions, we are also conscripting the `cloudposse/.github` repo to act as the source for all GitHub Actions workflows and other bootstrapping files that are copied out automatically to our repositories (and which we encourage others to copy to their own repositories) using our [Auto-format GitHub Action](https://github.com/cloudposse/github-action-auto-format). (Note that there is some overlap between the files that GitHub recognizes as repo-level default files and the files that we actively copy to our repos using the `Auto-format` action. This doesn't affect the functionality of either process, but it's worth noting for future reference.) Files that are distributed in this way include: +3. In addition to these GitHub-mediated functions, we are also conscripting the `cloudposse/.github` repo to act as the source for all GitHub Actions workflows and other bootstrapping files that are copied out automatically to our repositories (and which we encourage others to copy to their own repositories) using our [Auto-format GitHub Action](https://github.com/cloudposse/github-action-auto-format). (Note that there is some overlap between the files that GitHub recognizes as repo-level default files and the files that we actively copy to our repos using the `Auto-format` action. This doesn't affect the functionality of either process, but it's worth noting for future reference.) Files that are distributed in this way include: - `.github/auto-release.yml` - `.github/CODEOWNERS` - `.github/ISSUE_TEMPLATE/*` diff --git a/README.yaml b/README.yaml index 7b96401c..40fde34f 100644 --- a/README.yaml +++ b/README.yaml @@ -27,15 +27,16 @@ badges: # Short description of this project description: |- - This repository fulfills several unique functions functions for Cloud Posse. - 1. It can contain special org-level files that provide functionality for our organization on GitHub. These files include: - - `profile/README.md` - 2. It can also act as a source for defaults of some repo-level files that might be found in a new GitHub repo's `.github` folder. In the event that a new repo is initialized without these files, the repo will behave on github.com as those the default copies of these files were present in the repo. These files include: - - `.github/CODEOWNERS` - - `FUNDING.yml` - - `.github/ISSUE_TEMPLATE/*` + This repository fulfills several unique functions functions for the Cloud Posse GitHub Organization. + + 1. It can contain special org-level files that provide functionality for our organization on GitHub. These files include: + - [`profile/README.md`](profile/README.md) + 2. It can also act as a source for defaults of some repo-level files that might be found in a new GitHub repo's `.github` folder. In the event that a new repo is initialized without these files, the repo will behave on github.com as those the default copies of these files were present in the repo. These files include: + - [`.github/CODEOWNERS`](.github/CODEOWNERS) + - [`FUNDING.yml`](FUNDING.yml) + - [`.github/ISSUE_TEMPLATE/*`](.github/ISSUE_TEMPLATE/) - `.github/PULL_REQUEST_TEMPLATE.md` - 3. In addition to these GitHub-mediated functions, we are also conscripting the `cloudposse/.github` repo to act as the source for all GitHub Actions workflows and other bootstrapping files that are copied out automatically to our repositories (and which we encourage others to copy to their own repositories) using our [Auto-format GitHub Action](https://github.com/cloudposse/github-action-auto-format). (Note that there is some overlap between the files that GitHub recognizes as repo-level default files and the files that we actively copy to our repos using the `Auto-format` action. This doesn't affect the functionality of either process, but it's worth noting for future reference.) Files that are distributed in this way include: + 3. In addition to these GitHub-mediated functions, we are also conscripting the `cloudposse/.github` repo to act as the source for all GitHub Actions workflows and other bootstrapping files that are copied out automatically to our repositories (and which we encourage others to copy to their own repositories) using our [Auto-format GitHub Action](https://github.com/cloudposse/github-action-auto-format). (Note that there is some overlap between the files that GitHub recognizes as repo-level default files and the files that we actively copy to our repos using the `Auto-format` action. This doesn't affect the functionality of either process, but it's worth noting for future reference.) Files that are distributed in this way include: - `.github/auto-release.yml` - `.github/CODEOWNERS` - `.github/ISSUE_TEMPLATE/*` diff --git a/SECURITY.md b/SECURITY.md new file mode 100644 index 00000000..ede00f4e --- /dev/null +++ b/SECURITY.md @@ -0,0 +1,42 @@ +# Security Policy + +## Reporting a Vulnerability + +The Cloud Posse team takes the security of our software seriously. If you believe you have found a security vulnerability in any repository owned by Cloud Posse, we encourage you to let us know straight away. We will investigate all legitimate reports and do our best to quickly fix the problem. + +> [!IMPORTANT] +> Please report any security vulnerabilities by sending an email to [security@cloudposse.com](mailto:security@cloudposse.com). + +### What to Include in Your Report + +To help us better understand the nature and scope of the issue, please include as much of the following information as possible in your report: +- Description of the vulnerability and its potential impact. +- Step-by-step instructions to reproduce the issue. +- Affected versions and configurations. +- Any possible mitigations or workarounds that you have identified. + +### What to Expect + +> [!NOTE] +> **Bug Bounties** +> +> As an open-source company, Cloud Posse **does not** provide bug bounties for vulnerability disclosures. +> + +After you submit a report, we will endeavor to: +- Respond to your report within 48 hours to acknowledge receipt. +- Provide an estimated time frame for addressing the vulnerability. +- Notify you when the issue is resolved. + +## Supported Versions + +Given the nature of our open-source projects, we generally support only the latest major version of each project. However, critical security patches may be applied to older versions at our discretion. + +## Our Commitment + +We deeply value the contributions and efforts of security researchers and the wider community in improving the security and integrity of our projects. + +We are committed to working with the community in a transparent and collaborative manner. We recognize the efforts of those who responsibly disclose vulnerabilities and will ensure they receive acknowledgment for their contributions in our project documentation or other public communications, as appropriate. + +Thank you for your support in keeping Cloud Posse and the open source ecosystem secure! + diff --git a/SUPPORT.md b/SUPPORT.md new file mode 100644 index 00000000..7b864462 --- /dev/null +++ b/SUPPORT.md @@ -0,0 +1,70 @@ +# Support + +This document provides support information for all repositories under the Cloud Posse organization. + +We value your involvement in the Cloud Posse community and look forward to your contributions and questions. + +Thank you for being part of our community! + + +> [!TIP] +> **Where to Find Support** +> +> If you're looking for support for any Cloud Posse projects, here are a few options to consider. +> + +### Documentation + +Before seeking support, please make sure to check our documentation. Each project in the Cloud Posse organization typically has its own set of documentation, which can be found in the repository's `README.md` file or in a dedicated `docs` directory. We also have a developer [documentation portal](https://docs.cloudposse.com) which collates all our documentation into one place that is searchable. + +### Issues + +If you believe you have found a bug or if you have a feature request, please use the GitHub issue tracker of the specific repository. Before creating a new issue, please: +- Check that the issue has not already been reported or fixed. +- Ensure that the issue is related to the specific project and not a dependency or a broader system issue. + +### Discussions + +For questions, ideas, and general discussion, we encourage the use of our organization's [GitHub Discussions](https://github.com/orgs/cloudposse/discussions). This is a great place to seek help, share your knowledge, and engage with the Cloud Posse community. + +### Community Channels + +Cloud Posse also maintains community [Slack Team & Channels](https://slack.cloudposse.com). These can be great places to seek real-time help or advice from the community and the Cloud Posse team. + +## How to Contribute + +We love contributions! If you're interested in helping out, check out the `CONTRIBUTING.md` file in the respective repository for guidelines on how to contribute. + +## Professional Support + +For professional support, please contact [Cloud Posse](https://cloudposse.com) directly. Please note that while we strive to provide community support wherever possible, professional support will involve costs or service agreements. +[![README Commercial Support][readme_commercial_support_img]][readme_commercial_support_link] + +## Security Issues + +For security issues, please do not post them publicly on the forums, issue trackers, or discussions. Instead, refer to our security policy outlined in [`SECURITY.md`](https://github.com/cloudposse/.github/blob/main/SECURITY.md) in the respective repository. + + +## Guidelines When Asking for Help + +> [!TIP] +> **Tips to follow when asking for help** +> +> We appreciate that not everyone has all the answers every time. That’s exactly why our community is here to help. +> Keep in mind, we are all volunteers. Everyone donates their time; no one receives any payment for helping answer your questions. +> + +1. **Research the problem or question.** Be prepared to share links of what you’ve already tried and considered. We expect you’ve “Googled it” before we do. If you don’t know where to begin, that’s okay. In that case, ask for help on how to approach the problem. +2. **State your problem, not just your solution.** The [XY Problem](http://xyproblem.info/) is the fallacy of asking for help about your _attempted solution_ rather than ask for help solving your _actual_ _problem_. This leads to enormous amounts of wasted time and energy, both on the part of people asking for help, and on the part of those providing help. +3. **Search our Slack for the answer.** We see a lot of the same questions asked over and over again. Do a quick search before asking your question. +4. **Ask Constructive Questions.** When asking your question, mention any research you’ve done, relevant links and GitHub issues, as well as provide any relevant code samples. +5. **Use Markdown Formatting.** When pasting code samples, make sure you use markdown formatting. Code that is not formatted makes it difficult for others to read and reduce the likelihood of getting an answer. For longer blobs of text, make sure you use snippets.**IMPORTANT**: Make sure you have permission to share any code samples because these will be public. +6. **Use the Appropriate Channel.** We have dozens of channels that help us organize all the information and questions asked. The #general channel is only for welcoming new users or asking for help on where to ask a question. +7. **Do Not Cross-Post.** Use one channel at a time to avoid spamming our community. Keep in mind, users are in 57 timezones. You may not get an answer right away. +8. ** Keep Conversations in Threads.** Our channels get pretty busy. When multiple concurrent conversations are happening, it’s hard to keep it straight. Also, it’s helpful if you add supplementary information in the thread of the question, rather than posting a new message. +9. **Give Copious Praise.** Did you get the answer you were looking for? Did someone help you? Let them know! We operate on praise. There’s never enough. + + + [readme_commercial_support_img]: https://cloudposse.com/readme/commercial-support/img + [readme_commercial_support_link]: https://cloudposse.com/readme/commercial-support/link?utm_source=github&utm_medium=readme&utm_campaign=cloudposse/.github&utm_content=readme_commercial_support_link + diff --git a/profile/banner/image.png b/profile/banner/image.png index ffb57f59..d1095585 100644 Binary files a/profile/banner/image.png and b/profile/banner/image.png differ