Is this library maintained?

[debris]

Latest commit to master was almost 2 years ago, and latest release was over 4 years ago. Is anyone looking after this library? If not, can push access be granted to some volunteers?

[jonathancross]

Sadly, looks like the answer is "no". @signal11 isn't doing much on GitHub, 128 open issues, 49 PRs and no commits since 2016.

[Youw]

If we don't hear from author within reasonable time - it could mean, that this repo is abandoned.
And it is not good, since there is more and more forks and no true, well maintained library.

On the other hand, there is a comment from author on 15 Nov 2017. At least he's still here.

[ulao]

I find this one to work best. I really wish the author would still check in from time to time.

[todbot]

This library is sort of a thankless task. I wouldn't mind if more active collaborators were present. I notice this library has a lot of forks with changes. Perhaps some of those people could help out?

[ulao]

I asked single11 to come back and he did for a few question. So I'd expect he may come back yet again. Though I agree we just need more activity. This is why I deiced to answer am many questions as I could. I didn't write any of this code but I sure have used it for a long while in a straight run. IMO it is one of the best for c#.

[jdk]

Yes, this library is still active. todbot is right.

I've connected with Alan and will be doing my best to join in and help him where I can as another contributor.

There are a lot of branches. One thing to note is that many of them added fixes for their specific situation without doing due diligence for every scenario, kernel, hardware version. But I hope to make this less of an issue as time goes on.

[mickeyl]

@jdk Great, thanks for this commitment. It would be a shame to see this library unmaintained, since there are hardly any other cross-platform alternatives.

[Be-ing]

@signal11, maybe you could give @jdk write access to this repository?

[jdswensen]

If write access was given to someone (@jdk?) and a plan was put in place to begin resolving issues, I would be interested in helping. I need a cross platform HID (mac/win) layer for a work project, so I'll probably be forking this to fix any issues I encounter during that process. I would like to submit contributions/fixes, but it doesn't look like PRs have been merged or rejected in a while. If I'm gonna go through the pain of fixing stuff, I would rather share it on this repo rather than having it live forever on my own fork.

I'd also be willing to perform reviews of the existing PRs and to help manage merging known fixes (or rejecting erroneous ones).

[jdk]

@jdswensen unfortunately, I haven't heard from Alan in a while. = (

[mcuee]

@jdk Let me try to contact Alan as well. HIDAPI is a great library and we at libusb project recommends HIDAPI over libusb for HID device.

Ref: https://github.com/libusb/libusb/wiki/FAQ#Does_libusb_support_USB_HID_devices

[jdswensen]

@mcuee,
If you can't get a hold of Alan, would it be possible for libusb to host a fork? I think the biggest issue for maintaining the library is to have a rally point for discussion and development. If someone can't get access to this one, the community will need something else. libusb seems like a natural choice given that the project already has an established reputation and are actively recommending libusb users to consider using hidapi.

[mcuee]

@jdswensen
I do not see a problem using libusb mailing list for discussions related to HIDAPI. In fact, there were quite some HIDAPI related discussions there.

However, I am not so sure about hosting a fork under libusb. I will wait for Alan's response and then check with other libusb admins.