I think stalebot is not a good solution for Issues. It is good for PRs (PRs age much faster than issues and usually if you have not touched the code for a few weeks, it's better to start from the beginning, unless you continuously upgrade and "refresh" it.
I do think, however (following what Elad wrote) that organizing the issues might be a better idea to some extent. And here, I think help from volunteers from the community - not only committers - might be super valuable. There is a discussion recently about using the new (still in public beta) Triage "level" for access in the project and I think what I liked most is giving everyone from the community an automatically Trage level of access. I would be all for it. Maybe there are more people in the community, who would like to help with that - similar to Elad? If so, maybe then we can ask the infrastructure to enable the Triage level for us, work out some general ideas on how we would like to organize the issues, document that, and ask our community to help with that? This might be a road to commitership as well for people who are not necessarily coders. Something that we had a talk at the Airflow Summit (https://youtu.be/wxn9ta13Gbo) ? Maybe we can pioneer and experiment with that for the whole ASF and help to reach the decision by showing example :). Here are the discussions in ASF about the "Triage" level: Incubator: https://lists.apache.org/thread.html/r497c5bf9a68e631bc93274e65beb3e28b769ce21e55961407adc5d10%40%3Cgeneral.incubator.apache.org%3E DevCom discussion: https://lists.apache.org/thread.html/r617c960eae5a33e8f911c8606f93b6826f2724b3260553a162e2f9f4%40%3Cdev.community.apache.org%3E J. On Thu, Sep 10, 2020 at 4:09 PM Elad Kalif <elad...@gmail.com> wrote: > If I opened a bug report - what is the action expected from my side to keep > it alive? > Am I supposed to comment on it every 30 days? > > Check https://github.com/apache/airflow/pull/10760 was picked after being > open for 3+ months. > Keep in mind that not always the person who reports the issue also has the > skills to create a PR and address it. > > Is the actual problem the amount of open issues or the lack of labeling to > specific areas/providers so it's hard to navigate and manage the list? > I'm volunteering to help with labeling of current open issues if needed > > elad > > On Thu, Sep 10, 2020 at 3:54 PM Ash Berlin-Taylor <a...@apache.org> wrote: > > > I'm not a fan of these bots for issues. > > > > Yes, we have a lot of open issues, but I find it far more demotivating > > to stumble across an issue on a project only to find it closed due to > > inactivity -- even if it is still a problem. > > > > -ash > > > > On Sep 10 2020, at 1:22 pm, Ry Walker <r...@rywalker.com> wrote: > > > > > I agree that stalebot is a best practice and we should use it, and 30d > > > sounds like a good starting point. > > > > > > On Thu, Sep 10, 2020 at 7:56 AM Tomasz Urbaszek <turbas...@apache.org> > > > wrote: > > > > > >> Hi all, > > >> > > >> Currently, we have about 582 open issues on Github. The oldest opened > > >> in March. Do you think we should consider using stale bot as we do for > > >> PRs? > > >> > > >> I don't think that issue that is open since March is "so important" to > > >> keep it still open. This would also automate the process of verifying > > >> the issue (the author will be notified and asked for an update). If > > >> the issue is something that we want to keep open we should be able to > > >> use the "pinned" label. > > >> > > >> Other projects use it and I don't see anything wrong with it. I would > > >> say that 30d is a good period for keeping an issue open. > > >> > > >> What do you think? > > >> > > >> Bests, > > >> Tomek > > >> > > > > > > -- Jarek Potiuk Polidea <https://www.polidea.com/> | Principal Software Engineer M: +48 660 796 129 <+48660796129> [image: Polidea] <https://www.polidea.com/>
