Wrap in a Transitive capability (web + remote)?

[chfritz]

Hi @sutharsan-311 , I found this project on LinkedIn and I think it's pretty cool. Have you thought about making it available as a web UI that is also usable remotely? That way people can (re)configure deployed robots as well. If you are interested in that I would like to collaborate in turning nav2_config into a Transitive capability to make it more accessible to others.

If you haven't heard about Transitive, it's like Android for robot full-stack software: an open-source platform that makes it easy to develop, deploy, and operate such software. Like with Android, such "capabilities" can be open-source, free, or paid (your choice). You can learn more about it here:

• https://transitiverobotics.com/docs/learn/intro/
• https://transitiverobotics.com/docs/develop/introduction/

[sutharsan-311]

Thanks for reaching out, the remote access use case makes sense, someone filed issue #1 yesterday running into exactly that problem on a remote Jazzy machine.
I haven't looked at Transitive before. A few questions before I can say whether it's a good fit: how much of the existing PyQt6 code could be reused, or would this be essentially a rewrite targeting a web frontend? And is Transitive's platform open source end to end or does deployment depend on their hosted infrastructure?
Happy to explore it, just want to understand the scope first.

[chfritz]

how much of the existing PyQt6 code could be reused, or would this be essentially a rewrite targeting a web frontend?

I don't know much about QT but I assume it would be a rewrite -- although probably something AI could do easily to a first degree.

And is Transitive's platform open source end to end or does deployment depend on their hosted infrastructure?

It's entirely open-source (Apache-2.0) and people can self-deploy it on their own infrastructure if they don't want to use the hosted solution. Similarly for the capability you write you can choose to publishing it on our "capability store", to make it easy for Transitive users to install it (even if they self-host), or just on Github (think "build from source").

[sutharsan-311]

Both answers are reassuring, Apache 2.0 and self-hostable is exactly what i would want.
The rewrite scope tracks. Honestly the PyQt6 parts are the least interesting bit of the codebase anyway, everything that actually matters (param services, lifecycle through lifecycle_manager, post-set costmap clears, node discovery) lives in the ROS2 backend and stays untouched.
I'm genuinely interested. I'm in the middle of fixing bugs from the first users right now (issue #1 came in yesterday from a Turtlebot4 on Jazzy). Can we pick this up in a week or two once the desktop version is stable?

[chfritz]

Sounds good!