diff --git a/gh_pages/404.html b/gh_pages/404.html new file mode 100644 index 0000000..f32223c --- /dev/null +++ b/gh_pages/404.html @@ -0,0 +1,340 @@ + + + +
+ + + + + + + + + + + + + + +The dbt-loom community exists to provide a free, unencumbered, and +vendor-agnostic means of enabling multi-project deployments of dbt-core. +We accept that for this project to be successful, we must create a +community that is open, curious, and accepting of each others differences.
+We as members, contributors, and leaders pledge to make participation in our +community a harassment-free experience for everyone, regardless of age, body +size, visible or invisible disability, ethnicity, sex characteristics, gender +identity and expression, level of experience, education, socio-economic status, +nationality, personal appearance, race, religion, sexual identity +and orientation, or employer.
+We pledge to act and interact in ways that contribute to an open, welcoming, +diverse, inclusive, and healthy community.
+Examples of behavior that contributes to a positive environment for our +community include:
+Examples of unacceptable behavior include:
+Community leaders are responsible for clarifying and enforcing our standards of +acceptable behavior and will take appropriate and fair corrective action in +response to any behavior that they deem inappropriate, threatening, offensive, +or harmful.
+Community leaders have the right and responsibility to remove, edit, or reject +comments, commits, code, wiki edits, issues, and other contributions that are +not aligned to this Code of Conduct, and will communicate reasons for moderation +decisions when appropriate.
+This Code of Conduct applies within all community spaces, and also applies when +an individual is officially representing the community in public spaces. +Examples of representing our community include using an official email address, +posting via an official social media account, or acting as an appointed +representative at an online or offline event.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be +reported to the community leaders responsible for enforcement at +yager@nicholasyager.com. All complaints will be reviewed and investigated +promptly and fairly.
+All community leaders are obligated to respect the privacy and security of the +reporter of any incident.
+Community leaders will follow these Community Impact Guidelines in determining +the consequences for any action they deem in violation of this Code of Conduct:
+Community Impact: Use of inappropriate language or other behavior deemed +unprofessional or unwelcome in the community.
+Consequence: A private, written warning from community leaders, providing +clarity around the nature of the violation and an explanation of why the +behavior was inappropriate. A public apology may be requested.
+Community Impact: A violation through a single incident or series +of actions.
+Consequence: A warning with consequences for continued behavior. No +interaction with the people involved, including unsolicited interaction with +those enforcing the Code of Conduct, for a specified period of time. This +includes avoiding interactions in community spaces as well as external channels +like social media. Violating these terms may lead to a temporary or +permanent ban.
+Community Impact: A serious violation of community standards, including +sustained inappropriate behavior.
+Consequence: A temporary ban from any sort of interaction or public +communication with the community for a specified period of time. No public or +private interaction with the people involved, including unsolicited interaction +with those enforcing the Code of Conduct, is allowed during this period. +Violating these terms may lead to a permanent ban.
+Community Impact: Demonstrating a pattern of violation of community +standards, including sustained inappropriate behavior, harassment of an +individual, or aggression toward or disparagement of classes of individuals.
+Consequence: A permanent ban from any sort of public interaction within +the community.
+This Code of Conduct is adapted from the Contributor Covenant, +version 2.0, available at +https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+Community Impact Guidelines were inspired by +Mozilla's code of conduct enforcement ladder.
+For answers to common questions about this code of conduct, see the FAQ at +https://www.contributor-covenant.org/faq. Translations are available +at https://www.contributor-covenant.org/translations.
+ + + + + + + + + + + + + +Thank you for taking the time to contribute! 🎉💃
+The following is a set of guidelines for contributing to dbt-loom. These are +mostly guidelines, not rules. Use your best judgment, and feel free to propose +changes to this document in a pull request.
+If you find a bug, please report it by opening an issue on GitHub. Make sure to +include:
+If you have an idea to enhance dbt-loom, we'd love to hear about it! Please +open an issue on GitHub and include:
+When you're ready to start working on an issue, fork the repository and create +a new branch for your work. Follow these steps:
+git checkout -b feature/my-feature-branch
.git commit -m 'Add some feature'
.git push origin feature/my-feature-branch
.After creating the pull request, the PR will automatically notify the +maintainers, and they will be able to trigger CI checks for your change.
+Make sure all tests pass before submitting a pull request. You can run the +tests with:
+ +Contributions to documentation are always welcome. If you see something that can be improved or needs clarification, feel free to make changes.
+This project adheres to the Contributor Covenant Code of Conduct. +By participating, you are expected to uphold this code.
+If you need help or have any questions, feel free to open an issue on GitHub.
+Thank you for contributing!
+ + + + + + + + + + + + + +