Message-ID: <1200566685.4300.1485865458435.JavaMail.confluence@ip-10-127-227-164> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_4299_731732276.1485865458435" ------=_Part_4299_731732276.1485865458435 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html Q: How can I contribute to eZ Publish's development?

Q: How can I contribute to eZ Publish's development?

eZ Publish is a fully open source and community-driven project. = Code contributions are simply done via github Pull Requests.

Contribu= te

Workflow

Remember to first create a issue in our issue tracker and refer to it = in commits and Pull Requests headers.

Examples:

"Implement EZP-201xx: Add support for X in Y"

"Fix EZP-20104: ContentController should return error status when conte= nt is not found"

Keep different changes in different commits in case cherry-pick= is preferred instead of a merge later.

A Pull Request should only cover one issue.

A commit should not contain code changes at the same time as doing codi= ng standards/whitespace/typo fixes.

If you want to contribute implementation specification proposals, place the= m in=20 doc/ folder.

Tes= ting

TDD: Write/Change the test(s) for the change you do and commit = it before you do the actual code change
If a bug affects Public API, write or enhance a integration test to mak= e sure the bug is covered.
Unit tests should only use mocks/stubs and never test = the full stack like integrations tests does.
Please test/check your commits before pushing:
Run unit tests and integration test before commits

Make sure you follow our=20 coding standards

See also
For further information please have a look at the rela= ted guidance page.

Learn

You will, amongst other, learn how to make pull-requests. More on this here= :=20 "How to contribute = to eZ Publish using GIT".

------=_Part_4299_731732276.1485865458435--