Ways to help

[sezanzeb]

Helping Users

• Answer questions in https://github.com/sezanzeb/input-remapper/discussions
• Watching the repo for new Discussions and Issues ("Watch" button on the top right), and answer them if a user needs help with using the tool
• Translating https://github.com/sezanzeb/input-remapper/blob/main/readme/development.md#translations
• Providing useful examples for https://github.com/sezanzeb/input-remapper/blob/beta/readme/examples.md, if you have one that adds new value over the existing ones

Programming

just like with any open source project out there, contributions are very welcome.

I will gladly discuss any pull request and point to the appropriate places in the code where modifications might be needed.

You really only have to know python, I didn't know anything about python-evdev when I started with input-remapper. Just make sure to write unittests and use pylint and black.

Some information is here: https://github.com/sezanzeb/key-mapper/blob/main/readme/development.md

I won't be developing a lot of new stuff after the 2.0.0 release myself, because I want to focus on other things in the future. I'll still help with testing and merging PRs though when needed.

Easy

• There are issues labeled with "good first issue", you could try working on one of them
• Profiling performance to figure out optimizations
• Cleaning up code. Look at pylint and mypy (see readme/development.md) output and fix issues listed there

Possibly complicated

Those may require knowledge about the architecture. see readme/development.md

• Issues that are labeled with "help wanted"
• There are lots of issues labeled with "feature request". Some of them might be outdated
• port input-remapper-gtk to qt Port GUI to qt #526
• Help wanted from people who know X/Gnome/Wayland/KDE internals #147