-1 I think it's totally valid to comment on a closed issue in case the problem was not actually fixed. I would rather discourage people from creating another issue for the same problem. We saw it quite a few times that somebody noticed that an issue was not properly resolved and then asked to reopen the thread. A new issue would act as a disconnect and would split the discussions.
-Marco On Fri, Feb 19, 2021, 09:32 Chaitanya Bapat <[email protected]> wrote: > Hello community, > > Issues that have been closed and without additional activity for over a > quarter are stale. In other open source communities, such issues are > handled by locking the conversation. > > *Advantage*: > - This prevents re-opening issues revolving around legacy/older versions > - Encourages users to post new issues > > *Disadvantage* > - Locking of issues might seem like administrative overreach to new users > or those unaware about the reasoning behind this locking decision. > > Looking around the open-source community, there's Angular JS which uses > automatic-lock-bot [1]. They explain the process [2] as to why locking is > beneficial. > > *Implementation*: > Lock-threads [3] is a github action that can be easily plugged into our > repository to facilitate the auto-lock functionality. It allows us to > configure various input parameters [most relevant one being: > issue-lock-inactive-days] > > I'm looking to hear from the community about what they feel regarding this > proposal. > > Thanks, > Chai > > [1] https://github.com/apps/angular-automatic-lock-bot > [2] https://github.com/angular/angular/blob/master/docs/GITHUB_PROCESS.md > [3] https://github.com/dessant/lock-threads > > -- > *Chaitanya Prakash Bapat* > *+1 (973) 953-6299* > > [image: https://www.linkedin.com//in/chaibapat25] > <https://github.com/ChaiBapchya>[image: https://www.facebook.com/chaibapat > ] > <https://www.facebook.com/chaibapchya>[image: > https://twitter.com/ChaiBapchya] <https://twitter.com/ChaiBapchya>[image: > https://www.linkedin.com//in/chaibapat25] > <https://www.linkedin.com//in/chaibapchya/> >
