ROS 2

The repository is a map of the software

The ros2/ros2 repository contains a ros2.repos manifest naming separate repositories and their selected versions. Preserving this archive preserves that map; it does not preserve every component's source, binary or dependency. A reproducible source build needs the referenced repositories as well. For users who want to begin with the framework, the documentation offers prebuilt packages rather than requiring a source build. [S011] [S012]

The Humble deb instructions target Ubuntu 22.04 on amd64 or arm64. The desktop installation includes RViz, demos and tutorials; ros-base provides communication libraries, messages and command-line tools without GUI tools. Follow the complete upstream locale, repository and system-update prerequisites before installing either. The guide specifically warns about updating systemd/udev-related packages on early Ubuntu 22.04 installations. These steps were inspected, not executed here. [S006]

Use the demo to check communication, then add the robot

For the documented desktop route, source the Humble setup script in each terminal, using the extension for the current shell. The guide then runs demo_nodes_cpp talker in one terminal and demo_nodes_py listener in the other through ros2 run. Receiving the published messages checks that this example can communicate through the C++ and Python APIs. It does not establish that a motor driver, navigation system or physical robot is correctly configured. [S006]

Nodes participate in a graph and can run in the same process, in separate processes or on different machines. They publish and subscribe to topics, provide services, accept actions and expose runtime parameters. Actions add feedback and cancellation or preemption for longer-running work, such as requesting travel to a waypoint; a short request can use a service instead. Choosing those interfaces is part of designing the application, rather than something the framework decides for the robot. [S007] [S008]

The Humble documentation names Fast DDS as the default middleware and describes alternatives through the RMW layer. Keep the selected middleware and package versions with the experiment's configuration. Before adding a driver or algorithm, use its package documentation and ROS Index entry to check supported distributions and dependencies. ROS ecosystem membership alone does not establish that two packages work together in the selected release. [S005] [S006]

Licensing follows the packages

The ROS 2 developer guide requires package license files, typically Apache-2.0, while allowing existing permissive licenses such as RViz's three-clause BSD. That is a package policy, not one license covering an entire robot stack. Inspect the actual selected components and dependencies before redistributing them. The separately preserved documentation repository has a CC-BY-4.0 license. [S009] [S010]

This profile establishes a documented starting route and the scope of the saved release manifest. No ROS installation, network test, robot-driver integration or control-system validation was performed.