Meta: autoclosing issues

[ezzra]

sorry I am a bit confused if contributions via issues are wanted in this repo? After using listmonk a bit for the first time I created these 3 issues:

• Show list name in "confirm subscription" mails even for private lists #2790
• Move "Logo URL" and "Favicon URL" to Appearance setting #2791
• Allow to set language in users profile #2792

and they were unanswered, thats ok in open source projects as people do this in their free-time.

But why are they automatically auto closed as "not planned"? Seems a bit strange to me, I guess the problems addressed there still remain and nobody decided that they should not be fixed but just nobody had the time or desire to tackle them, which is ok, but why not just leave them open as the problem remains 🤔

[knadh]

Hi @ezzra. I introduced autoclosing last year because as the sole maintainer, it was getting really difficult to organize and keep track of issues (mostly feature and enhancement requests). If an issue has received 0 comments or has not been assigned to a user within a 5 month period, then it's "closed" to move it away from the main view. That's a reasonably good signal that the issue is not critical/there isn't attention from many users/maintainer(s) don't have the bandwidth.

What's important here is that it's always possible to comment on "Closed" issue to revive it. Issues aren't locked preventing commenting (which would've been bad).

PS: The 'Not planned' message is just what the workflow posts by default. That can be changed if that's what's confusing: https://github.com/knadh/listmonk/blob/master/.github/workflows/issues.yml