Skip to content

2025 01 07 Eclipse iceoryx developer meetup

Jump to bottom
Mathias Kraus edited this page Jan 7, 2025 · 3 revisions

Eclipse iceoryx developer meetup

Date: 2025/01/07

Time: 17:00 CEST

Link: https://app.element.io/jitsi.html#conferenceDomain=meet.element.io&conferenceId=JitsiVtfrqukadefbqiqfxryxabai&userId=&roomId=!AooDAAwkyNWwkMElpt%3Agitter.im&roomName=eclipse%2Ficeoryx&startWithAudioMuted=true&startWithVideoMuted=true&language=en

Talking points

Please join the iceoryx gitter chat on https://gitter.im/eclipse/iceoryx and propose talking points for the agenda.

If there are no points on the agenda (except looking at the open tasks from previous meetings) the day before the meeting, the meeting will be skipped.

Attendees

  • Christian, ekxide IO
  • Mathias, ekxide IO
  • Graham, Latitude AI
  • Brendan, Latitude AI
  • Mike, Latitude AI
  • Ryan, Latitude AI

Agenda

  1. Look at the open tasks from previous meetings, 10 min, Mathias
    • Adding the new meeting date to the ROS 2 calendar
    • Check to register iceoryx.rs and maybe iceoryx.com
  2. Discussing classic iceoryx v3.0.0 release
  3. Discuss differences between iceoryx classic and iceoryx2

Minutes

  1. nothing changed
  2. postponed
  3. Differences:
  • better separation for freedom of interference
  • waitset can now handle file descriptors
  • event mechanism is more flexible
  • better mempool handling
    • memory chunks are tied to a publisher
  • separate domains, e.g. for parallel unit tests
  • no central daemon
    • no memory configuration required
    • system config (default number of supported subscribers, etc.) still in TOML
  • request-response is missing but should be finished at the end of Q1
  • Python bindings at end of Q2
  • rmw_iceoryx2 to enable seamless communication between ROS 2 and native iceoryx2
    • safety critical applications can be ported to safety certified iceoryx2
    • non-safety critical applications can continue using the ROS 2 framework
  • zenoh gateway for host2host communication
  • ekxide Mission Control as Swiss knife tool to debug iceoryx2 issues on user side
    • rerun gateway for more sophisticated debugging
  • iceoryx2 C++ bindings currently depend on iceoryx_hoofs
    • those dependencies will be moved to iceoryx2

Topics for future meetings

  1. Move C-binding to separate repo?
    • #2030
Clone this wiki locally