# The Rust library uavcan.rs is looking for a new maintainer

**URL:** <https://forum.opencyphal.org/t/the-rust-library-uavcan-rs-is-looking-for-a-new-maintainer/687>\
**Category:** Applications & Usage\
**Created:** [November 17, 2019, 8:11pm UTC](https://forum.opencyphal.org/t/the-rust-library-uavcan-rs-is-looking-for-a-new-maintainer/687 "2019-11-17T20:11:57Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![pavel.kirienko](https://forum.opencyphal.org/user_avatar/forum.opencyphal.org/pavel.kirienko/32/9_2.png) [@pavel.kirienko](https://forum.opencyphal.org/u/pavel.kirienko)\
**Post date:** [June 5, 2020, 7:16pm UTC](https://forum.opencyphal.org/t/the-rust-library-uavcan-rs-is-looking-for-a-new-maintainer/687/3 "2020-06-05T19:16:53Z")

</div>

Great ☀

> What is the current state

It’s been abandoned for the last ~1.5 years. At this point, I suspect it could be easier to restart from scratch and possibly make the API closer in spirit to PyUAVCAN.

> what are the gotchas, what is currently missing in the implementation

It is rather early-stage, I would say. It’s been envisioned to implement the support for different transport protocols which would probably require revamping a lot of the existing code unless it is redesigned from scratch. I mentioned PyUAVCAN as a sensible reference because it was designed specifically to support different transports.

> who else currently has a stake in the matter

Nobody. To the best of my knowledge, this implementation is neither actively used nor developed by anyone.

You are welcome to join our [dev call](https://forum.opencyphal.org/t/weekly-dev-call/173) if you want to discuss this in real-time.

---

_[View the full topic](https://forum.opencyphal.org/t/the-rust-library-uavcan-rs-is-looking-for-a-new-maintainer/687)._
