# \[Vote ended on 2026-02-19\] Possibly unmaintained collection: awx.awx

**URL:** <https://forum.ansible.com/t/vote-ended-on-2026-02-19-possibly-unmaintained-collection-awx-awx/44706>\
**Category:** Project Discussions\
**Tags:** awx, community-wg, collections\
**Created:** [October 18, 2025, 1:45pm UTC](https://forum.ansible.com/t/vote-ended-on-2026-02-19-possibly-unmaintained-collection-awx-awx/44706 "2025-10-18T13:45:48Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![MalfuncEddie](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/malfunceddie/32/428_2.png) [@MalfuncEddie](https://forum.ansible.com/u/MalfuncEddie)\
**Post date:** [February 10, 2026, 6:59pm UTC](https://forum.ansible.com/t/vote-ended-on-2026-02-19-possibly-unmaintained-collection-awx-awx/44706/13 "2026-02-10T18:59:05Z")

</div>

@mariolenz maybe this helps?

> [@AWX modernization: Moving forward](https://forum.ansible.com/t/awx-modernization-moving-forward/45134):
>
> Hi folks, I’d like to give an update on the AWX modernization effort. Before we dive in, let’s briefly recap the [goals we defined](https://forum.ansible.com/t/refactoring-awx-into-a-pluggable-service-oriented-architecture/7404) for refactoring AWX into a pluggable, service-oriented architecture: Improved Flexibility: Easier to implement changes and add new features. Enhanced Maintainability: Simplified codebase with clear service boundaries. Better Code Reuse: More efficient reuse of code across different projects. Active Community Participation: Greater opportunity for community members …

> Blockquote  
> In short, the AWX refactoring effort is nearing completion and there is no longer the need to use multiple branches for development. However there is still work to be done in our efforts to modernize the AWX codebase.

---

_[View the full topic](https://forum.ansible.com/t/vote-ended-on-2026-02-19-possibly-unmaintained-collection-awx-awx/44706)._