# Proposal: close old feature-request issues (Language summit follow up)

**URL:** <https://discuss.python.org/t/proposal-close-old-feature-request-issues-language-summit-follow-up/15776>\
**Category:** Core Development\
**Created:** [May 15, 2022, 10:06pm UTC](https://discuss.python.org/t/proposal-close-old-feature-request-issues-language-summit-follow-up/15776 "2022-05-15T22:06:47Z")\
**Posts on this page:** 1\
**Showing post:** 27

<div class="post-metadata">

**Author:** ![AA-Turner](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/aa-turner/32/4979_2.png) [@AA-Turner](https://discuss.python.org/u/AA-Turner)\
**Post date:** [May 16, 2022, 7:50pm UTC](https://discuss.python.org/t/proposal-close-old-feature-request-issues-language-summit-follow-up/15776/27 "2022-05-16T19:50:39Z")

</div>

> [@erlendaasland](#):
>
> Oh, another observation; a large piece of the issue cake is `doc` -labelled issues 🍰 It would be interesting to see if we could make _that_ particular subset more manageable by using GitHub Projects.

We discussed this at the start of May in the documentation team meeting — I’d be keen to help with any ideas around this, as documentation issues are fairly user/programmer-visible.

A

---

_[View the full topic](https://discuss.python.org/t/proposal-close-old-feature-request-issues-language-summit-follow-up/15776)._