Contribute to Aeolus

There are several ways you can contribute to the Aeolus project:

• Report issues

• Help newcomers

• Develop

• Package

You can also help in other ways. If you would like to discuss anything, just get in touch via #aeolus IRC channel or aeolus-comm-mgmt mailing list.

Report issues

If you find a bug in Aeolus or if you think Aeolus is missing an important feature, let us know. Please try to report issues against the appropriate issue tracker – each Aeolus subproject has its own:

• Conductor issues

• Deltacloud issues

• ImageFactory issues

• Oz issues

• Tim issues

• Audrey issues

• Aeolus-configure issues

• CLI issues

• DevTools issues

• Website issues

Help newcomers

If you already have some knowledge of Aeolus, you can help newcomers get started by answering their questions on #aeolus IRC channel and aeolus-users mailing list.

Develop

You can help us build Aeolus itself. It’s best to first come to #aeolus IRC channel or aeolus-devel mailing list and discuss your plans with the rest of the community, so that your contribution gets integrated smoothly.

Here’s a bunch of helpful links:

• Aeolus project and Aeolus incubator on GitHub – the center of the universe for every Aeolus developer. Here you can find source code for the majority of the subprojects (for details see source code locations). We also use GitHub for issue tracking and accepting pull requests.

• Submitting pull requests – guide to Aeolus pull request process.

• Aeolus dev-tools – tools to help you set up a development environment for Conductor and CLI.

• How to compile Aeolus – instructions for compiling Aeolus components on Fedora/RHEL/CentOS.

Please take a look at issue lists for particular Aeolus subprojects to get inspiration on what could use some improvement.

Package

Currently we package for Fedora and CentOS. If you want to package Aeolus for some other distro, please let us know via #aeolus IRC channel or aeolus-comm-mgmt mailing list.