You are reading an unmaintained version of the Ansible documentation. Unmaintained Ansible versions can contain unfixed security vulnerabilities (CVE). Please upgrade to a maintained version. See the latest Ansible documentation.

How can I help?

Become a power user
Ask and answer questions online
Review, fix, and maintain the documentation
Participate in your local meetup
File and verify issues
Review and submit pull requests
Become a collection maintainer
Join a working group
Teach Ansible to others
Social media

Thanks for being interested in helping the Ansible project!

There are many ways to help the Ansible project…but first, please read and understand the Community Code of Conduct.

Become a power user 

A great way to help the Ansible project is to become a power user:

Use Ansible everywhere you can
Take tutorials and classes
Read the official documentation
Study some of the many excellent books about Ansible
Get certified.

When you become a power user, your ability and opportunities to help the Ansible project in other ways will multiply quickly.

Ask and answer questions online 

There are many forums online where Ansible users ask and answer questions. Reach out and communicate with your fellow Ansible users.

You can find the official Ansible communication channels.

Review, fix, and maintain the documentation 

Typos are everywhere, even in the Ansible documentation. We work hard to keep the documentation up-to-date, but you may also find outdated examples. We offer easy ways to report and/or fix documentation errors.

Participate in your local meetup 

There are Ansible meetups all over the world. Join your local meetup. Attend regularly. Ask good questions. Volunteer to give a presentation about how you use Ansible.

If there is no meetup near you, we are happy to help you start one.

File and verify issues 

All software has bugs, and Ansible is no exception. When you find a bug, you can help tremendously by telling us about it.

If the bug you found already exists in an issue, you can help by verifying the behavior of the reported bug with a comment in that issue, or by reporting any additional information.

Review and submit pull requests 

As you become more familiar with how Ansible works, you may be able to fix issues or develop new features yourself. If you think you have a fix for a bug in Ansible, or if you have a new feature that you would like to share with millions of Ansible users, read all about the Ansible development process and and how to contribute to collections to learn how to get your code accepted into Ansible.

Another good way to help is to review pull requests that other Ansible users have submitted. The Ansible community keeps a full list of open pull requests by file, so if a particular module or plugin interests you, you can easily keep track of all the relevant new pull requests and provide testing or feedback.

Become a collection maintainer 

Once you have learned about the development process and have contributed code to a collection, we encourage you to become a maintainer of that collection. There are hundreds of modules in dozens of Ansible collections, and the vast majority of them are written and maintained entirely by members of the Ansible community.

To learn more about the responsibilities of being an Ansible module maintainer, please read our collection maintainer guidelines.

Join a working group 

Working groups are a way for Ansible community members to self-organize around particular topics of interest. We have working groups around various topics. To join or create a working group, please read the Ansible Working Groups.

Teach Ansible to others 

We are working on a standardized Ansible workshop that can provide a good hands-on introduction to Ansible usage and concepts.