# Major yum and dnf refactor: requesting feedback and testing **URL:** \ **Category:** Ansible Developer\ **Created:** [August 3, 2018, 4:47am UTC](https://forum.ansible.com/t/major-yum-and-dnf-refactor-requesting-feedback-and-testing/28246 "2018-08-03T04:47:42Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![maxamillion](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/maxamillion/32/98_2.png) [@maxamillion](https://forum.ansible.com/u/maxamillion)\ **Post date:** [August 3, 2018, 4:47am UTC](https://forum.ansible.com/t/major-yum-and-dnf-refactor-requesting-feedback-and-testing/28246/1 "2018-08-03T04:47:42Z")
Hello all,     I have recently opened a pull request that contains a bit of work to heavily refactor both the yum and dnf modules in hopes of making them easier to maintain going forward and also bring them into feature parity[0]. The initial goal is to ensure that the dnf module can do everything the yum module can do, but the intent is that the dnf module will be at liberty to extend beyond the yum module's functionality as upstream dnf continues to add new functionality that will never get backported to yum. Another goal will be achieved via a secondary pull request once this one is merged, which will add an action plugin for yum that will handle the hand off to the appropriate back-end module (yum or dnf) in service of yum4[1] compatibility (yum4 has a dnf backend and not a yum3 backend), but that is relatively out of scope for the discussion and testing of this pull request. I wanted to mention it for frame of reference and in hopes to justify the newly shared module arg spec. I welcome comments either in thread or in GitHub. Thank you, -AdamM [0] - [https://github.com/ansible/ansible/pull/43621](https://github.com/ansible/ansible/pull/43621) [1] - [https://wiki.centos.org/SpecialInterestGroup/ConfigManagementSIG/YUM4](https://wiki.centos.org/SpecialInterestGroup/ConfigManagementSIG/YUM4)