Please read our Contributing guide lines first.
+You can find any required library for this project in the requirements.txt:
+autopep8==1.3.5
+docutils==0.14
+guzzle-sphinx-theme==0.7.11
+-e git://github.com/miyakogi/m2r@dev#egg=m2r
+pep8==1.7.1
+pycodestyle==2.4.0
+six==1.11.0
+Sphinx==1.7.5
+sphinxcontrib-log-cabinet==1.0.0
+sphinxcontrib-websupport==1.1.0
+twine==1.11.0
+
NOTE: Make sure to have also all the extensions listed in the docs/conf.py that are required for the SDK Documentation.
+In addition, you need nodejs/npm with globally installed module auto-changelog in case you want to generate an update changelog version. +We suggest to use nvm.
+We suggest to use Visual Studio Code with installed plugins for Python Development described here. But if you prefer any other IDE / Editor, it is fine.
+There are up to no automated tests realized, but planned to come in short.
+Code validation and auto-fixing can be run by
+./scripts/pep8fix.sh
+# to autofix possible issues
+
+./scripts/pep9check.sh
+# to check for issues left
+
Please fix all issues before creating a PR.
+We care then about the rest - no need to worry about things like building current realease and versioning.
+You can stop here.
+The below sections are just for our reference. +TIA for your PR and thus for your support of this project. As we have further SDKs in other languages, it might take a bit of time to check if we can role out that PR as we want to keep all our SDKs aligned.
+We use SemVer for versioning. For the versions available, see the tags on this repository.
+Merge the desired changes in case tests and code validation succeed. +Then create a new tag version by
+git tag -a v1.2.3 master
+# please replace the semver version accordingly
+
+git push --tags
+# push the tags to remote
+
Create a new release out of that new tag and provide release details about the changes applied in the git interface. In case of breaking changes, describe what has changed and how to migrate.
+Changes will be auto-deployed by a webhook to readthedocs.org and automatically updated on github pages.
+Publish your changes to the Python Package Index (PyPi) by
+./scripts/createdistribution.sh
+# to create packages of the new distribution
+
+./scripts/uploaddistribution_test.sh
+# to upload the generated packages to the PyPi Test Index (test.pypi.org)
+
+./scripts/uploaddistribution_live.sh
+# to upload the generated packages to the PyPi Index (pypi.org)
+
The module can be accessed on the PyPi (Live) Index and the PyPi (Test) Index.
+Have an eye on the generated SDK Documentation.
+If you want to generate it from scratch out of the sources, please use composer together with our project as follows:
+./scripts/generatedocs.sh
+
The generated files are then available in subfolder “docs/_build/html”. Commit and push the changes.
+After having changes merged and released, run
+./scripts/changelog.sh
+
Commit and push the changes.
+