Todo

• GitHub wiki
• Translations
• ...

Reading issues in ranked/structured/motivating ways:

We can work on the top bugs, plans & wishes ordered by popularity and inpute as linked in our readme.md ToDo:

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

For example the bug (on top are most important ones and/or half-solved)

- "tidy" could be first in the ToDo-List, 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.)