chore(docs): add community files

CODE_OF_CONDUCT.md

@@ -0,0 +1,82 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+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, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+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.
+
+## Scope
+
+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 e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement using [this e-mail](mailto:upgraded-enigma@protonmail.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.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**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.
+
+### 2. Warning
+
+**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.
+
+### 3. Temporary 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.
+
+### 4. 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 project community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], 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](https://github.com/mozilla/diversity).
+
+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.

CONTRIBUTING.md

@@ -0,0 +1,112 @@
+# Contributing to this repository <!-- omit in toc -->
+
+## Getting started <!-- omit in toc -->
+
+### Before you begin
+
+Have you read the [code of conduct](CODE_OF_CONDUCT.md)?
+
+Check out the [existing issues](https://github.com/dead-beef/webaudio-spectrum-analyser/issues) and see what [types of contributions](#types-of-contributions) are accepted.
+
+### Don't see your issue? Open one
+
+If you spot something new, open an issue using a [template](https://github.com/dead-beef/webaudio-spectrum-analyser/issues/new/choose). We'll use the issue to have a conversation about the problem you want to fix.
+
+### Keep contributing
+
+Now that you're a part of the community, you can keep participating in many ways.
+
+**Learn more about contributing:**
+
+- [ Types of contributions](#types-of-contributions)
+  - [:memo: Issues](#memo-issues)
+  - [:hammer_and_wrench: Pull requests](#hammer_and_wrench-pull-requests)
+- [Starting with an issue](#starting-with-an-issue)
+  - [:label: Labels](#label-labels)
+- [Opening a pull request](#opening-a-pull-request)
+- [Reviewing](#reviewing)
+  - [Self review](#self-review)
+  - [Suggested changes](#suggested-changes)
+- [Working in the repository](#working-in-the-repository)
+
+## Types of contributions
+
+You can contribute to the repository several ways.
+
+### :memo: Issues
+
+[Issues](https://docs.github.com/en/github/managing-your-work-on-github/about-issues) are used to track tasks that contributors can help with. If an issue has no labels, we haven't reviewed it yet and you shouldn't begin work on it.
+
+If you've found something in the content or the website that should be updated, search open issues to see if someone else has reported the same thing. If it's something new, open an issue using a [template](https://github.com/dead-beef/webaudio-spectrum-analyser/issues/new/choose). We'll use the issue to have a conversation about the problem you want to fix.
+
+### :hammer_and_wrench: Pull requests
+
+A [pull request](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/about-pull-requests) is a way to suggest changes in the repository.
+
+## Starting with an issue
+
+You can browse [existing issues](https://github.com/dead-beef/webaudio-spectrum-analyser/issues) to find something that needs help.
+
+If you find something that is not present in the issues section [Submit a new issue using existing templates](https://github.com/dead-beef/webaudio-spectrum-analyser/issues/new/choose)
+
+### :label: Labels
+
+Labels can help you find an issue you'd like to help with.
+
+- The [`Help wanted` label](https://github.com/github/docs/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) is for problems or updates that anyone in the community can start working on.
+
+Check all available labels with description [here](https://github.com/dead-beef/webaudio-spectrum-analyser/labels).
+
+## Opening a pull request
+
+Fork using the command line:
+
+- [Fork the repo](https://docs.github.com/en/github/getting-started-with-github/fork-a-repo#fork-an-example-repository) so that you can make your changes without affecting the original project until you're ready to merge them.
+
+### Make your update
+
+Make your changes to the file(s) you'd like to update. Here are some tips and tricks for [using the docs codebase](#working-in-the-repository).
+
+### Open a pull request
+
+When you're done making changes and you'd like to propose them for review. Read [about pull requests](https://docs.github.com/en/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) if unsure how to do it.
+
+### Submit your PR & get it reviewed
+
+- Once you submit your PR, others from the core team will review it with you. The first thing you're going to want to do is a [self review](#self-review).
+- After that, we may have questions, check back on your PR to keep up with the conversation.
+- Did you have an issue, like a merge conflict? Check out our [git tutorial](https://lab.github.com/githubtraining/managing-merge-conflicts) on how to resolve merge conflicts and other issues.
+
+### Your PR is merged!
+
+Congratulations! The whole Intel community thanks you.
+
+Once your PR is merged, you will be listed as a contributor in the [contributor chart](https://github.com/dead-beef/webaudio-spectrum-analyser/graphs/contributors).
+
+## Reviewing
+
+Every single PR is reviewed.
+
+- Reviews are always respectful, acknowledging that everyone did the best possible job with the knowledge they had at the time.
+- Reviews discuss content, not the person who created it.
+- Reviews are constructive and start conversation around feedback.
+
+### Self review
+
+You should always review your own PR first.
+
+For content changes, make sure that you:
+
+- [ ] Confirm that the changes meet the user experience and goals outlined in the content design plan (if there is one).
+- [ ] Review the content for technical accuracy.
+- [ ] If there are any failing checks in your PR, troubleshoot them until they're all passing.
+
+### Suggested changes
+
+We may ask for changes to be made before a PR can be merged, either using [suggested changes](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request) or pull request comments. You can apply suggested changes directly through the UI. You can make any other changes in your fork, then commit them to your branch.
+
+As you update your PR and apply changes, mark each conversation as [resolved](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#resolving-conversations).
+
+## Working in the repository
+
+To work with in the repository the following [requirements](https://github.com/dead-beef/webaudio-spectrum-analyser#requirements) should be fulfilled.

SECURITY.md

@@ -0,0 +1,8 @@
+# Secutiry
+
+TODO
+
+```plaintext
+Support file contents.
+Fur supported files see https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file#about-default-community-health-files
+```

SUPPORT.md

@@ -0,0 +1,8 @@
+# Support
+
+TODO
+
+```plaintext
+Support file contents.
+Fur supported files see https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file#about-default-community-health-files
+```