# New to Ansible Development

**URL:** <https://forum.ansible.com/t/new-to-ansible-development/18237>\
**Category:** Ansible Developer\
**Created:** [May 15, 2015, 3:24pm UTC](https://forum.ansible.com/t/new-to-ansible-development/18237 "2015-05-15T15:24:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ken\_Mitchell](https://avatars.discourse-cdn.com/v4/letter/k/5f9b8f/32.png) [@Ken\_Mitchell](https://forum.ansible.com/u/Ken_Mitchell)\
**Post date:** [May 15, 2015, 3:24pm UTC](https://forum.ansible.com/t/new-to-ansible-development/18237/1 "2015-05-15T15:24:52Z")

</div>

I have created some custom modules, but I want to get my feet wet contributing to Ansible. Considering working on some ansible-modules-core bugfixes. I’ve read CONTRIBUTING.md and README.md, and of course the docs. Should I just grab an issue and go then submit PR, or is there a specific workflow?

Also, not new to development nor git, but new-ish to github.

Thanks!

---

<div class="post-metadata">

**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\
**Post date:** [May 15, 2015, 3:51pm UTC](https://forum.ansible.com/t/new-to-ansible-development/18237/2 "2015-05-15T15:51:49Z")

</div>

Yep, just grab issue and submit PR, you might want to look at a few  
previous merged PRs to give you an idea of what we look for:

- keep documentation updated  
- strive for backwards compatibility (breaking existing playbooks is  
bad, but sometimes needed)  
- declarative is prefered over imperative interfaces  
- most modules need to be python 2.4 compatible, sometimes underlying  
library (i.e. boto/aws) trumps this.  
- use consistent naming with other ansible modules (aliases are  
permitted for those more familiar with underlying API used by module)