Completed GitHub community standards

.github/ISSUE_TEMPLATE/ISSUE_TEMPLATE.md

@@ -0,0 +1,21 @@
+---
+name: 🐛 Bug
+about: Create a report to help us improve Blaze
+title: ''
+labels: ''
+assignees: ''
+---
+<!--
+Before reporting a bug, please check for existing or closed issues first.
+
+### This bug report should include:
+- [ ] A short, but descriptive title. The title doesn't need "Blaze" in it.
+- [ ] The version of Blaze showing the problem.
+- [ ] The last version of Blaze where the problem did _not_ occur, if applicable.
+- [ ] The operating system you're running Blaze on.
+- [ ] The expected behavior.
+- [ ] The actual behavior.
+- [ ] A **simple** reproduction! (Must either include a minimal code example
+or a link to a Github repository with steps to reproduce the issue on it.)
+
+-->

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,19 @@
+---
+blank_issues_enabled: false
+contact_links:
+  -
+    about: Ask a question or for help on the Meteor forums
+    name: ❓ Question
+    url: https://forums.meteor.com/
+  -
+    about: Chat on our community Slack
+    name: 🗯 Chat
+    url: https://join.slack.com/t/meteor-community/shared_invite/enQtODA0NTU2Nzk5MTA3LWY5NGMxMWRjZDgzYWMyMTEyYTQ3MTcwZmU2YjM5MTY3MjJkZjQ0NWRjOGZlYmIxZjFlYTA5Mjg4OTk3ODRiOTc
+  -
+    about: The official Blaze website
+    name: ℹ️ Website
+    url: https://www.blazejs.org/
+  -
+    about: Blaze documentation
+    name: 📜 Documentation
+    url: https://www.blazejs.org/guide/introduction.html

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,23 @@
+<--
+First, 🌠 thank you 🌠 for taking the time to consider a contribution to Blaze!
+
+Here are some important details to follow:
+
+* ⏰ Your time is important
+          To save your precious time, if the contribution you are making will take more
+          than an hour, please make sure it has been discussed in an issue first.
+          This is especially true for feature requests!
+* 🕷 Bug fixes
+          These can be created and discussed in this repository. When fixing a bug,
+          please _try_ to add a test which verifies the fix.  If you cannot, you should
+          still submit the PR but we may still ask you (and help you!) to create a test.
+* 📖 Contribution guidelines
+          Always follow https://github.com/meteor/blaze/blob/master/CONTRIBUTING.md
+          when submitting a pull request.  Make sure existing tests still pass, and add
+          tests for all new behavior.
+* ✏️ Explain your pull request
+          Describe the big picture of your changes here to communicate to what your
+          pull request is meant to accomplish.  Provide 🔗 links 🔗 to associated issues!
+
+We hope you will find this to be a positive experience!  Open source contribution can be intimidating and we hope to alleviate that pain as much as possible.  Without following these guidelines, you may be missing context that can help you succeed with your contribution, which is why we encourage discussion first.  Ultimately, there is no guarantee that we will be able to merge your pull-request, but by following these guidelines we can try to avoid disappointment.
+-->

CODE_OF_CONDUCT.md

@@ -0,0 +1,69 @@
+# Blaze Project Code of Conduct
+
+### Community and Diversity
+
+We want to build a productive, happy and agile community that welcomes new ideas, constantly looks for areas to improve, and fosters collaboration. 
+
+The project gains strength from a diversity of backgrounds and perspectives in our contributor community, and we actively seek participation from those who enhance it. This code of conduct exists to lay some ground rules that ensure we can collaborate and communicate effectively, despite our diversity. The code applies equally to founders, team members and those seeking help and guidance.
+
+### Using This Code
+
+This isn’t an exhaustive list of things that you can’t do. Rather, it’s a guide for participation in the community that outlines how each of us can work to keep Blaze a positive, successful, and growing project. 
+
+This code of conduct applies to all spaces managed by the Blaze project or company. This includes Slack, GitHub issues, and any other forums created by the Blaze team which the community uses for communication. Breaches of this code outside these spaces may affect a person's ability to participate within them. We expect it to be honored by everyone who represents or participates in the project, whether officially or informally.
+
+If you believe someone is violating the code of conduct, please report it by emailing [community@meteor.com](mailto:community@meteor.com). 
+
+### We Strive To:
+
+- **Be open, patient, and welcoming**
+
+    Members of this community are open to collaboration, whether it's on PRs, issues, or problems. We're receptive to constructive comment and criticism, as we value what the experiences and skill sets of contributors bring to the project. We're accepting of all who wish to get involved, and find ways for anyone to participate in a way that best matches their strengths.
+
+- **Be considerate**
+
+    We are considerate of our peers: other Blaze users and contributors. We’re thoughtful when addressing others’ efforts, keeping in mind that work is often undertaken for the benefit of the community. We also value others’ time and appreciate that not every issue or comment will be responded to immediately. We strive to be mindful in our communications, whether in person or online, and we're tactful when approaching views that are different from our own.
+
+- **Be respectful**
+
+    As a community of professionals, we are professional in our handling of disagreements, and don’t allow frustration to turn into a personal attack. We work together to resolve conflict, assume good intentions and do our best to act in an empathic fashion. 
+
+    We do not tolerate harassment or exclusionary behavior. This includes, but is not limited to:
+  - Violent threats or language directed against another person.
+  - Discriminatory jokes and language.
+  - Posting sexually explicit or sexualized content.
+  - Posting content depicting or encouraging violence. 
+  - Posting (or threatening to post) other people's personally identifying information ("doxing").
+  - Personal insults, especially those using racist or sexist terms.
+  - Unwelcome sexual attention.
+  - Advocating for, or encouraging, any of the above behavior.
+  - Repeated harassment of others. In general, if someone asks you to stop, then stop.
+
+- **Take responsibility for our words and our actions**
+
+    We can all make mistakes; when we do, we take responsibility for them. If someone has been harmed or offended, we listen carefully and respectfully. We are also considerate of others’ attempts to amend their mistakes.
+
+- **Be collaborative**  
+
+    The work we produce is (and is part of) an ecosystem containing several parallel efforts working towards a similar goal. Collaboration between teams and individuals that each have their own goal and vision is essential to reduce redundancy and improve the quality of our work. 
+
+    Internally and externally, we celebrate good collaboration. Wherever possible, we work closely with upstream projects and others in the free software community to coordinate our efforts. We prefer to work transparently and involve interested parties as early as possible.
+
+- **Ask for help when in doubt**
+
+    Nobody is expected to be perfect in this community. Asking questions early avoids many problems later, so questions are encouraged, though they may be directed to the appropriate forum. Those who are asked should be responsive and helpful.
+
+- **Take initiative** 
+
+    We encourage new participants to feel empowered to lead, to take action, and to experiment when they feel innovation could improve the project. If we have an idea for a new tool, or how an existing tool can be improved, we speak up and take ownership of that work when possible. 
+
+### Attribution
+
+Sections of this Code of Conduct were inspired in by the following Codes from other open source projects and resources we admire:  
+
+- [The Contributor Covenant](https://www.contributor-covenant.org/version/1/4/code-of-conduct/)
+- [Python](https://www.python.org/psf/codeofconduct/)
+- [Ubuntu](https://ubuntu.com/community/code-of-conduct)
+- [Django](https://www.djangoproject.com/conduct/)
+
+*This Blaze Code of Conduct is licensed under the [Creative Commons Attribution-ShareAlike 4.0 International](https://creativecommons.org/licenses/by-sa/4.0/) license. This Code was last updated on August 28, 2017.* 

SECURITY.md

@@ -0,0 +1,44 @@
+# Security Policy
+
+## Supported Versions
+
+| Version | Support Status
+| ------- | --------------
+| 3.x.y   | ✅  all security issues
+| >=2.5   | ✅  all security issues
+| <2.5    | 🚧  only critical security issues
+| <= 2    | ❌  no longer supportted
+
+## Reporting a Vulnerability
+
+Report security bugs to security@meteor.com.
+
+Your report will be acknowledged within 2 work days, and you'll receive a more
+detailed response to your report within 6 work days indicating the next steps in
+handling your submission.
+
+After the initial reply to your report, the security team will endeavor to keep
+you informed of the progress being made towards a fix and full announcement,
+and may ask for additional information or guidance surrounding the reported
+issue.
+
+We don't have any bounty program. 
+
+## Reporting a security bug in a third party module
+
+Security bugs in third party modules should be reported to their respective
+maintainers.
+
+Thank you for improving the security of Blaze and its ecosystem. Your efforts
+and responsible disclosure are greatly appreciated and will be acknowledged.
+
+## Disclosure policy
+
+Here is the security disclosure policy for Blaze
+
+* The security report is received and is assigned a primary handler. This
+  person will coordinate the fix and release process. The problem is confirmed
+  and a list of all affected versions is determined. Code is audited to find
+  any potential similar problems. Fixes are prepared for all releases which are
+  still under maintenance. These fixes are not committed to the public
+  repository but rather held locally pending the announcement.