Assign eQuantum to project workflow

.github/CODEOWNERS

@@ -0,0 +1,13 @@
+# Lines starting with '#' are comments.
+# Each line is a file pattern followed by one or more owners.
+
+# These owners will be the default owners for everything in the repo.
+*       @eq19
+
+# Order is important. The last matching pattern has the most precedence.
+# So if a pull request only touches javascript files, only these owners
+# will be requested to review.
+# *.js    @octocat @github/js
+
+# You can also use email addresses if you prefer.
+# .github/*  [email protected]

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,49 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers 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, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

.github/CONTRIBUTING.md

@@ -0,0 +1,16 @@
+# Installation
+
+1. Install a full [Ruby development environment](https://jekyllrb.com/docs/installation/)
+2. Change into your new directory
+
+```sh
+make
+```
+
+4. Build the site and make it available on a local server
+
+```sh
+make server
+```
+
+5. Browse to [http://localhost:4000](http://localhost:4000)

.github/FUNDING.yml

@@ -0,0 +1 @@
+custom: ["https://git.io/JJAW8"]

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,32 @@
+---
+name: Bug report
+about: Create a bug report
+title: ''
+labels: bug, needs triage
+assignees: ''
+
+---
+
+**Description:**
+A clear and concise description of what the bug is.
+
+**Task version:**
+Specify the task version
+
+**Platform:**
+- [ ] Ubuntu
+- [ ] macOS
+- [ ] Windows
+
+**Runner type:**
+- [ ] Hosted
+- [ ] Self-hosted
+
+**Repro steps:**  
+A description with steps to reproduce the issue. If your have a public example or repo to share, please provide the link.
+
+**Expected behavior:**
+A description of what you expected to happen.
+
+**Actual behavior:**
+A description of what is actually happening.

.github/ISSUE_TEMPLATE/config.yml

@@ -1,4 +1,5 @@
+blank_issues_enabled: false
 contact_links:
-  - name: "Get Help"
-    about: "Links to documentation and community support"
-    url: "https://cloudinit.readthedocs.io/en/latest/#project-and-community"
+  - name: .NET issues
+    url: https://github.com/dotnet/runtime#filing-issues
+    about: Issues with the runtime, class libraries, frameworks, and SDK should be addressed directly with the .NET team. Documentation on filing issues can be found here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,16 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: feature request, needs triage
+assignees: ''
+---
+
+**Description:**
+Describe your proposal.
+
+**Justification:**
+Justification or a use case for your proposal.
+
+**Are you willing to submit a PR?**
+<!--- We accept contributions! -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,47 +1,29 @@
-## Proposed Commit Message
-<!-- Include a proposed commit message because PRs are squash merged
-by default.
-
-See https://www.conventionalcommits.org/en/v1.0.0/#specification
-for our commit message convention.
-
-If the change is related to a particular cloud or particular distro,
-please include the "optional scope" in the summary line. E.g.,
-feat(ec2): Add support for foo to the baz
-
-Types used by this project:
-feat, fix, docs, ci, test, refactor, chore
--->
+### Summary
+<!-- Please mention all relevant issue numbers. -->
+Main Code: []()
 ```
-<type>(optional scope): <summary>  # no more than 72 characters
-
-A description of what the change being made is and why it is being
-made if the summary line is insufficient.  This should be wrapped at
-72 characters.
-
-If you need to write multiple paragraphs, feel free.
 
-Fixes GH-NNNNN (GitHub Issue number. Remove line if irrelevant)
-LP: #NNNNNN (Launchpad bug number. Remove line if irrelevant)
 ```
 
-## Additional Context
-<!-- If relevant -->
-
-## Test Steps
-<!-- Please include any steps necessary to verify (and reproduce if
-this is a bug fix) this change on a live deployed system,
-including any necessary configuration files, user-data,
-setup, and teardown. Scripts used may be attached directly to this PR. -->
-
-## Checklist
-<!-- Go over all the following points, and put an `x` in all the boxes
-that apply. -->
-- [ ] My code follows the process laid out in [the documentation](https://cloudinit.readthedocs.io/en/latest/development/index.html)
-- [ ] I have updated or added any [unit tests](https://cloudinit.readthedocs.io/en/latest/development/testing.html) accordingly
-- [ ] I have updated or added any [documentation](https://cloudinit.readthedocs.io/en/latest/development/contribute_docs.html) accordingly
-
-## Merge type
-
-- [x] Squash merge using "Proposed Commit Message"
-- [ ] Rebase and merge unique commits. Requires commit messages per-commit each referencing the pull request number (#<PR_NUM>)
+###  Checklist
+<!-- Please keep this section. It will make maintainer's life easier. -->
+1. [ ] Privileged views and APIs are guarded by proper permission checks.
+1. [ ] All visible strings are translated with proper context.
+1. [ ] All data-formatting is locale-aware (dates, numbers, and so on).
+1. [ ] Database queries are optimized and the number of queries is constant.
+1. [ ] Database migration files are up to date.
+1. [ ] The changes are tested.
+1. [ ] The code is documented (docstrings, project documentation).
+1. [ ] GraphQL schema and type definitions are up to date.
+1. [ ] Changes are mentioned in the changelog.
+
+### Reference
+<!-- Put some necessary link for referrence of the PR  -->
+
+- []()
+- []()
+- []()
+
+### Screenshots
+<!-- If your changes affect the UI, providing "before" and "after" screenshots will
+greatly reduce the amount of work needed to review your work. -->

.github/csc.json

@@ -0,0 +1,18 @@
+{
+    "problemMatcher": [
+        {
+            "owner": "csc",
+            "pattern": [
+                {
+                    "regexp": "^([^\\s].*)\\((\\d+)(?:,\\d+|,\\d+,\\d+)?\\):\\s+(error|warning)\\s+([a-zA-Z]+(?<!MSB)\\d+):\\s*(.*?)\\s+\\[(.*?)\\]$",
+                    "file": 1,
+                    "line": 2,
+                    "severity": 3,
+                    "code": 4,
+                    "message": 5,
+                    "fromPath": 6
+                }
+            ]
+        }
+    ]
+}