[Hamlib-developer] Old issues in the GitHub issue tracker

[Nate B. <n0...@n0...>]

Like most I likely just look at no more than the first couple of pages
of the GitHub issue tracker.  As the number is at 195 open issues, it
becomes a chore to start wading deeper into the pool and it becomes easy
to decide to do something else.

On the Issue page one can select the order shown to be oldest first and
I've been looking at some of those and have closed a couple.  The oldest
issues are just over five years old and in many cases the project has
resolved these issues but no followup was done because it may have been
forgotten that an issue had been opened months or years before.

In other cases, Mike opened a number of issues with enhancement ideas.
Some of these seem more doable than others but to the person with the
right motivation, they would be a useful challenge and addition.  I'm
hesitant to close these no matter how old they get unless there is
sufficient feedback along the lines of, "No, this doesn't fit within the
scope of Hamlib."

Fortunately, for the issues that are labeled, filters can be applied to
limit the list.  To make this work, it's likely that I need to assure
there are relevant labels applied to each issue.  I can also add a
"Type" that is currently limited to four--None, Feature, Bug, and Task.
This will produce a more general list that could be narrowed with the
filter.  Also, I can add multiple labels to an issue but only one type.

I'll start working my way through the list adding types and labels.
Nearly all of the issues will be assigned a type of either Feature or
Bug, then labels can give an indication of what it entails.  Once
complete, anything with the Bug type should be looked at and fixed or
closed.

73, Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819