# Contributing Back - "Help Wanted"

**URL:** <https://forum.ansible.com/t/contributing-back-help-wanted/30632>\
**Category:** AWX Project\
**Tags:** awx\
**Created:** [June 21, 2019, 9:25pm UTC](https://forum.ansible.com/t/contributing-back-help-wanted/30632 "2019-06-21T21:25:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rpetrell](https://avatars.discourse-cdn.com/v4/letter/r/b4bc9f/32.png) [@rpetrell](https://forum.ansible.com/u/rpetrell)\
**Post date:** [June 21, 2019, 9:25pm UTC](https://forum.ansible.com/t/contributing-back-help-wanted/30632/1 "2019-06-21T21:25:28Z")

</div>

Hello everyone!

Since open sourcing AWX, we’ve noticed a huge uptick in contributions from the community. These contributions have come in many forms - oftentimes they’re code contributions, and other times they take the shape of people showing up on this mailing list and our IRC room to answer project questions or help others troubleshoot.

The AWX issue tracker at [https://github.com/ansible/awx/issues/](https://github.com/ansible/awx/issues/) is where we track bugs and feature enhancement requests - the project maintainers regularly comb through this list and maintain issues. Many times the issues that we see filed end up being users in the community who have questions about the project, or are looking for help diagnosing a particularly tricky setup (such as running AWX behind a reverse proxy, or integrating with third-party SSO/LDAP/SAML). Historically, we’ve directed these types of issues to the mailing list or IRC room.

While we are generally pretty active in replying to these types of issues, the AWX project maintainers spend the majority of their time working through bugs and enhancements so we can keep shipping the latest and greatest AWX. Going forward, we’re going to start labeling these issues in Github and keeping them open with a special help wanted label. For community members interested in diving in and helping us triage these types of issues, you can filter on them by visiting:

[https://github.com/ansible/awx/labels/help%20wanted](https://github.com/ansible/awx/labels/help%20wanted)

Happy Automating!

---

<div class="post-metadata">

**Author:** ![Juan\_A\_S](https://avatars.discourse-cdn.com/v4/letter/j/ba8739/32.png) [@Juan\_A\_S](https://forum.ansible.com/u/Juan_A_S)\
**Post date:** [June 23, 2019, 7:01pm UTC](https://forum.ansible.com/t/contributing-back-help-wanted/30632/2 "2019-06-23T19:01:08Z")

</div>

Ryan, how can I mark an issue as answered or resolved, or notify the administrator that an issue can be closed? I have seen some issues that can be easily answered or closed, for example, [https://github.com/ansible/awx/issues/1234](https://github.com/ansible/awx/issues/1234).

Thanks!

---

<div class="post-metadata">

**Author:** ![rpetrell](https://avatars.discourse-cdn.com/v4/letter/r/b4bc9f/32.png) [@rpetrell](https://forum.ansible.com/u/rpetrell)\
**Post date:** [June 24, 2019, 1:03pm UTC](https://forum.ansible.com/t/contributing-back-help-wanted/30632/3 "2019-06-24T13:03:21Z")

</div>

Juan,

Only the owner of the issue or somebody that’s an AWX maintainer can close an issue. Tagging just about anybody at the top of this list should give you what you need: [https://github.com/ansible/awx/graphs/contributors](https://github.com/ansible/awx/graphs/contributors)