Merge branch 'master'

.github/CONTRIBUTING.md

@@ -1,56 +1,62 @@
-# How To Contribute
+# Contributing to WooCommerce ✨
 
-Community made patches, localizations, bug reports and contributions are always welcome and crucial to ensure WooCommerce remains the leading eCommerce platform for WordPress. WooCommerce currently powers 30% of all online stores across the internet, and your help making it even more awesome will be greatly appreciated :)
+There are many ways to contribute to the WooCommerce project!
 
-When contributing please ensure you follow the guidelines below to help us keep on top of things.
+- Translating strings into your language.
+- Answering questions on GitHub and within the various WooCommerce communities.
+- Submitting fixes, improvements, and enhancements.
 
-__Please Note:__
+WooCommerce currently powers 30% of all online stores across the internet, and your help making it even more awesome will be greatly appreciated :)
 
-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 [WooCommerce Support](https://woocommerce.com/contact-us/) for customer support, [WordPress.org](https://wordpress.org/support/plugin/woocommerce) for community support, and for customizations we recommend one of the following services:
+If you think something can be improved and you wish to contribute code,
+[fork](https://help.github.com/articles/fork-a-repo/) WooCommerce, commit your changes,
+and [send a pull request](https://help.github.com/articles/using-pull-requests/). We'll be happy to review your changes!
 
-- [WooExperts](https://woocommerce.com/experts/)
-- [Codeable](https://codeable.io/)
+## Feature Requests
+
+Feature requests can be [submitted to our issue tracker](https://github.com/woocommerce/woocommerce/issues/new?template=Feature_request.md). Be sure to include a description of the expected behavior and use case, and before submitting a request, please search for similar ones in the closed issues.
+
+Feature request issues will remain closed until we see sufficient interest via comments and [👍 reactions](https://help.github.com/articles/about-discussions-in-issues-and-pull-requests/) from the community.
 
-## Contributing to Core
+You can see a [list of current feature requests which require votes here](https://github.com/woocommerce/woocommerce/issues?q=label%3A%22votes+needed%22+label%3Aenhancement+sort%3Areactions-%2B1-desc+is%3Aclosed).
 
-### Reporting Issues
+## Technical Support / Questions
 
-Reporting issues is a great way to became 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/woocommerce/woocommerce/issues/new) if you spot a bug. Sound like something you're up for? Go for it!
+We don't offer technical support on GitHub so we recommend using the following:
 
-#### How To Submit An Issue Report
+**Reading our documentation**
+Usage docs can be found here: https://docs.woocommerce.com/
 
-If something isn't working, congratulations you've found a bug! Help us fix it by submitting an issue report:
+If you have a problem, you may want to start with the self help guide here: https://docs.woocommerce.com/document/woocommerce-self-service-guide/
 
-* Make sure you have a [GitHub account](https://github.com/signup/free)
-* Search the [Existing Issues](https://github.com/woocommerce/woocommerce/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.
+**Technical support for premium extensions or if you're a WooCommerce.com customer**
+ from a human being - submit a ticket via the helpdesk
+https://woocommerce.com/contact-us/ 
 
-### Making Changes
+**General usage and development questions**
+- WooCommerce Slack Community: https://woocommerce.com/community-slack/
+- WordPress.org Forums: https://wordpress.org/support/plugin/woocommerce
+- The WooCommerce Help and Share Facebook group
 
-Making changes to the core is a key way to help us improve WooCommerce. You will need some technical skills to make a change, like knowing a bit of PHP, CSS, SASS or JavaScript.
+**Customizations**
+- [WooExperts](https://woocommerce.com/experts/)
+- [Codeable](https://codeable.io/)
 
-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 :)
+## Coding Guidelines
 
-#### How To Submit A PR
+- **Ensure you stick to the [WordPress Coding Standards](https://make.wordpress.org/core/handbook/coding-standards/php/)**
+- Install our pre-commit hook using composer. It'll help with the Coding Standards. To install run `composer install` from the command line within the woocommerce plugin directory.
+- Ensure you use LF line endings in your code editor. Use [EditorConfig](http://editorconfig.org/) if your editor supports it so that indentation, line endings and other settings are auto configured.
+- 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 WooCommerce repository. Existing maintenance branches will be maintained by WooCommerce developers.
 
-* Fork the repository on GitHub
-* Make the changes to your forked repository
-  * **Ensure you stick to the [WordPress Coding Standards](https://make.wordpress.org/core/handbook/coding-standards/php/)**
-    * Install our pre-commit hook using composer. It'll help with the Coding Standards. To install just run `composer install`
-  * Ensure you use LF line endings - no crazy Windows line endings please :)
-    * Optionally it's possible install [EditorConfig](http://editorconfig.org/) on your editor to auto configure with indentation, line endings and other settings
-* 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 WooCommerce repository. Existing maintenance branches will be maintained by WooCommerce developers
-* Please **don't** modify the changelog - this will be maintained by the WooCommerce developers.
-* Please **don't** add your localizations or update the .pot files - these will also be maintained by the WooCommerce developers. To contribute to the localization of WooCommerce, please join the [translate.wordpress.org project](https://translate.wordpress.org/projects/wp-plugins/woocommerce). This is much needed, if you speak a language that needs translating consider yourself officially invited to the party.
+Please **don't** modify the changelog or update the .pot files. These will be maintained by the WooCommerce team.
 
-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.
+## Translating WooCommerce
 
-## Contribute To Localizing WooCommerce
+We have a [project on translate.wordpress.org](https://translate.wordpress.org/projects/wp-plugins/woocommerce). You can join the localization team of your language and help by translating WooCommerce. [Find more about using joining a language team and using GlotPress](https://make.wordpress.org/polyglots/handbook/tools/glotpress-translate-wordpress-org/).
 
-Localization is a very important part of WooCommerce. We believe in net neutrality and want our platform to be available to everyone, everywhere with equal ease. When you localize WooCommerce, you are helping hundreds of people in the world, and all the people who speak your language. That's pretty neat.
+If WooCommerce 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.
 
 ### Glossary & Style Guide
 
@@ -80,22 +86,8 @@ We don’t have a Style Guide template available, so feel free to create your ow
 
 If you created a style guide for your language, please let us know so we can add it in the list above. You can also add it by yourself by submitting a PR for this file.
 
-### Translating Core
-
-We have a [project on translate.wordpress.org](https://translate.wordpress.org/projects/wp-plugins/woocommerce). You can join the localization team of your language and help by translating WooCommerce. [Find more about using joining a language team and using GlotPress](https://make.wordpress.org/polyglots/handbook/tools/glotpress-translate-wordpress-org/).
-
-If WooCommerce 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.
-
 ### Translating Video Tutorials
 
 Another valuable way to help is by translating our growing library of WooCommerce video tutorials. Check out the [Translating  Our Videos](https://docs.woocommerce.com/document/translating-our-videos/) doc and join in!
 
 By translating video tutorials you'll be helping non-English speaking users and people affected by disabilities to get to grips with using WooCommerce for the first time, and to go on and create their businesses and make a living! That's something to be proud of and if you choose to dive into this area, we salute you.
-
-# Additional Resources
-
-* [General GitHub documentation](https://help.github.com/)
-* [GitHub pull request documentation](https://help.github.com/articles/about-pull-requests/)
-* [Translator Handbook](https://make.wordpress.org/polyglots/handbook/)
-* [WooCommerce Docs](https://docs.woocommerce.com/)
-* [WooCommerce Support](https://support.woocommerce.com)

.github/ISSUE_TEMPLATE/Bug_report.md

@@ -0,0 +1,34 @@
+---
+name: "\U0001F41E Bug report"
+about: Report a bug if something isn't working as expected in the core WooCommerce
+  plugin.
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is. Please be as descriptive as possible; issues lacking detail, or for any other reason than to report a bug, may be closed without action.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Isolating the problem (mark completed items with an [x]):**
+- [ ] I have deactivated other plugins and confirmed this bug occurs when only WooCommerce plugin is active.
+- [ ] This bug happens with a default WordPress theme active, or [Storefront](https://woocommerce.com/storefront/).
+- [ ] I can reproduce this bug consistently using the steps above.
+
+**WordPress Environment**
+<details>
+```
+Copy and paste the system status report from **WooCommerce > System Status** in WordPress admin.
+```
+</details>

.github/ISSUE_TEMPLATE/Enhancement.md

@@ -0,0 +1,17 @@
+---
+name: "✨ New Enhancement"
+about: "If you have an idea to improve an existing feature in core or need something for development (such as a new hook) please let us know or submit a Pull Request!"
+
+---
+
+**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/ISSUE_TEMPLATE/Feature_request.md

@@ -0,0 +1,17 @@
+---
+name: "\U0001F680 Feature request"
+about: "Suggest a new feature \U0001F389 We'll consider building it if it receives sufficient interest! \U0001F44D"
+
+---
+
+**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/ISSUE_TEMPLATE/Support.md

@@ -0,0 +1,22 @@
+---
+name: "❓ Support Question"
+about: "If you have a question \U0001F4AC please see our docs or use our forums, helpdesk,
+  or Slack Community!"
+
+---
+
+We don't offer technical support on GitHub so we recommend using the following:
+
+**Reading our documentation**
+Usage docs can be found here: https://docs.woocommerce.com/
+
+If you have a problem, you may want to start with the self help guide here: https://docs.woocommerce.com/document/woocommerce-self-service-guide/
+
+**Technical support for premium extensions or if you're a WooCommerce.com customer**
+ from a human being - submit a ticket via the helpdesk
+https://woocommerce.com/contact-us/ 
+
+**General usage and development questions**
+- WooCommerce Slack Community: https://woocommerce.com/community-slack/
+- WordPress.org Forums: https://wordpress.org/support/plugin/woocommerce
+- The WooCommerce Help and Share Facebook group

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,33 @@
+### All Submissions:
+
+* [ ] Have you followed the [WooCommerce Contributing guideline](https://github.com/woocommerce/woocommerce/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](../../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 ran tests with your changes locally?
+
+<!-- Mark completed items with an [x] -->
+
+### Changelog entry
+
+> Enter a short summary of all changes on this Pull Request. This will appear in the changelog if accepted.

.gitignore

@@ -38,9 +38,11 @@ tests/cli/vendor
 /tmp
 /tests/bin/tmp
 /tests/e2e-tests/config/local-*.json
+/tests/e2e-tests/config/local.json
 
 # Logs
 /logs
 
 # Composer
 /vendor/
+contributors.md