There’s one thing that’s bothering me about this “project”. How is it supposed to work with the upstream? Is this supposed to be a rivaling fork? How am I suppo

There’s one thing that’s bothering me about this “project”. How is it supposed to work with the upstream? Is this supposed to be a rivaling fork? How am I supposed to have it on my system? Also, it rubs me the wrong way that the blog author is seeking a person to do all the dirty work — even for compensation — and then what? Have all the credit? Basically, act as a glorified Forward button? If I felt up to the task enough, I’d slap a sponsorship button onto my github on my own. And here’s the difference: prior to asking for the money, I’d have something to show to prove I’m not a phony. The upstream is not without its problem as well. Right now it’s being maintained by Peter Hutterer from Red Hat, and judging by his LinkedIn, it’s pretty much his job description. Recently he did a talk about how overloaded he is with libinput[1], and how someone volunteering to comb through pull requests and issues would easily become his “number two”. Which also is striking me as odd. libinput, given its importance for Linux ecosystem as such in general, and Red Hat ecosystem in particular (especially since they bet on Wayland as the future, and there libinput is the only choice), is important enough that Red Hat better make sure it’s well maintained. It’s Red Hat/IBM, really, who should be interested in making sure the bus factor of libinput is > 1. Thus the problem should be raised within Red Hat’s management, and they should _hire_ additional people for fair buck to help. Otherwise it looks as if someone who’s paid for X input stack maintenance is seeking free labor to help him. If I asked someone to help me do my paid job for free, open source or not, I don’t think it would even be ethical. [1] http://who-t.blogspot.com/2019/10/libinputs-bus-factor-is-1.html http://who-t.blogspot.com/2019/10/libinputs-bus-factor-is-1....