Thats a misunderstanding. You don't need to be a coder to fix bugs. Many debian maintainers are non-coders. At least half of fixing a bug is getting it into a state in which a coder can have a look at it. E.g.: Is it reproducible? How? Fixed in newer versions? In fact a user error/question? Already reported upstream? (Forwarded) The pro's call that bug-triage.

Meet us on IRC: First, you should join IRC channel #debian-qt-kde on irc.debian.org. This is the place where we meet and work on KDE-related packages in Debian. It is a good starting point: you'll be able to work on what you're interested on, discuss your ideas, fix bugs, etc

I think it's very important to first join the place where they meet and work, get to know them etc. That's where you'll politely ask for help next time if problem arises even while trying to fix non-coding bugs. And that's where you'll find out if there are any other non-coding stuff you can help with.