chore(docs): add license, issue pr templates, CoC, contrib guide and …

…security policy (#202)

Fixes: #199

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,18 @@
+### Issue Type
+
+- [ ] Bug Report
+- [ ] Feature Request
+- [ ] Other
+
+### Current/Missing Behaviour
+
+### Expected/Proposed Behaviour
+
+### Additional Info
+
+- Package version:
+- Operating System:
+- Node version:
+- NW.js version:
+- Repro link:
+- ...

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,11 @@
+<!-- Description of Changes -->
+
+* 
+
+<!-- Notes: additional context on why this PR is being merged when it doesn't seem like it should -->
+
+<!-- Fixes: # -->
+<!-- Closes: # -->
+<!-- Refs: # -->
+
+<!-- Note: Remove all markdown comments after creating the pull request -->

CODE_OF_CONDUCT.md

@@ -0,0 +1,55 @@
+# "No Ideologies" Code of Conduct
+
+The following are the guidelines we expect our community members and maintainers to follow.
+
+---
+
+## Terminology and Scope
+
+**What defines a "maintainer"?**
+
+- A maintainer is anyone that interacts with the community on behalf of this project. Amount of code written is not a qualifier. A maintainer may include those who solely help in support roles such as in resolving issues, improving documentation, administrating or moderating forums/chatrooms, or any other non-coding specific roles. Maintainers also include those that are responsible for the building and upkeep of the project.
+
+**What defines a "community member"?**
+
+- Anyone interacting with this project directly, including maintainers.
+
+**What is the scope of these guidelines?**
+
+- These guidelines apply only to this project and forms of communication directly related to it, such as issue trackers, forums, chatrooms, and in person events specific to this project. If a member is violating these guidelines outside of this project or on other platforms, that is beyond our scope and any grievances should be handled on those platforms.
+
+**Discussing the guidelines:**
+
+- Discussions around these guidelines, improving, updating, or altering them, is permitted so long as the discussions do not violate any existing guidelines.
+
+---
+
+## Guidelines
+
+### Guidelines for community members
+
+This project is technical in nature and not based around any particular non-technical ideology. As such, communication that is based primarily around ideologies unrelated to the technologies used by this repository are not permitted.
+
+Any discussion or communication that is primarily focused around an ideology, be it about race, gender, politics, religion, or anything else non-technical, is not allowed. Everyone has their own ideological preferences, beliefs, and opinions. We do not seek to marginalize, exclude, or judge anyone for their ideologies. To prevent conflict between those with differing or opposing ideologies, all communication on these subjects are prohibited. Some discussions around these topics may be important, however this project is not the proper channel for these discussions.
+
+### Guidelines for maintainers
+
+- Maintainers must abide by the same rules as all other community members mentioned above. However, in addition, maintainers are held to a higher standard, explained below.
+- Maintainers should answer all questions politely.
+- If someone is upset or angry about something, it's probably because it's difficult to use, so thank them for bringing it to your attention and address ways to solve the problem. Maintainers should focus on the content of the message, and not on how it was delivered.
+- A maintainer should seek to update members when an issue they brought up is resolved.
+
+---
+
+## Appropriate response to violations
+
+How to respond to a community member or maintainer violating a guideline.
+
+1. If an issue is created that violates a guideline a maintainer should close and lock the issue, explaining "This issue is in violation of our code of conduct. Please review it before posting again." with a link to this document.
+1. If a member repeatedly violates the guidelines established in this document, they should be politely warned that continuing to violate the rules may result in being banned from the community. This means revoking access and support to interactions relating directly to the project (issue trackers, chatrooms, forums, in person events, etc.). However, they may continue to use the technology in accordance with its license.
+1. If a maintainer is in violation of a guideline, they should be informed of such with a link to this document. If additional actions are required of the maintainer but not taken, then other maintainers should be informed of these inactions.
+1. If a maintainer repeatedly violates the guidelines established in this document, they should be politely warned that continuing to violate the rules may result in being banned from the community. This means revoking access and support to interactions relating directly to the project (issue trackers, chatrooms, forums, in person events, etc.). However, they may continue to use the technology in accordance with its license. In addition, future contributions to this project may be ignored as well.
+
+---
+
+Based on version 1.0.3 from https://github.com/CodifiedConduct/coc-no-ideologies

CONTRIBUTING.md

@@ -0,0 +1,17 @@
+# Contributing
+
+## External contributor
+
+- We use [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) style of commit messages.
+- On opening a new PR, the comments will guide you on how to construct the new PR.
+- Pull requests are squashed and merged onto the `main` branch.
+- PR title is used as commit's first line, PR description is used as commit body.
+- Add tests whenever possible.
+
+## Maintainer guidelines
+
+- Approve pull requests before merging.
+- Enforce conventional commits before merging pull requests.
+- A commit's first line should be formatted as `<type>[optional scope]: <description>`.
+- A commit's body should have a description of changes in bullet points followed by any links it references or issues it fixes or closes.
+- NPM Publish Action publishes to `npm` if there is a version bump.

LICENSE

@@ -0,0 +1,20 @@
+Copyright (c) 2011-2019 NW.js Authors
+Copyright (c) 2011-2019 The Chromium Authors
+Copyright (c) 2011-2018 Intel Corp
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of 
+this software and associated documentation files (the "Software"), to deal in
+the Software without restriction, including without limitation the rights to use, 
+copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the 
+Software, and to permit persons to whom the Software is furnished to do so,
+subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
+INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR 
+A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
+HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN 
+ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH
+THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

SECURITY.md

@@ -0,0 +1,5 @@
+# Reporting a Vulnerability
+
+If you discover a security vulnerability within grunt, please submit a report via the Github's Private Vulnerability Reporting feature.
+
+All security vulnerabilities will be promptly addressed.