State of Maintenance

[sezanzeb]

You may have noticed that issues are piling up.

I believe most of them concern

• installation
• limitations of input-remapper/evdev
• figuring out how to do things

Thanks to the pretty high test coverage, I think the tool is rather stable luckily (Thinking back, I wish I applied the DI pattern everywhere, would have made writing tests easier)

I have moved on to other hobbies though that are a bit less complicated quite some time ago (music and cycling among others), and I think @jonasBoss has also been doing different things than keeping an eye on input-remapper for quite some time.

I am still looking at pull-requests, but don't expect valuable input from me in all other cases. Thanks to this being open-source, anyone is invited to participate in keeping this project alive.

Thanks for your support. I hope this post makes me feel better for turning my back on you.

[sezanzeb]

(I think we should probably remove the donation link from the front page since we aren't really involved anymore, @jonasBoss?)

[jonasBoss]

Well, given that I only read this now ...
I have been busy with university and working on my master thesis. I will try to be more active helping with issues but I don't have time to contribute much.

---

I think we should probably remove the donation link from the front page since we aren't really involved anymore, @jonasBoss?

I agree

[ironhak]

Is there any active fork of this or valid alternatives?

[sezanzeb]

Is there any active fork

Since I'm still willing to review PRs there is no need for a fork.

As for alternatives, https://github.com/snyball/Hawck comes to mind, but being an evdev based solution as well as far as I know, it suffers from the same limitations.

Development effort should be focused on improving the situation in linux in general: allowing multiple mapping tools to do their thing on top of each other, and allowing injecting any character (instead of any keycode). See kermitfrog/inputmangler#2 and kermitfrog/inputmangler#5