I tag all new issues that come as “Feature Request”, “Bug”, etc. and then as far as I’m concerned, unless I’m interested in the issue, my work is done.
Those then serve as an excellent roadmap for anyone who wants to contribute, but my projects are built for me and I work on the parts I want and need.
I also use GH automation to auto-close issues after a year. If no one cares enough to implement the change in a year, no one cares.
Your project is yours, feel free to ignore everyone else.
I would be careful about auto-closing issues after a year. It's quite possible that some issues are genuine but for various reasons (time required, difficulty of the problem, etc...) people might not do anything about it right away. You can check the feature requests or bugs databases for large projects like Firefox or WebKit for example and find plenty of entries that are several years old yet those entries often still have comments being made which shows that at least some people care about them.
I find the use of “she” throughout your site when referring to an automated code process to be fairly strange. I suspect you’re trying to add levity and personality, but it’s an odd thing to assign gender to. Perhaps consider replacing those with “it”?
Apparently someone asked the same question - from the FAQ:
> Danger keeps getting referred to as “her/she”, what gives?
> When we were in the naming process of Danger, we went through a lot of names. In the end, it got named after Gem “Danger” McShane, who was involved in both the copy and the concept. While not a programmer herself, she’s helped out with trying to understand the personality behind the project. Danger, the project, is a female, northern UK, command-line app into 80’s punk/indie. Inspired by community efforts like the Haçienda / Factory Records.
> Understandably, applying a gender to a genderless concept comes with it’s own complications. To make it worse, female genders tend to be applied towards “digital assistants” which should raise questions on outdated-but-still-persisting gender stereotypes and patriarchical power structures. There is no answer that can completely absolve the disconnect I’m afraid.
At the risk of pumping my own project, and recognizing that this is an untested methodology, I've just recently created this project to do exactly that:
Windows support is being tracked in issue #103 on GitHub. People have had success building from source. Automated Windows builds currently fail for reasons unknown.
Those then serve as an excellent roadmap for anyone who wants to contribute, but my projects are built for me and I work on the parts I want and need.
I also use GH automation to auto-close issues after a year. If no one cares enough to implement the change in a year, no one cares.
Your project is yours, feel free to ignore everyone else.
I also highly recommend watching this talk by Pieter Hintjens a couple of times. It is brilliant https://m.youtube.com/watch?v=uzxcILudFWM
(I’m the creator of WTFUtil).