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 > >> > > >
