# (developers) Modules go for "commonality" upgrades

**URL:** <https://forum.ansible.com/t/developers-modules-go-for-commonality-upgrades/11707>\
**Category:** Ansible Project\
**Created:** [July 20, 2012, 11:40pm UTC](https://forum.ansible.com/t/developers-modules-go-for-commonality-upgrades/11707 "2012-07-20T23:40:24Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\
**Post date:** [July 20, 2012, 11:40pm UTC](https://forum.ansible.com/t/developers-modules-go-for-commonality-upgrades/11707/1 "2012-07-20T23:40:24Z")

</div>

For those that want to help port existing modules to use the new  
"common code" stuff, I have decided that the classes used (as detailed  
I prior emails) are fine to start with.

Go ahead and have at!

I will hold up the release until we're 100% ported, so we don't have  
the "this one works different" discussion again. The command  
module should subclass the AnsibleModule code because it works a  
little different.

--Michael