[Documentation] [TitleIndex] [WordIndex] 

Planet ROS

Planet ROS - http://planet.ros.org

Planet ROS - http://planet.ros.org[WWW] http://planet.ros.org

ROS Discourse General: ROS News for the Week of April 7th, 2025

ROS News for the Week of April 7th, 2025

ROSConUK2025

Announcing the First Ever ROSCon UK! :united_kingdom:


9q76m6

It is official, ROS Noetic will go end-of-life on May 31, 2025.. I’ve put together some guidance on how to migrate to ROS 2.


OpenCV-SID-1x1-Poster@1x

Our friends at OpenCV are holding their first ever Conference! The event is schedule for May 12th, 2025 in San Jose, California.


x1
camera_angle

Lots of interesting URDF news this week. Check out this cool automatic URDF generation paper @arjo129 found.There is also this handy tool to generate differential drive robots for Gazebo.

calibrate

This week I came across this one dependency, pip-installable, easy to use camera calibration utility. This should make robot camera calibration so much easier!

Events

News

ROS

Got a minute? :alarm_clock:

A friendly fuzzer just dumped a bunch of issues in RViz and Geometry2. We would love to get these fixed before the Kilted feature freeze on 2025-04-14. If you have some time why not send us a pull request?

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/ros-news-for-the-week-of-april-7th-2025/43181

ROS Discourse General: Generic Controller for Omnidirectional Robots using Omni Wheels

Hello everyone! I have made a ros2_controller for omnidirectional robots that are using 3 or more omni wheels.
I have made a PR, submitting this controller into the official repository so that it can have a wider reach, but the maintainers haven’t gotten the time yet to review and test the controller.
It would be really nice if someone from the community could go ahead and review/test the controller.
You can find the kinematics used by the controller in the official docs.

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/generic-controller-for-omnidirectional-robots-using-omni-wheels/43172

ROS Discourse General: ROS Noetic End-of-Life: May 31, 2025

Hello ROS Noetic users and maintainers!

This week the ROS PMC formally voted to set the Noetic end-of-life (EOL) date to May 31, 2025. This is the same day Ubuntu Focal reaches end of standard support.

I’m a ROS Noetic user, what do I need to know?

You need to know that it is time to upgrade! 80% of the ROS community has already made the switch.

We put together a single page of guidance for current ROS Noetic users who need to upgrade to ROS 2: ROS: Upcoming ROS 1 End of Life

I’m a ROS Noetic maintainer

How long do I have to make releases?

If you maintain a ROS Noetic repository and you haven’t made a release in a while, then you should make a release now.

There are only a few syncs left. The last two syncs will follow this schedule:

[1] The sync dates may be delayed if releases cause regressions that need to be resolved or rolled back.

What should maintainers do to prepare for EOL?

First, if you have unreleased changes, then make a release now.

There won’t be an opportunity to fix regressions in binary packages once ROS Noetic goes EOL, so consider reducing the risk of regressions when reviewing PRs by:

Some users will build ROS Noetic from source, for example, to use the ros1_bridge. Consider merging PRs that make your package build on newer Ubuntu versions.

If your repository only supports ROS 1, and you are not going to maintain it after ROS Noetic goes EOL, then make that clear to your users on May 31, 2025 by:

If your repository supports ROS 1 and ROS 2, then make sure the default branch supports ROS 2, preferably ROS Rolling.

8 posts - 4 participants

Read full topic

[WWW] https://discourse.ros.org/t/ros-noetic-end-of-life-may-31-2025/43160

ROS Discourse General: Rosdep search

Greetings fellow roboticists,

if you’re a commendable package creator and always try to specify all your dependencies, you might know the struggle of trying to guess the right dependency key.
Maybe you’re lucky and guess it; otherwise, you have to take the cumbersome route of visiting the rosdep repo and checking the base.yaml for the key for your dependency.

This should really be easier, shouldn’t it?
Well, now it can be!
I’ve added a search command to rosdep in my fork and opened a PR #997.

This command enables you to simply search your rosdep database (which can also include additional sources to the official ones) for the keys matching your search with 1 allowed error (missing, wrong, or extra letter).
It checks both for keys and packages, so you can search for the package name in your Linux distros package manager.

Examples:

$ rosdep search libpcl-dev
Closest keys:
  libfcl-dev

Closest packages:
  libpcl-all-dev: libpcl-dev [debian]
  libpcl-all-dev: libpcl-dev [ubuntu]
  acl: libacl-devel [fedora]
  acl: libacl-devel [rhel]


$ rosdep search pinoccio
Closest keys:
  kinematics_interface_pinocchio
  pinocchio

I hope this will be useful for you and this post helps get the PR some attention so it can be finalized and merged in a timely fashion :innocent:

If it wasn’t useful, here’s a picture to make up for your time:

image

5 posts - 4 participants

Read full topic

[WWW] https://discourse.ros.org/t/rosdep-search/43148

ROS Discourse General: New Packages for Noetic 2025-04-08

We’re happy to announce 2 new packages and 5 updates are now available in ROS Noetic. This sync was tagged as noetic/2025-04-08.

Package Updates for noetic

Added Packages [2]:

Updated Packages [5]:

Removed Packages [0]:

Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/new-packages-for-noetic-2025-04-08/43121

ROS Discourse General: CppCon 2025 Robotics and AI Track Call for Submissions!

The C++ programming community is excited to announce the Robotics and AI Track for the upcoming CppCon 2025, taking place on-site at the Gaylord Rockies in Aurora, Colorado September 13th-19th. We invite robotics practitioners from industry, academia, and the hobbyist domain to share their insights, experiences, and knowledge about using C++ in a robotics context.

Deadline for Submission is May 11th!

image

The track has a focus on C++ used in a Robotics or AI context so that we can share best practices and strengthen our community. It differs from events such as ROSCon or ICRA as it has an emphasis on code on slides and talks are typically 1 hour long.

Last year’s presentations included:

Below is a playlist of presentations from last year’s track as well as 2023, which should give you an idea of the subject matter and C++ emphasis the track welcomes.

CppCon 2024 Robotics Track Playlist

CppCon 2023 Robotics Track Playlist

For more information (and links to submit your talk proposal) see this longer post here:

Deadline for Submission is May 11th!

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/cppcon-2025-robotics-and-ai-track-call-for-submissions/43110

ROS Discourse General: New packages and patch release 4 for Jazzy Jalisco 2025-04-07

We’re happy to announce 24 new packages and 473 updates are now available on Ubuntu Noble on amd64 for Jazzy Jalisco.

This sync was tagged as jazzy/2025-04-07 .

:jazzy: :jazzy: :jazzy:

Package Updates for jazzy

Added Packages [24]:

Updated Packages [473]:

Removed Packages [4]:

Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:

Enjoy! :jazzy:

4 posts - 4 participants

Read full topic

[WWW] https://discourse.ros.org/t/new-packages-and-patch-release-4-for-jazzy-jalisco-2025-04-07/43100

ROS Discourse General: Upcoming ROS 2 Feature Freeze for Kilted Kaiju on April 14th

We’ve just entered the RMW Feature Freeze period for ROS 2 Kilted Kaiju, and this means that we’re only one week away from the same milestone for all ROS 2 core package in Rolling (soon to be Kilted). At that time, all ros_core packages will be feature and API frozen in Rolling Ridley until we branch Kilted from Rolling on 2025-04-21T00:00:00Z UTC. Feature and API changes can be merged into the Rolling branches once again after the branching is complete.

As always, refer to the Kilted Kaiju Release Timeline for all of the important dates and milestones as we approach World Turtle Day and the release of Kilted Kaiju!

Thanks!

– ROS 2 Team

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/upcoming-ros-2-feature-freeze-for-kilted-kaiju-on-april-14th/43096

ROS Discourse General: BeetleBot Differential Drive Robot Template for GZ sim ROS2

Beetlebot Repo.This repository contains different configurations for the BeetleBot differential drive robot with Gazebo sim to make it easier for beginners to create thier own robot for gazebo sim in sdf or URDF format also make it easier to understand the diffrences between SDF and URDF .

Each branch in this repository represents a unique configuration of the same beetlebot robot in the world it operates in.

  1. SDF-format

In this branch beetlebot robot is writen in SDF format and spawnd inside the main world using spawner cmd in the launch file.

  1. URDF-format

In this branch beetlebot robot is written as URDF and spawned inside the main world using spawner cmd in the launch file.
camera_angle
beetlebot_empty_world
beetlebot_track

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/beetlebot-differential-drive-robot-template-for-gz-sim-ros2/43085

ROS Discourse General: ROS Deliberation Community Group Survey

Following our latest meeting today, I would like to learn a bit more on what you guys expect from the Deliberation Community group.

Please answer this quick (<5 mins) survey:
ROS Deliberation Community Group Survey

Thanks :slight_smile:
Christian

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/ros-deliberation-community-group-survey/43075

ROS Discourse General: Location for ROSCon 2026?

Hi,

given that traditionally the rotation for locations for ROSCon has been Europe → Asia → North America, and after this year it’ll be the turn of North America for 2026, I’d like to ask if the location been decided yet. I imagine so, given that the effort for organizing ROSCon is not to be dismissed (thanks MeetGreen, Vanessa, Geoff, Kat and everyone else involved!)

I’m asking because of recent travel warnings that several countries have issued (European countries, Canada issue advisories for travelers to U.S. : NPR) and cases like the one of a French researcher who was on his way to attend a conference in Houston, but was denied entry to the US because immigration officers had found messages on his phone where he criticized the current US administration (French scientist denied US entry after phone messages critical of Trump found | US news | The Guardian). Or now that the US government only recognizes two genders, possibly denying entry to trans people who have an X on their passport or the gender on their passport does not match the gender assigned at birth (https://edition.cnn.com/2025/04/03/travel/trans-people-travel-advisories-united-states/index.html)

I’m not trying to start a political thread here. As a very wise man once said when he arrived on Coruscant, “I’m not brave enough for politics”, but I’m only asking if these concerns could be taken into account for ROSCon 2026 before a final decision is made and if possible, other locations in North America like Canada or Mexico could be considered.

Or maybe even somewhere in a new region, like Oceania, South America or Africa, that would be really cool.

Looking forward to seeing you all in Singapore! :slightly_smiling_face:

5 posts - 4 participants

Read full topic

[WWW] https://discourse.ros.org/t/location-for-roscon-2026/43073

ROS Discourse General: New to ROS – Learning ROS2 as a Student, Open to Suggestions

Hi everyone!

My name is Jorge Andrés Duque, a Mechatronics Engineering student from Colombia currently diving into ROS2 as part of my university and personal projects. I’ve worked with embedded systems, AI, and VEX Robotics, but ROS is something I’m now truly focused on learning more deeply.

I’m especially interested in applying ROS2 for autonomous robots, and I’ve started experimenting with PID control and basic perception using sensors.

If anyone has suggestions for beginner-friendly ROS2 packages, tutorials, or simulation environments you’ve found useful, I’d love to hear from you!

Thanks and I look forward to learning and contributing in the future!

5 posts - 4 participants

Read full topic

[WWW] https://discourse.ros.org/t/new-to-ros-learning-ros2-as-a-student-open-to-suggestions/43051

ROS Discourse General: Gatorcat: EtherCAT on Zenoh / ROS

I have been developing an open-source EtherCAT maindevice and it might be interesting to ROS folks.

Here is a summary of its capabilities:

Notably missing features (coming soon!):

ROS folks may be using a lot of distributed clocks for motor drives, I have not tested it extensively with motor drives. It is well suited for digital / analog output/input modules right now.

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/gatorcat-ethercat-on-zenoh-ros/43050

ROS Discourse General: Upcoming RMW Feature Freeze for ROS 2 Kilted Kaiju on April 7 2025

Hi all,

On 2025-04-08T06:59:00Z UTC we will freeze all RMW related packages in preparation for the upcoming Kilted Kaiju release on May 23, 2025.

Once this freeze goes into effect, we will no longer accept additional features to RMW packages, which includes rmw_fastrtps, rmw_cyclonedds, rmw_connextdds, rmw_zenoh; as well as their vendor packages, Fast-DDS, Fast-CDR , cyclonedds, iceoryx and zenoh_cpp.

Bug fixes will still be accepted after the freeze date.

You may find more information on the Kilted Kaiju release timeline here: ROS 2 Kilted Kaiju (codename ‘kilted’; May, 2025).

2 posts - 2 participants

Read full topic

[WWW] https://discourse.ros.org/t/upcoming-rmw-feature-freeze-for-ros-2-kilted-kaiju-on-april-7-2025/43020

ROS Discourse General: ROS News for the Week March 31st, 2025

ROS News for the Week March 31st, 2025


OSRF Google Summer of Code

Applications for GSoC 2025, the OSRF’s only paid internship program, are due on 2025-04-08T18:00:00Z UTC. I checked this morning and there are only ~30 legitimate applications. A few of the “less sexy” projects don’t have any applications. All of this is to say, if you take the time to apply you have a really good shot at getting accepted!


ROSConDiversity

ROSCon 2025 Diversity Scholarship applications are due in two weeks, on 2025-04-18T07:00:00Z UTC.


Copy of March25GCM

Join us for on 2025-04-30T07:00:00Z UTC for our next Gazebo Community meeting on RoSE Terrain Generator (RTG): Monocular Depth-Based Synthetic DEM Generation


Screenshot From 2025-04-04 12-29-47

The Robot Report’s 50 most innovative robotics companies were released this week. More than half of them are ROS users, including OSRA members NVIDIA, Clearpath, Roboto, Asensus, and Locus. :tada:


hand_intro_3
Check out this super cool open hardware / open software dexterous hand that runs ROS!. Source code and CAD available here.


GoBlue
Our colleagues over at University of Michigan have released :ocean:OceanSim: A GPU-Accelerated Underwater Robot Perception Simulation Framework. Even better, it has ROS baked right in. Source code available here.


main_teaser

Check out FACTR an open hardware / open software teleop and RL training framework based on ROS. FACTR Hardware - FACTR Teleop - FACTR Training


86e7ac01fc34606483074cf5af9ba191d5362ebc_2_499x500

There’s finally a low-cost micro-ROS/LiDAR/Motor drivers board thats available commercially?. THIS IS HUGE! :tada:

Events

News

ROS & Robotics

Got a Minute? :alarm_clock:

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/ros-news-for-the-week-march-31st-2025/43015

ROS Discourse General: New ROS 2 package for multi-sensor calibration

Hello there!

We are excited to announce the release of a new package for ROS 2 Jazzy (we also have a ROS 1 branch, but please note that it will not be maintained). This package enables much faster and easier extrinsic calibration of camera and LiDAR sensors through a user-friendly GUI application—no coding required!

Currently, the calibration process utilizes a physical target, but the package is designed to be extensible, allowing for other target geometries or even targetless calibration.

We are actively working on adding new calibration modalities (e.g. intrinsic calibration of cameras) and would greatly appreciate your input, ideas, and contributions in the form of pull requests!

For more information, please visit our GitHub repository:

Thank you for your interest, and we look forward to your feedback!

Best regards,

Miguel

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/new-ros-2-package-for-multi-sensor-calibration/43003

ROS Discourse General: Low-cost micro-ROS/LiDAR/Motor drivers board available commercially

Hello,

I have designed, manufactured and made available commercially a low-cost all-in-one board for beginners building DIY robots capable of ROS2/Nav2 mapping, navigation, SLAM and frontier exploration. Everything is open source.

This board has a 2D LiDAR port, 2 channel DC 12/24V motor drivers. Think of this PCB as a miniature robot “motherboard” for building small differential two-wheel educational LiDAR robots. Out-of-the-box firmware, ROS2 packages and starter robot body for easy robot building are provided as well.

brushed_dc_motors_pcb_for_esp32_doit_DevKit_v1_30pin_BDC_30P_front_left

The board accepts an ESP32 development board and runs micro-ROS for Arduino connected over WiFi to a local PC running ROS2 Iron. Here is an example interfacing this board to a LiDAR and two N20 encoder motors.

BDC_30P_usage

Here is a video example of what you can build in action, running glorious Nav2 and frontier exploration.

The board comes with the following:

Extensive troubleshooting instructions and a technical support forum are available as help resources.

I hope this robot board can be useful for the ROS community.

3 posts - 2 participants

Read full topic

[WWW] https://discourse.ros.org/t/low-cost-micro-ros-lidar-motor-drivers-board-available-commercially/42985

ROS Discourse General: Next Client Library WG Meeting: Friday 4th April 8AM PST

Hi,

The next meeting of the Client Library Working Group will be this Friday, 4th April 2025 at 8 AM Pacific Time.

Agenda:

Everyone is welcome to join and bring their own topics for discussion, just add them to the agenda!

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/next-client-library-wg-meeting-friday-4th-april-8am-pst/42969

ROS Discourse General: OSRA TGC meeting minutes for February, 2025

The meeting minutes for the regular meeting of the Technical Governance Committee held on the 27th of February, 2025, were approved in the March meeting and are now available in the official minutes repository. You can find the complete minutes here, as well as a Markdown version below. The Markdown version is experimental so please excuse any formatting problems and errors; the PDF version is the official version.

The next TGC meeting will take place in April, 2025. The minutes of the March meeting should be approved in that meeting and posted publicly shortly thereafter.

TECHNICAL GOVERNANCE COMMITTEE

MEETING MINUTES

27 FEB 2025 / 14:00-15:30 UTC / VIRTUAL VIA ZOOM

ATTENDEES

OSRF:

OSRA Delegates/TGC Reps:

OSRA Observers

AGENDA

Vanessa Yamzon Orsi, TGC Secretary (filling in for the TGC Chair) called the meeting to order at 15:04 on 27 Feb 2025 UTC

Existing Business

  1. Confirmation of minutes of meeting TGC-20250123-Regular
    • Approved by consensus
  2. Project reports
    • Project update: ROS
      • Presented by Michael Carroll, PMC Lead
        • Transition work in progress as Michael took over as interim project lead from Chris Lalancette.
        • Main priority is wrapping up RMW Zenoh as a Tier 1 middleware. Final steps on security implementation, CI and build farm are in progress. Aiming for completion before feature freeze on April 7 for the Kilted release.
        • pixi and Conda migration - for Kilted and Rolling going forward, pixi will be the recommended installation procedure for ROS on Windows. We are seeing community excitement around this, and we are happy to report that the process is much better and we are getting support from the folks at prefix.dev who develop pixi.
        • eProsima is wrapping up the renaming of Fast-RTPS to FastDDS in preparation of landing a new version of FastDDS in Kilted.
        • Tomoya and Sony are working on action introspection to record ROSbag actions and replay them, a valuable feature for users with action-heavy workflows like Nav2.
        • The Client Library Working Group has a couple of contributions such as a multi-threaded executor starvation fix and an rclpy events executor which improves python performance by an order of magnitude.
        • Kilted timeline reminder: Feature freeze on April 7 with events in between including testing and tutorial party before final release on May 23, 2025.
    • Project update: Gazebo
      • Presented by Steve Peters, PMC Member on behalf of the PMC Lead
        • Carlos Aguero (Honu) will serve as interim PMC lead while Addisu Taddese (Intrinsic) is out on personal leave.
        • External contributions: generating 3D meshes from a smartphone and then making a Gazebo world from that, features from Gazebo Classic that were ported by community members such as visualizing frustums for cameras and also using the physics engine to calculate ray intersection.
        • Recent features announced at community meeting: updated automatic inertial calculation feature to auto calculate density from specifying the mass of a link.
        • Conda for Windows support: Gazebo’s Windows and CI machines have been switched to use Conda and pixi instead of vcpg.
        • Roadmap item: continuing prototyping work on using Xeno with Gz transport.
        • Several GSoC projects have been proposed: Migrating from QT 5 to 6, deprecating the Gz launch package which is mostly redundant with ROS 2 launch.
        • The PMC has nominated Saurabh Kamat (github.com/sauk2) as a project committer; he is a great contributor and is now in the mentorship phase under Carlos Aguero.
    • Project update: Open-RMF
      • Presented by Michael Grey, PMC Lead
        • One of the large ongoing efforts is the development of a workflow execution framework, particularly targeting workflow diagrams that can represent multi-agent interactions. The execution framework is finished, now working a serialized format to represent the workflow.
        • Close to having support for buffer elements - elements within the workflow that can store data in flight or which needs to be retained during the lifespan of the workflow.
        • Quality of life improvements to the site editor UI around the scenarios concept, currently an experimental feature.
        • Moved on async capabilities for rclrs
          • Discussion on rcls as the library of choice for Open-RMF implementation.
        • The PMC initiated a biweekly Open-RMF community forum. This is an open-format, no agenda meeting. Community members may ask questions and the PMC representatives will answer.
    • Project update: Infrastructure
      • Presented by Steven! Ragnarok, PMC Lead
        • Primary mission right now is to transition all of our infrastructure hosts from Ubuntu 20.04 to 24.04 before the end of community support for 20.04. Contingency plans in place for support in the case we don’t make the cutoff. The priority is to move the ROS 2 buildfarm by mid-March to prepare for the work on ROS 2 Kilted (Kaiju).
        • We had the first release of ROS build farm python modules in some time. Both the Infra team and community have been instructed to use them directly from the main development branch, but this was done so that other released packages can depend on it.
        • All other resources focused on maintenance.
    • Project update: ROS Controls
      • Presented by Bence Magyar, PMC Lead
        • The PMC has been running a fortnightly meeting with leads and contributors.
        • Working with companies upstreaming specialized or rugged versions of controllers such as the scaled joint trajectory controller that Universal Robot worked on.
        • Working on adding the joint functionality at the framework and not the controller level.
        • Recurring discussions are in place over introducing a real time-friendly high frequency logging or introspection tool to support running in the kHz range. Opted to adopt path statistics.
        • Several depreciations are marked for removal for the ROS 2 L-release.
        • Call for contribution to the PR regarding the joint limiting topic currently on Discourse.
  3. Existing Business

    • Status of SIGs/TCs

      • Technical Committee on Enhancement Proposal Processes

        • Goal: Upgrade and improvements over REP
        • Chair: Geoff Biggs (presented by Vanessa Yamzon Orsi on behalf of Geoff Biggs)
        • Members: PMC Leads
        • Update:
          • Draft of scope and process is in progress, aiming to circulate to the TGC for review in the March 2025 meeting, however there is a possibility of an upcoming extension request
          • Items in discussion: platform for collecting, reviewing and discussing enhancement proposals, process for handling backlog

      • SIG on Interoperability

        • Chair: Michael Grey
        • In this month’s meeting, Aaron Chong (Intrinsic) presented on recent developments on RMF-web that improves modularity.

    • Results of vote to recommend adoption of GAI policy

      • The received votes are as follows:
        - 5 for, 1 abstention; quorum was not reached and therefore the motion is lost.
      • Discussion opened regarding two topics:
        • Broader discussion on voting and how to encourage more votes
        • Specific discussion regarding why this particular motion did not attain the required quorum.
      • Takeaways:
        • Explore increased asynchronous communication methods to give members more time to study and discuss issues.
        • Explore options for asynchronous voting to remove hindrances from live voting during TGC meetings, consider methods for preserving discussions and voting records by matter.
        • More explicit calls to action in communications and increase in follow-ups.
        • Review charter specifications and amend them if necessary.

    • Report on progress on federated mirroring

      • The effort falls under discussions within the OSRA as to how we could do more to make ROS and other project resources more available to those in the community who are not able to reliably access centralized resources like GitHub, ROS wiki, and other documentation sites hosted in the United States.
      • We have existing guides but some information is outdated. We need a new and more comprehensive guide with expanded information and a way to verify that a mirror of a repository matches what is available.
      • Currently assessing tools that would make this possible, and further work on building this guide is on the Infra project team’s radar.
      • Discussions were had regarding the timeline and resources needed vs other Infra team projects, approach to project execution, and impact on ROS metrics and assessing community growth.

New Business

  1. Welcome to new TGC members
    Several new members are joining the TGC from this meeting:
    • Bence Magyar (Locus) - ROS Controls Project Leader
    • Clara Berendsen (Ekumen) - Infrastructure PMC Representative
    • Daniel Gordon (Huawei) - Gold Representative
    • Christian Henkel (Bosch) - Gold Representative
    • Maria Carolina Vergo (ROS-I) - Silver Representative

Other Items

Adjournment - Vanessa Yamzon Orsi adjourned the meeting at 15:25 UTC.

ACTION ITEMS

  1. The meeting minutes will be circulated to the TGC for review and approval before the next meeting by the TGC Chair.
  2. Steven! Ragnarok (Infra PMC Lead) to send a summary of the federated mirroring progress report to the TGC.
  3. The TGC Chair will lead the research on async communication and voting mechanism improvements.

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/osra-tgc-meeting-minutes-for-february-2025/42941

ROS Discourse General: ROS Deliberation Community Group Meeting - April 7, 2025

The next ROS Deliberation Community Group meeting will be on 2025-04-07T15:00:00Z UTC.

Google Meet link: https://meet.google.com/njs-ieym-dgk

Agenda:

Feel free to propose additional agenda items, join the mailing list, or the Discord server.

- Sebastian

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/ros-deliberation-community-group-meeting-april-7-2025/42937

ROS Discourse General: ROS 2 tutorials upgrade & entrance level complexity

Hi, this will be a long post!

I’m a late ROS 1 → 2 transitioner with a research and teaching background. I learned ROS long ago by myself and was also taught it at under and grad level. However, when I arrived at ROS 2, I had a hard time adapting, even though I had plenty of experience with ROS. After a year, I have thought deeply about the reasons and arrived at two main reasons:

  1. The tutorials and onboarding experience.
  2. There is a lack of established practices.

The second is getting better every day, and I think that it’s a matter of convergence for the community. However, the first is more concerning, in my opinion. Over the last months, I have gathered a series of points that could be improved and I would like to share it with all of you, get your feedback, and possibly your help for improving the tutorials and general docs. The aim of this post is to work towards a general tutorial upgrade to ease the entry-level experience for users.

Why? ROS tutorials are the entry point for both newcomers and transitioners. From our teaching experience, if the complexity gets overwhelming, students will simply avoid ROS at all costs. I have discussed this issue with people from different backgrounds and experiences and agree that, currently, it’s difficult to approach ROS 2 unless you have been an early developer.

Why now? ROS (1) EOL has arrived, and a lot of transitioners will use the tutorials to look for differences between the two major versions. Any undergraduate and graduate education that didn’t transition will do it before the next semester starts.

How? So far, I have gathered in this document (EDIT: Please, even if you leave a comment in the GDocs, write also a comment on this post to keep it alive) a list of improvement points with a clear action that could be turned into a GitHub issue in the docs repo. However, before flooding the repo, I would like to have some initial feedback from the community, hence this post. I think that some organization such as a work group could also be interesting.

Next steps So far, I would appreciate some feedback on the general idea and the specific ideas in the document linked above (it has commenter permissions). I would also appreciate any other ideas in this post. Finally, ideas on how to organize the workload and a possible work group are also appreciated. After that, we could move on to the actual work!

Just as a disclaimer, this post is not a complaint. I understand that the whole community puts a lot of effort into gradually improving all the content. My objective is to give it a push so everyone can have an easy approach to using and contributing to this community.

56 posts - 23 participants

Read full topic

[WWW] https://discourse.ros.org/t/ros-2-tutorials-upgrade-entrance-level-complexity/42926

ROS Discourse General: Invitation to Collaborate on AsyncAPI Specification for ROS2

Dear ROS Community Members,

image

We are excited to announce that we are crafting a standard message representation for ROS2 using AsyncAPI. A draft is already available on GitHub, and we warmly invite the ROS community to join us in refining this specification. Your input is invaluable, and we encourage you to participate in the ongoing discussions.

Right now, we have developed an AsyncAPI binding for ROS2, and there’s a vibrant conversation happening on GitHub. To enhance collaboration, we’re planning to hold an open discussion session. To help us find a time that suits everyone, please indicate your availability using the Microsoft Forms link below:

:backhand_index_pointing_right: Indicate Your Availability Here

image

Slot 1: 2025-04-08T12:00:00Z UTC→2025-04-08T13:00:00Z UTC

Slot 2: 2025-04-09T12:00:00Z UTC→2025-04-09T13:00:00Z UTC

Slot 3: 2025-04-10T08:00:00Z UTC→2025-04-10T09:00:00Z UTC

Slot 4: 2025-04-10T14:00:00Z UTC→2025-04-10T15:00:00Z UTC

If you’re interested in learning more about AsyncAPI and its significance for ROS2 users, we invite you to watch the ROSCon DE talk we presented last year:

:movie_camera: Watch the ROSCon DE Talk - PDF
( @destogl would you please help us access the video recording, please?)

Join the discussion on GitHub:

:rocket: AsyncAPI Specification Draft on GitHub

We look forward to your contributions and to meeting you all soon!

Best regards,

Florian

This Communication is part of the aerOS project that has received funding from the European Union’s Horizon Europe research and innovation programme under grant agreement Nº101069732

10 posts - 7 participants

Read full topic

[WWW] https://discourse.ros.org/t/invitation-to-collaborate-on-asyncapi-specification-for-ros2/42915

ROS Discourse General: Interop SIG April 3, 2025 - Scenarios: How to manage a multiverse

Community Page

Meeting Link

Calendar Link

2025-04-03T15:00:00Z UTC

The site editor is a tool in the Open-RMF project that allows users to sketch a facility in 3D and specify the mobile robot traffic rules within it.

A common requirement when designing the operations within a facility is the need to consider many different configurations of robots. You may want to see what happens when they are positioned differently or have different properties. You might see positive or negative impacts on the effectiveness or efficiency of your operations under the different circumstances.

A recently introduced feature to the site editor is the concept of Scenarios which allows users to create inter-related variations of scenarios within the same facility. Scenarios can have parent/child relationships with each other where child scenarios inherit the characteristics of parent scenarios and then introduce their own modifications. This creates branching worlds where modifications to a parent scenario will carry over into the child scenarios, while child scenarios can diverge from each other.

At this month’s session, Xiyu Oh will introduce us to the scenarios feature.

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/interop-sig-april-3-2025-scenarios-how-to-manage-a-multiverse/42910

ROS Discourse General: Jetson AI Research Group Meeting - 4/1/25 9AM PST

Hi Everyone,
The JetsonAI Research Group is meeting tomorrow (4/1/25) at 9AM PST.

  • Hope to see you there,

    2 posts - 2 participants

    Read full topic

    [WWW] https://discourse.ros.org/t/jetson-ai-research-group-meeting-4-1-25-9am-pst/42907

    ROS Discourse General: New packages and patch release for Humble Hawksbill 2025-03-31

    We’re happy to announce a new Humble release!

    This sync brings several new packages and some updates to ROS 2 core packages. (I haven’t included the project board for patch info because there was nothing on it.)

    Package Updates for Humble

    Added Packages [27]:

    Updated Packages [535]:

    Removed Packages [0]:

    Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:

    1 post - 1 participant

    Read full topic

    [WWW] https://discourse.ros.org/t/new-packages-and-patch-release-for-humble-hawksbill-2025-03-31/42906

    2025-04-12 13:07