ROS PMC Minutes for March 10, 2026

ROS ROS PMC
1

The ROS PMC meeting for this week was on Tuesday, March 10, 2026.

ROS PMC Business

  • No formal business.

Regular Business

Buildfarm update

Waffle note-taker

Waffle is a weekly meeting where maintainers triage incoming issues and pull requests that haven’t been otherwise acted upon. One person per week is assigned to be the “waffle note-taker” to both take notes in the meeting to keep the meeting as efficient as possible.

Rosdistro assignments

Rosdistro is a weekly assignment to monitor incoming issues and pull requests in GitHub - ros/rosdistro. Two people per week are assigned to be the rosdistro maintainers.

  • Mar 03 - Mar 10 - [@emersonknapp] + [@andrew_symington]
  • Mar 10 - Mar 17 - [@christophebedard] + [@cottsay]
  • Outgoing rosdistro
    • Discussion on nanobind PR. [@emersonknapp] provided analysis on shadowing rules. The PMC reached a consensus to add stricter language to the contributing guide against shadowing system dependencies. In the specific case of nanobind, the Debian package is unmaintained/wrong, so the PMC decided to remove the Debian key and merge as a pip key.

Release Management

Working Groups

  • Client Library Working Group ([@alsora])
    • Discussed AsyncIO node implementation for Python (parallel implementation of executor/node concepts).
  • Accelerated Memory Transport Working Group ([@ahcorde])
    • First PR is open! PMC members are encouraged to prioritize reviews for Lyrical features.
  • ROSGraph Working Group ([@emersonknapp])
    • Discussion on high-level design for a declarative node framework.
    • Plan to transfer NoDL repositories to the ROS Tooling Working Group.
  • Lyrical Release Working Group ([@sloretz])
    • Discussed release timeline (Kilted sync 1 day earlier, adding Rolling migration date).
    • Call for help on Qt6 support, Ubuntu Resolute issues, and Windows 11 test_launch_ros hangs.

Agenda

  • [RECURRING] GSoC 2026
    • Mentor projects due 2026-03-16. Please add proposals to the Project Wiki ASAP.
  • Interface Folder Policy ([@MiguelCompany])
    • Discussion on whether msg, srv, action, and idl folders are strictly required or just convention. [@andrew_symington] argued for strict convention to avoid name collisions. [@mjcarroll] to investigate current enforcement/assumptions.
  • RMW Zenoh Test Failures ([@Jenoch])
    • Investigation into timeout failures on Windows, likely due to lack of isolation. [@mjcarroll] will perform an rcutils release to unblock related PRs.
  • Rust Versioning Follow-up ([@Jenoch])
    • Continued discussion on supporting newer Rust versions on older distributions like Jazzy/Humble. [@cottsay] suggested a ROS shim package to manage the environment and target the correct compiler version on Ubuntu without requiring internet access at build time.

Action Items

  • @everyone: Add GSoC project proposals to the wiki by March 16.
  • @everyone: Triage issues for “Good First Issue” tags for GSoC.
  • @mjcarroll: Investigate ros2topic pytest failure and CycloneDDS uninitialized peer warning.
  • @mjcarroll: Review Qt6 support PRs from @ahcorde.
  • @mjcarroll: Dig into ROS 2 interface folder naming conventions and enforcement.
  • @mjcarroll: Perform rcutils release to unblock RCL test isolation PR.
  • @ahcorde: Ping vendors and PMC members for reviews on Accelerated Memory Transport PRs.
  • @ahcorde: Follow up with @nvcyc on CI access/training.
  • @Jenoch: Investigate RMW Zenoh timeout failures in launch_testing.
  • @Jenoch + @cottsay: Brainstorm design for a ROS shim package to manage Rust/Cargo versioning on Ubuntu.
ROS News for the Week of March 16th, 2026