Skip to content

Contribution Guide

Daniel Kontšek edited this page Dec 25, 2016 · 8 revisions

Contribution Guide

We are happy with any volunteers involvement in Danube Cloud. If you would like to help us, there are multiple ways to do so. Depending on your skills and type of work you would like to do (doesn’t have to be development), we encourage you to start with any of the following:

Write a blog post, get involved in social media or make a speech

You can help out by spreading the word about Danube Cloud, or join our community and help others or share your ideas and experiences with people in community.

Update documentation

The official user guide is used to guide users the right way. If you don't know how to do something, we probably missed it in the user guide. Documentation is a never ending process so we welcome any improvement suggestions, feel free to create issues in the esdc-docs bug tracker.

Create VM images

Our image repository currently consists only of few basic VM images. If you create an image and think that others could also benefit from using it, just give us a shout, and we will be happy to add your image to our repository. You may also be interested in our image machinery, which we use to maintain our images (appliances).

Suggest an improvement, or report a bug

All issues are handled in the esdc-ce issue tracker, if you've found a bug please create an issue for it. For security related issues please send GPG encrypted emails to [email protected], by using our public GPG key.

If there is something you are missing, and wish to be implemented in Danube Cloud, feel free to create an issue and mark it as an enhancement.

Contributing code to esdc-ce

All development is done on Github, create your own fork, bootstrap your development environment and you are ready to write some code. Once you are happy with your changes create a pull request and we will review and merge it as soon as we can. To make our review easier please do all your work in a separate branch, if there is a bug for your change ideally include the bug number in the branch name.

Programming rules and style conventions

Contributing code to other esdc-* repositories

TODO

Clone this wiki locally