Thanks for contributing to MultilingualPress (MLP)—you rock!
- For general information please refer to the MultilingualPress website.
- MLP should be backwards compatible with the two versions prior to the current stable version of WordPress.
- MLP respects the WordPress Coding Standards and follows additional conventions and best practices.
- If you want to translate MultilingualPress, you best do so by means of the official WordPress.org GlotPress.
- Make sure you have a GitHub account.
- See if your issue has been discussed (or even fixed) earlier. You can search for existing issues.
- Assuming it does not already exist, create a new issue.
- Clearly describe the issue including steps to reproduce when it is a bug.
- Make sure you fill in the earliest version that you know has the issue.
- Fork the repository on GitHub.
- Create a topic branch from where you want to base your work.
- This is usually the
masterbranch. - Only target release branches if you are certain your fix must be on that branch.
- To quickly create a topic branch based on the
masterbranch:git checkout -b issue/%YOUR-ISSUE-NUMBER%_%DESCRIPTIVE-TITLE% master- a good example is
issue/118_html_lang_attribute
- Please avoid working directly on the
masterbranch.
- This is usually the
- Make commits of logical units.
- Make sure your commit messages are helpful.
- If you want to work on assets, find all relevant files in the
resourcesfolder. There you can initialize grunt withnpm installand thengrunt watchyour changes.
- Push your changes to the according topic branch in your fork of the repository.
- Create a pull request to our repository.
- Wait for feedback. The MLP team looks at pull requests on a regular basis.
By contributing code to MultilingualPress, you grant its use under the GNU General Public License v3.