These are the contribution guidelines for the SPHERE.IO JVM SDK 1.x and SPHERE.IO Sunrise shop template.

Contributions are welcome!

## Contribution process for all committers

1. on bigger effort changes: open an issue and ask if you can/should/need to help
1. fork the repository
1. produce production code and unit tests (tests can be omitted on pure documentation changes like typos)
1. make a pull request
1. @lauraluiz and @schleichardt will review and optionally merge

## Requirements for a pull request

We want to have a clear and tested code base.

* change as few lines as possible
* never reformat code, we want in diffs only real changes
* use code formatting like in the rest of the application
* use the namespace io.sphere.sdk
* don't commit code which emmits warnings like unchecked generics
* you need to use tests to prove that your code works, JUnit tests are sufficient
* production code should be in Java
* your code is from you and not copied from third party sources
* use [good commit messages](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
* tests have to be passed in Travis CI
* the SDK should be backwards compatible when released as 1.0.0

These are the contribution guidelines for the SPHERE.IO JVM SDK 1.x and SPHERE.IO Sunrise shop template.

Contributions are welcome!

## Contribution process for all committers

1. on bigger effort changes: open an issue and ask if you can/should/need to help
1. fork the repository
1. produce production code and unit tests (tests can be omitted on pure documentation changes like typos)
1. make a pull request
1. @lauraluiz and @schleichardt will review and optionally merge

## Requirements for a pull request

We want to have a clear and tested code base.

* change as few lines as possible
* never reformat code, we want in diffs only real changes
* use code formatting like in the rest of the application
* use the namespace io.sphere.sdk
* your committed code should not emit warnings such as unchecked generics
* you need to use tests to prove that your code works, JUnit tests are sufficient
* production code should be in Java
* your code is from you and not copied from third party sources
* use [good commit messages](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
* tests have to be passed in Travis CI
* the SDK should be backwards compatible when released as 1.0.0

Update sentence about code warnings in contribution guidelines.
Update sentence about code warnings in contribution guidelines.