Maintenance status of the crate?

[kanpov]

It seems like PRs aren't getting reviewed properly, with essential maintenance tasks like #76 also being ignored. This prompts the question whether any further maintenance is even expected of this library?

[kanpov]

If true, this is a major concern due to there being pretty much no Rust alternative for this (unlike Go with a much more active and mature networking ecosystem due to CNI and co.) in spite of the drawbacks (tokio dependency in netlink-proto, async-io being outdated for zero good reason).

[kanpov]

@cathay4t Any input?

[ssrlive]

Who is willing to take responsibility for maintaining this crate?
If there's really no one around, I'd be willing to do some basic work.
I can merge PRs and update dependencies. If @cathay4t thinks I'm right, please give me co-contributor and crates.io publisher permissions.

[mrcrgl]

I can also take a co-maintainer role in this crate if wanted. I can review PRs, fix bugs and extend it. @cathay4t

[cathay4t]

You don't need any permission to review a patch. I prefer promote co-maintaner who has enough patches merged.

From my point of view, this crate alone is higher level wrapper, many features(use cases) can be done through message_mut() without property wrapping in these handlers.

More efforts should be place on netlink-packet-route and try to make it reach 1.0 API stable. I could use a lot help on convert integer to enum there.

I will be diligent to put at least 1 hours per week on rust-netlink crates.