Software WG Meeting 2026/03/10

[mitsudome-r]

Administrative

• Past Meeting Minutes

Common Resources

Click to expand 🖱️🔛

• Past Meeting Minutes
• Autoware Contributors
• Autoware Software WG Project Board
• Autoware Foundation Events Calendar

Attendees

Chaired by Ryohsuke

- Fatih - Bonolo

Autoware.Universe

• PRs waiting for review not in the current milestone/high priority.
• Autoware.Universe reported bugs not in the current milestone/high priority.
• Autoware design discussions and demos

Announcements

Discussions

• Autoware Carla Leaderboard: Scenario Testing for Autoware Universe & CARLA 0.9.16 #6880
• Roscope: reconstruct autoware_launch system topology from launch files, no build, no runtime #6870
• Add differential pointcloud map visualization for RViz #6888

Updates from developers

• Support ROS 2 Jazzy autoware_universe#11418
  • https://github.com/autowarefoundation/autoware/actions/runs/22756054501/job/66000840056
  • ARM docker build is failing
• Remove autoware_auto_common package autoware_universe#11862
  • https://github.com/autowarefoundation/autoware_universe/pulls?q=is%3Apr+is%3Aopen+jazzy
• https://github.com/orgs/autowarefoundation/discussions/4120
  • feat(map): add differential lanelet loading autoware_universe#6241
  • Implement Differential Map Loading feature for lanelet2 map autoware_core#887
• Autoware Universe ➡️ autoware_universe_awf ➕ autoware_universe_community #6849 (comment)

Distribution of new tasks

Action Items

• Developers to add their discussion items to the agenda for the next meeting
• Developers to share updates on their works in the next meeting

[paulsohn]

Sorry, I cannot attend this week, so I just leave some topic list that I think requires some attention recently. These can be discussed as the next week's agenda.

• The direction of Dependency Version Pinning for Reproducible Builds #6861 / feat: dependency version pinning for reproducible builds #6862 are worth being discussed, including the alternative option to use Pixi.
  • My personal opinion is to go with Pixi, plus removing the most part of the ansible usage. Currently ansible is mostly used for installing system dependencies, so I expect Pixi can wipe out most of it.
• A side discussion of Autoware Universe ➡️ autoware_universe_awf ➕ autoware_universe_community #6849 (comment)
  • for short, me and sasaki-san propose that: AWF stops maintaining universal autoware_launch, TIER IV takes full responsibility to maintain their autoware_launch fork as a self-contained system, test it, and showcase to AWF. We still have autoware_core_launch for an official AWF launcher with minimal maintanence.
• launch-plus, my launch system static resolver ( Roscope: reconstruct autoware_launch system topology from launch files, no build, no runtime #6870 ) is still work-in-progress; the functionality is ready but it takes more time to convert the repository into a publically maintainable software development mode.
  • Meanwhile I found some issues on launchers which should be addressed; I created most of them as PR. I will update the relevant list.