Ensure there are enough "good first patch" issues for new-to-track contributors

When this issue is open, it means that we need to create more issues.

At any given time, we would like between 10-20 open issues with the label "good first patch". This makes for easy pickings for anyone wanting to try their hand at contributing to the track.

Here's that backlog:
https://github.com/exercism/xjava/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+patch%22

When:

  • that list is fewer than 10, whenever you see a little thing that needs to be addressed, rather than do it yourself, capture it in one or more bite-sized issues. Be sure to label it "good first patch".
    • if this issue is closed, re-open it... it's our semaphore that issues need to be created.
    • you can even consider it one of the many things you do in maintaining the track.
  • that list is more than 20, feel free to take care of nips-and-tucks since we have plenty of runway.
    • if this issue is open, close it... it's our semaphore that no more issues are needed.

Maintainers: the issues list without "good first patch"