Re-add files

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# 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, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, 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 support@mainwp.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and 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 https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

.github/CONTRIBUTING.md

@@ -0,0 +1,78 @@
+# How to contribute to MainWP Child plugin
+
+Community made patches, localizations, bug reports and contributions are always welcome. Your help making it even more awesome will be greatly appreciated :)
+
+When contributing please ensure you follow the guidelines below to help us keep on top of things.
+
+__Please Note:__
+
+GitHub is for _bug reports and contributions only_ - if you have a support question or a request for a customization this is not the right place to post it. Use [MainWP Support](https://mainwp.com/support/) for customer support and for customizations we recommend one of our MainWP trusted Experts:
+
+[MainWP Experts](https://mainwp.com/mainwp-experts/)
+
+
+## Contributing To The Core
+
+### Reporting Issues
+
+Reporting issues is a great way to become a contributor as it doesn't require technical skills. In fact you don't even need to know a programming language or to be able to check the code itself, you just need to make sure that everything works as expected and [submit an issue report](https://github.com/mainwp/mainwp/issues/new) if you spot a bug. Sound like something you're up for? Go for it!
+
+#### How To Submit An Issue Report
+
+If something isn't working, congratulations you've found a bug! Help us fix it by submitting an issue report:
+
+* Make sure you have a [GitHub account](https://github.com/signup/free)
+* Search the [Existing Issues](https://github.com/mainwp/mainwp/issues) to be sure that the one you've noticed isn't already there
+* Submit a report for your issue
+  * Clearly describe the issue (including steps to reproduce it if it's a bug)
+  * Make sure you fill in the earliest version that you know has the issue.
+
+### Making Changes
+
+Helping aking changes to the MainWP Dashboard is a key way to help us improve MainWP overall. You will need some technical skills to make a change, like knowing a bit of PHP, CSS, SASS or JavaScript.
+
+If you think something could be improved and you're able to do so, make your changes and submit a Pull Request. We'll be pleased to get it :)
+
+#### How To Submit A PR
+
+* Fork the repository on GitHub
+* Make the changes to your forked repository
+  * **Ensure you stick to the [WordPress Coding Standards](http://make.wordpress.org/core/handbook/coding-standards/php/).**
+  * Ensure you use LF line endings - no crazy Windows line endings please :)
+* When committing, reference your issue number (#1234) and include a note about the fix
+* Push the changes to your fork and submit a pull request on the master branch of the MainWP Dashboard repository. Existing maintenance branches will be maintained by MainWP developers
+* Please **don't** modify the changelog - this will be maintained by the MainWP developers.
+* Please **don't** add your localizations or update the .pot files - these will also be maintained by the MainWP developers. To contribute to the localization of MainWP, please join the [translate.wordpress.org project](https://translate.wordpress.org/projects/wp-plugins/mainwp). This is much needed, if you speak a language that needs translating consider yourself officially invited.
+
+After you follow the step above, the next stage will be waiting on us to merge your Pull Request. We review them all, and make suggestions and changes as and if necessary.
+
+## Contribute To Localizing MainWP
+
+Localization is a very important part of MainWP. We believe in net neutrality and want our platform to be available to everyone, everywhere with equal ease. When you localize MainWP, you are helping hundreds of people in the world, and all the people who speak your language. That's pretty neat.
+
+### Glossary & Style Guide
+
+Please refer to this page on the [Translator Handbook](https://make.wordpress.org/polyglots/handbook/translating/glossary-style-guide/) for information about the glossary and the style guide.
+
+Each translation editor will take care of updating the glossary on GlotPress by editing/adding items when needed.
+
+_**Note**: Only editors can create/import and edit glossaries and glossary items on GlotPress. Anyone can suggest new items to add to the glossary or translate them._
+
+### Translating The Core
+
+We have a [project on translate.wordpress.org](https://translate.wordpress.org/projects/wp-plugins/mainwp). You can join the localization team of your language and help by translating MainWP. [Find more about using joining a language team and using GlotPress](https://make.wordpress.org/polyglots/handbook/tools/glotpress-translate-wordpress-org/).
+
+If MainWP is already 100% translated for your language, join the team anyway! We regularly update our language files and there will definitely be need of your help soon.
+
+
+# Additional Resources
+
+* [General GitHub documentation](http://help.github.com/)
+* [GitHub pull request documentation](http://help.github.com/send-pull-requests/)
+* [Translator Handbook](https://make.wordpress.org/polyglots/handbook/)
+* [MainWP Docs](http://docs.mainwp.com/)
+* [MainWP API / Codex](http://codex.mainwp.com/)
+
+# CONTRIBUTING File Credit
+
+This CONTRIBUTING.md file relies heavily WooCommerce's [CONTRIBUTING.md](https://github.com/woothemes/woocommerce/blob/master/CONTRIBUTING.md) for wording and contribution requirements.   

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,38 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
+**Smartphone (please complete the following information):**
+ - Device: [e.g. iPhone6]
+ - OS: [e.g. iOS8.1]
+ - Browser [e.g. stock browser, safari]
+ - Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,33 @@
+### All Submissions:
+
+* [ ] Have you followed the [MainWP Contributing guideline](https://github.com/mainwp/mainwp-child/blob/master/.github/CONTRIBUTING.md)?
+* [ ] Does your code follow the [WordPress' coding standards](https://make.wordpress.org/core/handbook/best-practices/coding-standards/)?
+* [ ] Have you checked to ensure there aren't other open [Pull Requests](https://github.com/mainwp/mainwp-child/pulls) for the same update/change?
+
+<!-- Mark completed items with an [x] -->
+
+<!-- You can erase any parts of this template not applicable to your Pull Request. -->
+
+### Changes proposed in this Pull Request:
+
+<!-- Describe the changes made to this Pull Request and the reason for such changes. -->
+
+Closes # .
+
+### How to test the changes in this Pull Request:
+
+1.
+2.
+3.
+
+### Other information:
+
+* [ ] Have you added an explanation of what your changes do and why you'd like us to include them?
+* [ ] Have you written new tests for your changes, as applicable?
+* [ ] Have you successfully run tests with your changes locally?
+
+<!-- Mark completed items with an [x] -->
+
+### Changelog entry
+
+> Enter a summary of all changes on this Pull Request. This will appear in the changelog if accepted.

.github/SECURITY.md

@@ -0,0 +1,4 @@
+# Security Policy
+
+## Reporting Security Issues
+To disclose a security issue to our team, [please submit a report via HackerOne here](https://hackerone.com/mainwp).