# PRs getting stale

**URL:** <https://forum.ansible.com/t/prs-getting-stale/25038>\
**Category:** Ansible Developer\
**Created:** [July 21, 2017, 1:49am UTC](https://forum.ansible.com/t/prs-getting-stale/25038 "2017-07-21T01:49:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sdodsley](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sdodsley/32/655_2.png) [@sdodsley](https://forum.ansible.com/u/sdodsley)\
**Post date:** [July 21, 2017, 1:49am UTC](https://forum.ansible.com/t/prs-getting-stale/25038/1 "2017-07-21T01:49:27Z")

</div>

Hi team

This is my first foray into this group, so sorry if I’m breaking any protocols here…

I have 3 PRs waiting to be approved that are for a new storage module. The base PR has already been merged and these are the remaining modules submitted in bulk as per the contribution instructions.

No one seems to be looking at these and now they have stale\_ci labels.

Can someone explain the timescales for getting PRs approved and merged so I have an idea when I can expect some activity?

The PR #s are 26355, 26356 and 26357.

Thanks

Simon

> **Simon Dodsley MBCS CITP** | Director, New Stack Technologies

> Pure Storage, Inc. | One Penn Plaza – Suite 3430, New York, NY 10119

> t: +1 (510) 516-2682 | [simon@purestorage.com](mailto:simon@purestorage.com) | [www.purestorage.com](http://www.purestorage.com/)

[![cid:image001.png@01D2F67A.06F1F950](https://us1.discourse-cdn.com/ansible/original/2X/6/67ac4e9637833b6d0f5e539a5118a03c922d40f5.png)](http://code.purestorage.com/) ![http://www.purestorage.com/_media/header_logo.png?130529](https://us1.discourse-cdn.com/ansible/original/2X/d/d114eec37dea5e1637d5b3fdf1c9c14bde8cf875.png)

---

<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:** [July 21, 2017, 3:40pm UTC](https://forum.ansible.com/t/prs-getting-stale/25038/2 "2017-07-21T15:40:18Z")

</div>

There is no firm schedule, specially for ‘community’ supported modules, they require community members to review and approve.

The core team, as part of the community, can also review and approve, but the main focus is on ‘core’ labeled items.
