# Close issues on GitHub!

**URL:** <https://discourse.mc-stan.org/t/close-issues-on-github/242>\
**Category:** Developers\
**Created:** [February 5, 2017, 10:56pm UTC](https://discourse.mc-stan.org/t/close-issues-on-github/242 "2017-02-05T22:56:10Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![syclik](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.mc-stan.org/syclik/32/6_2.png) [@syclik](https://discourse.mc-stan.org/u/syclik)\
**Post date:** [February 5, 2017, 10:56pm UTC](https://discourse.mc-stan.org/t/close-issues-on-github/242/1 "2017-02-05T22:56:11Z")

</div>

I’d highly recommend closing issues that we can’t make progress on due to not enough specification. Would anyone mind if I created a tag for “needs more detail” or something like that? Ideally, we would be able to either add enough detail to remove that tag or close it after some time.

Thanks, @Bob_Carpenter, for closing a few issues. I’ll follow your lead and clean up as many issues as I can.

---

<div class="post-metadata">

**Author:** ![seantalts](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.mc-stan.org/seantalts/32/32_2.png) [@seantalts](https://discourse.mc-stan.org/u/seantalts)\
**Post date:** [February 6, 2017, 5:43pm UTC](https://discourse.mc-stan.org/t/close-issues-on-github/242/2 "2017-02-06T17:43:55Z")

</div>

Sounds like a good idea to me.

---

<div class="post-metadata">

**Author:** ![Bob\_Carpenter](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.mc-stan.org/bob_carpenter/32/9230_2.png) [@Bob\_Carpenter](https://discourse.mc-stan.org/u/Bob_Carpenter)\
**Post date:** [February 9, 2017, 7:09pm UTC](https://discourse.mc-stan.org/t/close-issues-on-github/242/3 "2017-02-09T19:09:21Z")

</div>

I agree that a label would be helpful. Mind adding one, Sean? We need it on at least the math and stan repos.

I always try to ask for clarification when issues come in, but then I forget until I do big passes over them. So it’ll be great to be able to find all the ones that need clarification.

I think what we want is issues that are technical specs, not just generic feature requests. Othewise, we should discuss on mailing list or Wiki or in a Google doc or whatever.
