feat(monorepo): Initial check-in of monorepo code

.chef-repo.txt

@@ -0,0 +1,6 @@
+.chef-repo.txt
+==============
+
+This file gives the Chef CLI's generators a hint that you are using a Chef Infra
+Repo and this is the root directory of your Chef Infra Repo. Chef CLI's generators
+use this to generate code that is designed to work with the Chef Repo workflow.

.chef/client.rb

@@ -0,0 +1,4 @@
+add_formatter :nyan
+validation_client_name 'storm-software-validator'
+validation_key './.chef/validator.pem'
+client_key './.chef/client.pem'

.chef/config.rb

@@ -0,0 +1,9 @@
+current_dir = File.dirname(__FILE__)
+cookbook_path ["#{current_dir}/../cookbooks"]
+data_bag_path "#{current_dir}/../data_bags"
+
+node_name 'mynode.example.com'
+recipe_url 'https://chef.storm-cdn.com/cookbooks'
+rest_timeout 300
+role_path '"#{current_dir}/../roles'
+sandbox_path 'path_to_folder'

.chef/solo.rb

@@ -0,0 +1,23 @@
+add_formatter :nyan
+checksum_path '/var/chef/checksums'
+cookbook_path [
+               '../cookbooks'
+              ]
+data_bag_path './data_bags'
+environment 'production'
+environment_path './tmp/chef/environments'
+file_backup_path './tmp/chef/backup'
+file_cache_path './tmp/chef/cache'
+json_attribs nil
+lockfile nil
+log_level :info
+log_location STDOUT
+node_name 'mynode.example.com'
+recipe_url 'http://stormsoftware/cookbook'
+rest_timeout 300
+role_path '/var/chef/roles'
+sandbox_path 'path_to_folder'
+solo true
+syntax_check_cache_path
+umask 0022
+verbose_logging nil

.github/.nvmrc

@@ -0,0 +1 @@
+20.14.0

.github/CODEOWNERS

@@ -0,0 +1,3 @@
+@sullivanpj @storm-software/operations
+
+/docs/ @storm-software/docs

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,125 @@
+# 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 at <[email protected]>.
+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 community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org),
+version 2.0, available at
+[https://www.contributor-covenant.org/version/2/0/code_of_conduct.html](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/inclusion).
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are available
+at [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations).

.github/CONTRIBUTING.md

@@ -0,0 +1,15 @@
+# All contributions, however small are valued
+
+## Steps to contribute
+
+If you want to make a small change, go ahead and raise a pull request, otherwise follow these steps:
+
+1. View the [Issues](https://github.com/storm-software/storm-chef/issues) page to see a To-Do list of things to be implemented.
+2. Raise an issue or comment on an existing issue with what you want to contribute if one does not already exist.
+3. When you get the go ahead, follow the coding guidelines and raise a pull request.
+4. Include a link to the issue in your pull request.
+
+## Coding Guidelines
+
+-   Projects use StyleCop and .editorconfig to produce style warnings. Please fix all warnings in any code you submit.
+-   Write unit tests for any code written.

.github/FUNDING.yml

@@ -0,0 +1,4 @@
+# These are supported funding model platforms
+
+patreon: StormSoftware
+github: storm-software

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -0,0 +1,102 @@
+name: 🐞 Bug Report
+description: Report a bug.
+title: "[Bug]: "
+labels: ["bug", "triage"]
+assignees:
+  - sullivanpj
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report!
+  - type: input
+    id: contact
+    attributes:
+      label: Contact Details
+      description: How can we get in touch with you if we need more info?
+      placeholder: ex. [email protected]
+    validations:
+      required: true
+  - type: textarea
+    id: actual-results
+    attributes:
+      label: Current Behavior
+      description: What behavior are you currently experiencing?
+      placeholder: What behavior are you currently experiencing?
+      value: "What behavior are you currently experiencing?"
+    validations:
+      required: true
+  - type: textarea
+    id: expected-results
+    attributes:
+      label: Expected Behavior
+      description: What behavior are you expecting to experience?
+      placeholder: What behavior are you expecting to experience?
+      value: "What behavior are you expecting to experience?"
+    validations:
+      required: true
+  - type: dropdown
+    id: package
+    attributes:
+      label: Package Name
+      description: Which package are you experiencing this error with?
+      multiple: true
+      options:
+        - create-storm-workspace
+        - Linting Tools
+        - Git Tools
+        - Workspace Tools
+    validations:
+      required: true
+  - type: dropdown
+    id: version
+    attributes:
+      label: Version
+      description: What version of our software are you running?
+      options:
+        - 1.0.0
+    validations:
+      required: false
+  - type: dropdown
+    id: operating-system
+    attributes:
+      label: What platform(s) are you seeing the problem in?
+      multiple: true
+      options:
+        - Microsoft Windows
+        - MacOS
+        - ChromeOS
+        - iOS
+        - Android
+        - Ubuntu
+        - Debian
+        - Fedora
+        - CentOS
+        - Linux (General)
+        - Other
+    validations:
+      required: false
+  - type: dropdown
+    id: browsers
+    attributes:
+      label: What browsers are you seeing the problem on (if applicable)?
+      multiple: true
+      options:
+        - Firefox
+        - Chrome
+        - Safari
+        - Microsoft Edge
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
+      render: TypeScript
+  - type: checkboxes
+    id: agreed
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/storm-software/storm-chef/blob/main/.github/CODE_OF_CONDUCT.md)
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.github/ISSUE_TEMPLATE/documentation.yml

@@ -0,0 +1,56 @@
+name: 📖 Documentation issue
+description: Help improve our docs.
+title: "[Documentation]: "
+labels: ["documentation"]
+assignees:
+  - sullivanpj
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to help us improve the ⚡ Storm Docs!
+  - type: input
+    id: contact
+    attributes:
+      label: Contact Details
+      description: How can we get in touch with you if we need more info?
+      placeholder: ex. [email protected]
+    validations:
+      required: true
+  - type: dropdown
+    id: type
+    attributes:
+      label: Documentation issue
+      description: Reason for this request
+      multiple: true
+      options:
+        - Reporting a typo
+        - Reporting a documentation bug
+        - Documentation improvement
+        - Documentation feedback
+    validations:
+      required: true
+  - type: input
+    id: description
+    attributes:
+      label: Is there a specific documentation page you are reporting?
+      description: Enter the URL or documentation section here.
+      placeholder: Enter the URL or documentation section here.
+    validations:
+      required: true
+  - type: textarea
+    id: additional-details
+    attributes:
+      label: Additional context or description
+      description: Provide any additional details here as needed.
+      placeholder: Provide any additional details here as needed.
+    validations:
+      required: false
+  - type: checkboxes
+    id: agreed
+    attributes:
+      label: Code of Conduct
+      description: By submitting this request, you agree to follow our [Code of Conduct](https://github.com/storm-software/storm-chef/blob/main/.github/CODE_OF_CONDUCT.md)
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true