phlask-map Issues sorting: Phase 1

[affabillyty]

As a user, I need to be able to open up the PHLASK GitHub and understand the following:

1. Which work is ready to go and be tackled
2. Which work is oriented as "good first issues" for newcomers
3. What aptitude level might be needed to do the work (novice, intermediate, advanced)

Goal: have 3-5 "Good first issues" ready to go on the Kanban board for a new user to find

Things to consider:

• What labels should be used
• How can the titles be understood by a newcomer
• What context/history should be in each issue for the user to understand it
• What pictures/screenshots might be helpful

Please engage Development conveners and other tenured technical contributors to help prepare/update the tickets

[affabillyty]

Billy idea: Look for tickets labeled "Bug" as potential places to start. If you read the ticket and the Bug appears to still be present, that ticket likely needs to remain and could be converted into a "Good First Issue." If we can't reproduce the Bug, it may have been fixed elsewhere and it's a good opportunity to take note of that ticket to see if we can close it.