ROS PMC Minutes for June 2, 2026

ROS ROS PMC
,
1

The ROS PMC meeting for this week was on Tuesday. The notes from the meeting are available at ROS PMC weekly meeting agenda

ROS PMC Business

  • Reminder: Funding proposals are due to the Technical Governance Committee (TGC) at the end of the month (June 30).

Regular Business

Buildfarm update

The buildfarm update is a weekly check-in on the status of the ROS 2 buildfarm. We track new issues and regressions to ensure the stability of the project.

  • :new_button: Issues
    • No new issues!
  • :warning: Priorities
    • PTAL Buildfarm Issues Triage Sheet (16 issues open in total).
    • Build regression: test_rosidl_buffer failing in CycloneDDS Resolute build because it cannot find rosidl_typesupport_fastrtps_cppConfig (ros2/rosidl#964).
      • Discussion around ensuring Fast CDR is built and renaming rosidl_typesupport_fastrtps to rosidl_typesupport_fastcdr in M-Turtle.
    • Build regression: test_launch_ros causing nightly_win failures via a Windows access violation (ros2/launch_ros#539).
      • @mjcarroll is investigating Windows executor/workspace issues.
    • Nightly builds are experiencing timeouts and slow execution, partially attributed to recent Ubuntu updates and kernel security patches.

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: This repo maintains a lists of repositories for each ROS distribution. Two people per week are assigned to be the rosdistro maintainers.

  • Jun 2 - Jun 9 - @tfoote + @wjwwood
  • Outgoing rosdistro
    • It was discussed that we should potentially bring in Rob Woolley (@robwoolley) as an official reviewer for OpenEmbedded rules.
    • Discussion on Nix rules: Nix rules are hard to validate programmatically, we should find someone that would be willing to be a community reviewer of Nix rules.

Release Management

Release Management tracks the status of upcoming releases, patches, and syncs across the active ROS distributions.

Working Group Updates

  • Client Library Working Group (@alsora)
    • Last Meeting: Friday, May 29, 2026
    • Next meeting: Friday, June 12, 2026
  • Accelerated Memory Transport Working Group (@ahcorde)
    • Last Meeting: Wednesday, May 20, 2026
    • Next Meeting: Wednesday, Jun 3, 2026
    • Switching to lower meeting cadence after the first Lyrical Patch release
  • ROSGraph Working Group (@emersonknapp)
    • Last Meeting: Tuesday, May 26, 2026
    • Next Meeting: Tuesday, June 9, 2026
  • Lyrical Release Working Group (@sloretz)
    • Retrospective scheduled for Jun 8, 2026, at 9:00 AM PDT (immediately following Infrastructure PMC).

Agenda

  • [@sloretz] ROS Lyrical Retrospective
  • [@mjcarroll] PSA: Removing Python2 rosdep keys
    • Progressing through five PRs (rosdistro#51715). The first four are pure removals.
  • [@mjcarroll] Google Summer of Code (GSoC) Updates
    • GSoC student Ammaar shared a performance monitoring dashboard mockup.
    • Discussion on hosting: Grafana/Prometheus was suggested, but @cottsay raised concerns over infrastructure maintenance burden and suggested looking into static JSON with client-side rendering.
  • [@mjcarroll] Rolling Distribution Sync Policy
    • Proposal to automate testing-to-main syncs for Rolling (eliminating manual syncs to main).
    • Stricter automated thresholds (like ros-desktop-full) could be adjusted dynamically before releases.
    • Next Action: Write a Discourse proposal to gather community feedback before PMC voting.
  • [@mjcarroll] Funding Proposals (due June 30)
    • [@christophebedard] CI strategy overhaul: Focus on speeding up CI by changing how/what is tested, documenting CI onboarding, and automating builds via contracted help.
    • [@mjcarroll] Canonical end-to-end demo: An integrated demo of Gazebo, ROS, and ros2_control in a neat package. Joint-PMC proposals (e.g. Gazebo + ROS) have higher approval odds.
    • [@cottsay] Hardware certification & Hardware-in-the-loop (HIL) testing: Pay a contractor to establish a certification program with public dashboard reporting and SBOM/HBOM formats.
    • [@cottsay] Commodity hardware drivers: Fund development of basic drivers (IMUs, motor controllers) to improve ROS 2 driver coverage and onboarding compared to ROS 1.

Action Items

  • @everyone
    • Submit funding proposals to the TGC by June 30.
    • Provide feedback for the Lyrical Retrospective using the form.
    • Working Group Leaders: Plan roadmaps and goals for the upcoming M-Turtle cycle.
  • @mjcarroll
    • Write a proposal on the Rolling repository sync policy for Discourse to gather community input.
    • Start a Zulip thread in the ROS General channel to coordinate funding proposals.
  • @sloretz
    • Host and organize the ROS Lyrical Retrospective meeting on Monday, Jun 8