Meta: Too many open issues

[christianlupus]

As @baradhili mentioned in this comment we have quite many open issues at the moment.

Although I confirm that this a unpleasant situation that puts (too) much pressure on the developer(s) and possible inteerested people, I think this is also a useful source of information what is non-functional and missing in PartKeepr. Not all of these issues are of high priority and quite a few might be invalid, I have to admit.

First, I wanted to create a single thread to discuss this instead of hijacking any other issue here.

To get around this whole situation, I suggest not to close the dangling issues. Instead, I propose to use the github internal features for peoject management to categorize and organize the issues. Here are som eideas, but this is to be discussed:

• Adding labels to the issues allows to separate between bugs, enhancements, search for support, and other topics.
• Adding milestones (including one called "future" or the like) allows to organize chronologically
• Usage of the projects feature to organize the issues
• Possible multiple projects (one for bugs, one for enhancements)

If the project starts to again work actively on the codebase, we could think of a sort of stale bot. But I think this should not be done as long as we are "offline". There might be some open issues, that are really to be closed. Here, it might be useful to warn the users once if the issue is still of interest and close only the ones that

• no one answers and
• seem to be related to individual problems (things like "I cannot uptade from x.xx to y,yy) to avoid loosing relevant information.

[christianlupus]

So in short: do we want a need-triage or similar to indicate.

[baradhili]

can we automatically add the needs-triage label under github's template system?

[christianlupus]

Yes, it is a matter of adding the label and changing one line in the template file. That should suffice.

[christianlupus]

I just opened #1097 regarding the issue templating system. If the needs-triage label is not wanted, I suggest removing the single commit.

[baradhili]

closing this now