2023 09 07 Eclipse iceoryx developer meetup

Eclipse iceoryx developer meetup

Date: 2023/07/20

Time: 17:00 CET

Link: https://eclipse.zoom.us/j/95918504483?pwd=RWM5Y1pkeStKVDZsU09EY1hnclREUT09

Reduce the number of required reviewers, 10 mins, Mathias "Bob" Kraus
- committers are currently quite slow at reviewing PRs
- even for PRs with a few lines it takes weeks to get a second reviewer
Get rid of used-header.txt or at least move the CI check from pre-flight to the code linting jobs, 10 mins, Mathias "Bob" Kraus
- https://github.com/eclipse-iceoryx/iceoryx/pull/1983 does not even start to run the CI which would give us some information if the changes do not break other platforms
- it does not help in any way since the proposed solution is always to add/remove the header from the list
Can we move away from Zoom for our dev meetings? 5 mins, Mathias "Bob" Kraus
Can we use cirrus-ci for FreeBSD and macOS tests? 10 mins, Mathias "Bob" Kraus
Delete GCC 5.4? 5 mins, Mathias "Bob" Kraus
Enable C++17, 10 min, Mathias "Bob" Kraus
When will the v3.0 release happen?, Mathias "Bob" Kraus

Proposal accepted under the condition that a new checklist item is added to the reviewer checklist along the lines of [ ] For complex new features a 2nd reviewer shall be added, Simon will ask Michael Pöhnl
Script kept but not run in the CI anymore, Bob will create a PR
There are privacy concerns with Zoom, alternatives are: Jitsi (requires an account lately, using a private Jitsi server is not an option, e.g. https://meet.in-berlin.de/ https://jitsi.freifunk-duesseldorf.de/), need to consult Andreas Riexinger about possible Eclipse requirements
GitHub Action Runner Setup is currently used for Ubuntu and macOS, FreeBSD is running on macOS, which makes it very slow, needs to be carefully evaluated whether cirrus CI fulfills the requirement of iceoryx, build examples: https://cirrus-ci.com/build/4804090664845312 Cirrus CI offers aarch64 build, the proposal is to first start with the FreeBSD as this is the most problematic job and caused a lot of issues in the past
GCC 5.4 is not needed anymore, Bob will create a PR
Needs to be carefully evaluated, can be addressed after the v3.0 release, can we do a user survey? Simon to do a survey
No new major features on master, hence decision made in February still holds, that a release should be only done if a new features for the user are available, decision will be postponed to the next meetup, proposal: clean up folder structure and naming convention of iceoryx_hoofs and iceoryx_dust