OpenBSW Monthly / 2026-03-30

[johannes-esr]

Participants

@johannes-esr
@dcavalei
@aschaal
@hans-guenterkothgasserbmw
@christophruethingbmw
@jiyuanwangbmw
@christian-schilling
@LarsVoelker
@nhuvaoanh123
@Marzieh-S-BMW

Agenda & Meeting Minutes

• Bazel support #97
  • Bazel support is requested by different parties
  • Wish to add bazel support (for now) in parallel for OpenBSW
  • Interested colleagues to exchange directly
• Support for C++17 as base standard of OpenBSW #136
  • C++17 as minimum requirement for OpenBSW fine -> PR to be opened to remove C++14 CI builds and change min. required version, @dcavalei
• Strategy regarding PR merging: Squash vs. Rebase & Merge
  • Right now, in the GitHub UI "Rebase & Merge" and "Squash & Merge" are allowed, "Merge commit" is not allowed right now
  • If we use "Rebase & Merge", it cannot be seen if the commits "inbetween" have a successful CI run
  • Chains of PRs are hard to handle, because if one PR changes, all subsequent PRs have to be changed as well
    • Idea: Mark subsequent PRs as draft
• Caching: https://github.com/eclipse-openbsw/openbsw/actions/caches
  • @johannes-esr to check with Eclipse Foundation
• Strategy for integration testing: Add cli based integration test #373
  • add functionlity to test on HW, then review in this round

For next meeting:

• Add repository Copilot customizations for openbsw contributors #407
• CODEOWNERS
• PRs

[dcavalei]

Possibility of adopting CODEOWNERS file per component.
e.g. @middleware-reviewers-group + @some-omnipotent-entity, where at least 2 reviews are needed.

[simon-d-bmw]

Copilot Instructions #407