<meta> Issue/bug prioritization?
@GoogleFrog @sprunk is there any prioritization of which issues/bugs (or features) are the most pressing?
What tasks are new contributors recommended to tackle?
Bug and Minor Bug seem like good places to start. The first step of many will be to try to reproduce the bug, as bugs that remain open tend to be rumors of bugs. Task and Backend tend to be a bit more far-reaching. Feature will have more exciting things. If there is some confusion about which way the feature should go, or whether there is a bug, then it is worth commenting for clarification.
I don't think anything is pressing enough to warrant specific attention, it's probably better for motivation if people can work on whatever they feel like. I had the idea to add "skills involved: X" (such as "modelling" or "editing text file and looking at results") so that people could find stuff they are actually able to help with (since "bug" or "feature" can pretty much be anything)