|
| 1 | +# Contributing to Magento 2 code |
| 2 | + |
| 3 | +## Overview |
| 4 | + |
| 5 | +Contributions to the Magento 2 codebase are done using the fork & pull model. |
| 6 | +This contribution model has contributors maintaining their own copy of the forked codebase (which can easily be synced with the main copy). The forked repository is then used to submit a request to the base repository to “pull” a set of changes (hence the phrase “pull request”). |
| 7 | + |
| 8 | +Contributions can take the form of new components/features, changes to existing features, tests, documentation (such as developer guides, user guides, examples, or specifications), bug fixes, optimizations or just good suggestions. |
| 9 | + |
| 10 | +The Magento 2 development team will review all issues and contributions submitted by the community of developers in the first in, first out order. During the review we might require clarifications from the contributor. If there is no response from the contributor for two weeks, the issue is closed. |
| 11 | + |
| 12 | +## Contribution requirements |
| 13 | + |
| 14 | +1. Contributions must adhere to [Magento coding standards](http://devdocs.magento.com/guides/v2.0/coding-standards/bk-coding-standards.html). |
| 15 | +2. Pull requests (PRs) must be accompanied by a meaningful description of their purpose. Comprehensive descriptions increase the chances of a pull request to be merged quickly and without additional clarification requests. |
| 16 | +3. Commits must be accompanied by meaningful commit messages. |
| 17 | +4. PRs which include bug fixing, must be accompanied with step-by-step description of how to reproduce the bug. |
| 18 | +5. PRs which include new logic or new features must be submitted along with: |
| 19 | + * Unit/integration test coverage where applicable. |
| 20 | + * Updated documentation in the `docs` directory at the root level. |
| 21 | +6. For large features or changes, please [open an issue](https://github.com/magento/magento2/issues) and discuss first. This may prevent duplicate or unnecessary effort, and it may gain you some additional contributors. |
| 22 | +7. All automated tests are passed successfully locally. After PR submitted Magento team will run builds on continuous integration environment. |
| 23 | + |
| 24 | +## Contribution process |
| 25 | + |
| 26 | +If you are a new GitHub user, we recommend that you create your own [free github account](https://github.com/signup/free). By doing that, you will be able to collaborate with the Magento 2 development team, “fork” the Magento 2 project and be able to easily send “pull requests”. |
| 27 | + |
| 28 | +1. Search current [listed issues](https://github.com/magento/magento2-page-builder/issues) on GitHub (open or closed) before starting work on a new contribution. |
| 29 | +2. Review the [Contributor License Agreement](https://magento.com/legaldocuments/mca) if this is your first time contributing. |
| 30 | +3. Create and test your work. |
| 31 | +4. Fork the Magento 2 repository according to [Fork a repository instructions](http://devdocs.magento.com/guides/v2.0/contributor-guide/contributing.html#fork) and when you are ready to send us a pull request – follow [Create a pull request instructions](http://devdocs.magento.com/guides/v2.0/contributor-guide/contributing.html#pull_request). Instructions written for `https://github.com/magento/magento2` repository, but they also apply to `https://github.com/magento/magento2-page-builder`. |
| 32 | +5. Once your contribution is received, Magento 2 development team will review the contribution and collaborate with you as needed to improve the quality of the contribution. |
| 33 | + |
| 34 | +## Code of Conduct |
| 35 | + |
| 36 | +Please note that this project is released with a Contributor Code of Conduct. We expect you to agree to its terms when participating in this project. |
| 37 | +The full text is available in the repository [Wiki](https://github.com/magento/magento2/wiki/Magento-Code-of-Conduct). |
0 commit comments