Seems like a patch others (ie:me) would like to see

Shouldn’t that be something that’s pulled into upstream? And if they refuse, fork libinput?

Since the libinput upstream is one guy and nobody stepped up to help him, good luck with long-term maintenance of your fork.

It's this kind of defeatist, responsibility-shifting attitude that holds Linux back from becoming a widely used desktop platform. What's the worst case with a fork, it stagnates and remains mostly identical to the upstream?

Is it defeatist to point out, that there is no need to fork, just communicate with the upstream?

Especially if you do not have resources for maintenance. If you had them, and spent some time and effort in the problem domain, maybe, just maybe, you could come to the same conclusions and the results as the original you forked from.

Like I said, it is something that should be pull requested to the upstream, and if that fails, then fork. The fork is a secondary path to cooperation.

If the conclusions are that the platform cannot support cursor acceleration the proper way (i.e. the way all commercial OSes do), the premise of the library is flawed. If not, then it must be the whole OS that's flawed, because that needs to be possible on a desktop system. Linux's cursor acceleration sucks, there is no excuse for the whole UI layer of the ecosystem being as bad as it is.

I think "there is only one person working full-time on maintaining Linux input libraries and he's overworked" is probably a decent excuse. I don't know what you plan to do, but I would advise against forking unless you can hire a team to accumulate testing hardware and work on this for multiple years. What we have seen too often is these forks just fizzle and get forgotten, especially if they are only focused on getting one feature to work on one very specific device.

I’ve heard of tons of these patches people write for libinput, yet they are never in master. There’s nothing in the libinput README or FAQ about how they’re looking for help, and there are quite a few different authors. How is anyone supposed to know help is needed?

This post was going around a while ago, I don't think anything has really changed for the better since then: https://who-t.blogspot.com/2019/10/libinputs-bus-factor-is-1...

well i put it out there, but it was (apparently) very personal. I use zowie mice at 800 dpi and setting gui settings to 0.1 sensitivity (or 1 etc,c whatever is lowest) would result in several desktops worth of movement per mousepad (22 inches), really bad over all. i just wanted a single left-right corresponding with monitor edges which was never a problem across any os until recently which oddly started treating low dpi at 1000 hz really weird

i still got the patches somewhere and will post them soon. it basically let you set mouse speed scaling on a larger scale