Community Meeting #51 - March 16th, 2026 @ 3pm UTC

[robwoolley]

Meeting Details

• Date/Time
  Monday, March 2nd, 2026 @ 3pm UTC, (4pm CET / 11am EDT / 8am PDT)
• Google Meet
  Video call link: https://meet.google.com/bxp-triq-yvr
  Dial-in numbers: https://meet.google.com/tel/fom-qmmu-nnw?pin=8216926365973

Attendees

• Name (Organization) - GitHub username
• Rob Woolley (Wind River) - @robwoolley

Agenda

Announcements

• Kirkstone will go end-of-life in April 2026
• Note: that the time has changed to account for daylight savings time and to allow our friends from California to attend. We are in the time between North America and Europe changing the clocks.
• AGL participating in Google Summer of Code again this year and looking for more projects involving ROS

Review Actions

Old Business

meta-ros status

• Currently working on building ros2-control and ros2-canopen on rolling to complete PR merges
  • Problem with "non-existant buildpath" in pal_statistics (eg. /opt/ros/rolling/include/pal_statistics_msgs) seemingly caused by ament_cmake_auto being used in pal_statistics. Need to add IMPORT_PREFIX as suffix.
  • Plan to work on Qt6 support after that

GitHub Pull Requests

• Old
  • Vermaete/master rolling 2025 12 04 #1630
    • Can we close this PR?
  • oelint: avoid whitespaces around some variables ros-infrastructure/superflore#318
• New
  • [master]{ros2} ament_cmake: add python configurations for class-target #1670
  • [scarthgap]{ros2} xtl: Update SRCREV for 0.7.7 #1671

GitHub Issues

• python3-flake8-blind-except: two recipes in meta-ros? #1631 (comment)

New Business

Readout from Embedded World 2026

• Robotics demos

Open Discussion

ROSCon 2026

• Possible Yocto demos / collabs?

ROS on Zephyr (micro-ROS? pico-ROS?)

• What are people using or interested in?

PX4 / Ardupilot

• Supported hardware? Supported use cases?

Space Grade Linux / Space ROS

• Looking for folks to try out existing demos and produce new ones

[vermaete]

@robwoolley : could we add this PR of superflore on the list to? ros-infrastructure/superflore#318
With not a lot of effort a lot of those oelint error can be avoided. And without risk because bitbake would give parser errors is it's wrong.