ros2-architect

To structure a ROS2 workspace, define standard package layouts, use ament_cmake or ament_python for build tooling, and establish cross-language node conventions. This ensures predictable CI and deployment across Jazzy, Kilted, and Lyrical distributions.

Managing ROS2 deployments across distributions like Jazzy and Kilted requires standardized workspace architectures. Using Pixi with RoboStack provides cross-platform development consistency and predictable deployment patterns for both C++ and Python packages.

Yes, the ROS2 architecture standard fully supports both rclcpp and rclpy. It provides clear node design patterns for C++ and Python, including lifecycle management, QoS strategies, services, actions, and parameterization conventions.

To set up QoS and lifecycle management, apply explicit QoS profiles for reliability and durability, and implement managed node states. The architecture standard enforces these patterns for both rclcpp and rclpy to ensure robust node communication.

Yes, Pixi can be used to build and deploy ROS2 workspaces. The architecture standard aligns workspace layout with Pixi and RoboStack, enabling cross-platform development and consistent deployment across Jazzy, Kilted, and Lyrical distributions.

Standardizing ROS2 launch configurations and testing practices ensures smooth CI integration and reliable deployment. Consistent patterns for services, actions, and parameters prevent runtime errors and simplify workspace audits across multi-package projects.