Todo

• GitHub wiki
• Translations
• ...

Reading issues in ranked/structured/motivating ways:

sorted like this, the bugs on top are more important (and/or half-solved)

so we can work on the top bugs, top plans & wishes as linked in the readme.md ToDo:

(Then bugs, then plans/org/structure then features/wishes )

- "tidy" could be first, besides it is last in the ToDo list requiring permission and assumming new contributors reading it, while repeat-contributors tidy already.

---

(you might also want to suggest edits of our Readme, to get the gist easier.)