Re: [automotive-pmc] URGENT: Several committer elections are awaiting yo

["Babanin Andrey, EF-821" <Andrey.Babanin@xxxxxx>]

Hi Andy,

I'm happy to provide the requested information on how Florian has contributed.

(Election page: https://projects.eclipse.org/projects/automotive.score/elections/election-florian-bauerle-eclipse-safe-open-vehicle-core)

Let me start with the Copybara process we set up for the https://github.com/eclipse-score/baselibs repo, since that seems to be the part that was unclear.

BMW first contributed the source code to Eclipse S-CORE in March and April 2025. The code was essentially an extraction from a large git monorepo. Around 240k lines of code that were under active development by several internal teams landed in the eclipse-score/baselibs repository.

At that time S-CORE was just getting started, the first contributions were only beginning to arrive, and the build toolchains were either missing or still in an early stage. To keep the code we had just contributed from going stale, we set up a code sync via Copybara from our internal codebase to S-CORE. This kept our internal development running in parallel while the community got code that stayed current and kept improving. We expected it would take a while before the internal teams completely moved their development into open source, and the internal codebase was cleaned up from a copy of the open-sourced code so it could reference the S-CORE modules directly. Throughout this time, we always accepted third-party contributions, but with one extra step before merging: the improvement also had to be reflected in the internal codebase (example: https://github.com/eclipse-score/baselibs/pull/71).

By now we have almost fully moved development to S-CORE, and the internal repository references the S-CORE modules as a Bazel build system dependency. This let the transition happen smoothly and incrementally, keeping the open-source code alive the whole time. The Copybara workflow is still in place, but we now use it only for a few parts that are still in transition (the current list for the baselibs is in https://github.com/eclipse-score/baselibs/blob/main/.github/workflows/restricted_paths.yml). For these cases, a Copybara sync just looks like a regular PR on GitHub (example: https://github.com/eclipse-score/baselibs/pull/283).

Florian has been directly involved in this from the start. He helped contribute the code from our internal codebase and has been the person driving the transition to open-source development for the baselibs module ever since. He is now working to phase Copybara out entirely, so that Baselibs can continue as a usable standalone module that everyone can benefit from.

Below is a summary of Florian's authored commits to the eclipse-score/baselibs repo. His first publicly visible contribution dates to September 2025.

A few highlights:

- Formatting and copyright checks: https://github.com/eclipse-score/baselibs/compare/e464c331a9374e90c74493ebe9574c9a63508b27...efc061359d159244a9bd31a6f1dc74f9246c07b6 

- Clang-tidy integration and C++ code formatting: https://github.com/eclipse-score/baselibs/compare/80820923ec98bb675a038265170e33fcf73a236a...37c5ac0dc0e1e00938516ba0bae39836f3af285d 

The complete list of Florian's contributions is below.

1. Build/Bazel & CI

- Bazel module/config maintenance: f89fc36d9, c2d9b7e87, f660b75d7, 3e81576c6, 80820923e, edaa95148, 0d75558fb, 3e222b2b7, bd9a13824, a02c76d89 

- CI workflow additions/updates: 37c5ac0dc, f35af1b08, e0f3110ef, 154995ef8, 8027cb6a0 

2. Formatting/linting

- C++ Format config & CI workflows introduced: 54ad821c9, 9d0c9cc58, c26df5972, a2c1f3bc6, e464c331a 

- Formatting applied/fixed across repo: 444d85d4b, b0525dad7, efc061359, 05ff3c4c3, 0e0f7fa53 

3. Copyright/licensing

- Copyright-check infrastructure: 9925dba1f, ab3e9eec2, 3cd3c3ec1 

- Headers added/fixed across modules: 030581d14, dec252de9, 4b67ce192, 602fa653d, 6951cd2a3, f055fdcb0, 04dac701a, 165cbec70, 381dd9a9c, 79c8c48b3, 1561bc47f, 69bd8297d 

- Correct code attribution for code adopted from the LLVM project: 92c327a7d

4. Static analysis, code quality & JSON lib changes

- Clang-tidy config for C++: b96711a56, af03b0aaf, 8302cec73 

- JSON lib fixes (coverity, clang-tidy, overloads): 6106564d7, f6939b3a9, 0fa025ef6, cf3b60cf5, bc8149ed3, 53687228c, c2a25eb39, c5c3fc856, de9ed149e 

- C++ include cleanup across modules: a93a5b3b0, 7eea26b1c, 6f0e83d8f, 880d89b62, c2d29ff39 

- C++ Namespace/type-tagging cleanup: ed76770ec, 836b50b03 

5. Documentation & open-sourcing enablement

- UML diagram conversions to PlantUML/SVG (to be compliant to agreed format in S-CORE): 7d05e838e, 99d49637a, d79ffd181, 9304b37a7, a676d7090, 3df9666a9, 54e67ea01

- Open-sourcing/external-contribution enablement: 3e07e3137, d786e401e, d63001c8d, de2904010, 1f7e6d99c, 52712b7a9 

- Bug fixes & reverts: 8ad6eb154, 6fdf2afee, 17d9b4e5e, b6fe0251f, 8f72e361b, bfc28e03c, 62f717ccd 

To see the diff on github: https://github.com/eclipse-score/baselibs/commit/<HASH> (replace <HASH> with the commit hash from the log above).

Florian also has a few contributions to other S-CORE modules: eclipse-score/tooling (Copyright checker improvements) as well as to eclipse-score/communication and eclipse-score/logging to improve compatibility with baselibs module.

On your question about review and maintenance activities: Florian is one of the most active reviewers in the repo. The leaderboard below ranks github users by the number of PRs they have commented on or reviewed in eclipse-score/baselibs. At this moment, Florian is the most active contributor in the repo (in terms of commenting & reviewing) who does not have committer rights.

1. 4og - 137 PRs - Committer

2. antonkri - 26 PRs - Committer

3. fbaeuerle - 25 PRs - Non-Committer

4. nradakovic - 11 PRs - Committer

5. pawelrutkaq - 11 PRs - Committer

6. paulquiring - 9 PRs - Non-Committer

7. FScholPer - 7 PRs - Committer

8. LittleHuba - 6 PRs - Committer

9. AlexanderLanin - 6 PRs - Committer

10. aschemmel-tech - 6 PRs - Committer

(These numbers for each user were obtained with: `gh search prs --repo eclipse-score/baselibs --commenter <USERNAME> --limit 500`)

A few examples of Florian's participation in PR reviews:

- https://github.com/eclipse-score/baselibs/pull/33 He reviewed an external contribution and declined it with a clear explanation, while inviting the author to resubmit any other fixes separately.

- https://github.com/eclipse-score/baselibs/pull/139 He left review comments on the JSON parser integration suggesting how to improve the implementation.

- https://github.com/eclipse-score/baselibs/pull/237 He suggested changes to the test target that it becomes more CI friendly.

I'm posting this reply to the mailing list as well, so that it becomes part of the public record. And I hope this information helps the PMC in its review of Florian's nomination.

Please let me know if you need any further details or clarifications.

Best regards,

Andrey

--

BMW Group

Andrey Babanin

BMW Car IT GmbH

Software Development Customer Functions

Max-Born-Straße 10

89081 Ulm

 

Telephone: +49-731-37804097

Mobile: +49-152-54980497

Mail: andrey.babanin@xxxxxx

Web: https://www.bmw-carit.de

-------------------------------------------------------------------------

BMW Car IT GmbH

Management: Michael Böttrich, Georg Bätz, Chris Brandt, Christian Salzmann

Domicile and Court of Registry: München HRB 134810

-------------------------------------------------------------------------

 

---

From: automotive-pmc <automotive-pmc-bounces@xxxxxxxxxxx> on behalf of Krivoborodov Anton, EF-80 via automotive-pmc <automotive-pmc@xxxxxxxxxxx>
Sent: Wednesday, July 15, 2026 14:55
To: Andy Riexinger <andreas@xxxxxxxxxxxxxxxxxx>; Automotive PMC discussions <automotive-pmc@xxxxxxxxxxx>; score-dev@xxxxxxxxxxx <score-dev@xxxxxxxxxxx>
Cc: Krivoborodov Anton, EF-80 <Anton.Krivoborodov@xxxxxx>
Subject: Re: [automotive-pmc] URGENT: Several committer elections are awaiting your approval

Dear Andy,

Thank you for your message. I’m still missing some information from your reply and would appreciate a bit more clarity.

Could we clarify the formal criteria and guidelines the PMC uses to decide which committer elections to approve? I believe having transparent, documented rules aligns with Eclipse’s principles of openness. Could you please point me to any documentation that defines these criteria and guidelines?

I also fully appreciate that PMC members contribute on a voluntary basis. At the same time, s-core involves multiple commercial organisations that rely on the Eclipse Foundation for their open-source collaboration. If committer elections routinely take several months, that could become a bottleneck. Would it help if others, for example project leads from the s-core project, provided additional support to the PMC? I’m also happy to assist if useful.

Thank you for your help.

Best regards,

Anton

Von: Andy Riexinger <andreas@xxxxxxxxxxxxxxxxxx>
Datum: Mittwoch, 15. Juli 2026 um 10:33
An: Krivoborodov Anton, EF-80 <Anton.Krivoborodov@xxxxxx>; Automotive PMC discussions <automotive-pmc@xxxxxxxxxxx>; score-dev@xxxxxxxxxxx <score-dev@xxxxxxxxxxx>
Betreff: Re: [automotive-pmc] URGENT: Several committer elections are awaiting your approval

Dear Anton,

thank you for raising this on the mailing list. I agree that discussions affecting project governance should be visible to the community whenever possible.

Let me try to answer your questions directly.

Regarding Florian's nomination

The Automotive PMC does not question Florian's technical qualifications or the positive support expressed by the S-CORE committers. The election result is an important input to our decision, but could be better as at nomination time there were 52 eligible voters. Having a broader participation in the vote always helps us feel confident that the nomination represents a strong consensus across the entire active community.

However, under the Eclipse Development Process, the PMC is expected to perform an independent review to ensure that committer nominations are supported by publicly visible merit and that the project's development process follows the Eclipse principles of openness and transparency.

What information is currently missing?

As discussed previously, we are still waiting for the following information to be provided on the mailing list so that it becomes part of the public record:

• references to a small number of representative PRs demonstrating Florian's technical contributions,
• clarification of Florian's review and maintenance activities,
• an explanation of the Copybara workflow and how contributions are reflected in the public repositories.

Once this information is available, the PMC intends to review the nomination again during its next meeting.

Why are we asking for this?

While commit counts and contributor statistics provide useful indicators of activity, they do not always provide sufficient context to evaluate public merit, particularly where contributions are imported through automated workflows. The additional information helps the PMC perform a fair and informed review.

I hope we can complete Florian's nomination once the remaining information has been provided publicly.

Best,
Andy

P.S. Just a gentle reminder that all PMC members contributes on a voluntary basis as a service to the Automotive community, balancing the PMC work alongside their regular full-time employer-paid jobs. We appreciate your understanding.

CONFIDENTIAL

---

Von: Krivoborodov Anton, EF-80 <Anton.Krivoborodov@xxxxxx>
Gesendet: Dienstag, Juli 14, 2026 11:43 AM
An: Automotive PMC discussions <automotive-pmc@xxxxxxxxxxx>; score-dev@xxxxxxxxxxx <score-dev@xxxxxxxxxxx>
Cc: Andreas Riexinger <andreas@xxxxxxxxxxxxxxxxxx>
Betreff: AW: [automotive-pmc] URGENT: Several committer elections are awaiting your approval

 

Dear Andy,

I’m responding regarding the committer nomination for the S-Core project, since the communication happened behind the scenes and I’d like to clarify the situation.

We nominated Florian Bauerle as a committer almost three months ago; his election page is here: https://projects.eclipse.org/projects/automotive.score/elections/election-florian-bauerle-eclipse-safe-open-vehicle-core.

His nomination was approved by nine project participants.

The nomination includes links to:

• Florian’s commits in the score organization, showing his contributions.
• Baselibs repository statistics, which show Florian is one of the main contributors to that repo.
• Florian’s GitHub profile, where you can review his activity, reviews, and issues he has created.

From my experience nominating committers over the past year, I’d like to offer a few observations and a request:

• To my understanding, the Automotive PMC is not directly part of our project and therefore may not be in the best position to judge the project’s day-to-day contributors and their roles. The most reliable input for committer elections comes from votes by active project participants.
• I believe the committer election process would benefit from a formal definition of the metrics and evidence required for approval. Elections should be a factual, yes-or-no decision based on clearly defined criteria, rather than an essay-style appeal to convince external reviewers.

Could you please:

1. Tell me which specific information was missing that prevented the PMC from making a decision on Florian’s election over the last two months.
2. Provide a link to any existing formal criteria the PMC uses to evaluate committer elections. If no such criteria exist, please propose one or let me know if you’d like me to draft a suggested set of concrete metrics and evidence to present going forward.

Thank you in advance for your help!

Kind regards,
Anton

Gesendet von Outlook für Mac

Von: automotive-pmc <automotive-pmc-bounces@xxxxxxxxxxx> im Auftrag von Andreas Riexinger via automotive-pmc <automotive-pmc@xxxxxxxxxxx>
Datum: Montag, 13. Juli 2026 um 18:22
An: Automotive PMC discussions <automotive-pmc@xxxxxxxxxxx>; score-dev@xxxxxxxxxxx <score-dev@xxxxxxxxxxx>
Cc: Andreas Riexinger <andreas@xxxxxxxxxxxxxxxxxx>
Betreff: Re: [automotive-pmc] URGENT: Several committer elections are awaiting your approval

Sent from outside the BMW organization - be CAUTIOUS, particularly with links and attachments.

Absender außerhalb der BMW Organisation - Bitte VORSICHT beim Öffnen von Links und Anhängen.

---

Dear all,

with regard to the nomination of Florian Bäuerle (https://projects.eclipse.org/projects/automotive.score/elections/election-florian-bauerle-eclipse-safe-open-vehicle-core) the Automotive PMC discussed the nomination again in our meeting today.

Unfortunately, there was a discussion behind the curtain between a S-CORE project lead and one member of the Automotive PMC, where the PMC asked for clarification and information on the mailing list.

Please provide the information on the Automotive PMC mailing list and we are happy to discuss the nomination in our next meeting.

Best,

Andy

On behalf of the Automotive PMC

P.S: To answer on the mailing list, please do not forget to subscribe to it

Am 08.07.2026 um 21:25 schrieb Wayne Beaton via automotive-pmc <automotive-pmc@xxxxxxxxxxx>:

Thanks Lukas.

I've identified two related issues and have bumped them to get them on the team's radar.

• Need way to navigate from project to elections
• Send reminder emails to PMC for pending election approvals

IMHO both proposed solutions are better than the notifications option, but I've opened an issue to address that as well.

Thanks for the feedback.

Wayne

CONFIDENTIAL

On Wed, 8 Jul 2026 at 13:40, Lukas Krawczyk <eclipse@xxxxxxxxxxx> wrote:

Hi Wayne,

thanks for the reminder.

Before voting on these elections, we would like to complete our PMC review. 
As part of our governance responsibilities, we try to ensure that nominations are sufficiently supported by evidence of the nominee's merit-based contributions to the project.

In several of the current nominations, we found the rationale to be rather high level, while concrete references to project contributions (e.g., commits, reviews, issues, specifications, or other community activities) are largely missing. 
We'll therefore take some time to collect and review the relevant evidence ourselves before casting our votes.

Our next Automotive PMC meeting is on Monday, where we typically discuss elections that require additional review. 
We therefore expect to complete the review and vote on these nominations after that meeting.

Thanks for your understanding.

Best regards

Lukas

PS: Just FYI, despite the outstanding approvals, the notification area remains empty for me:

<KQycoWpk26oLv0FJ.png>

On 7/7/2026 3:33 PM, Wayne Beaton via automotive-pmc wrote:

Greeting Eclipse Automotive PMC.

Several committer elections are awaiting your approval. Can you please have a look?

• https://projects.eclipse.org/projects/automotive.score/elections/election-florian-bauerle-eclipse-safe-open-vehicle-core
• https://projects.eclipse.org/projects/automotive.score/elections/election-andreas-mittag-eclipse-safe-open-vehicle-core-0
• https://projects.eclipse.org/projects/automotive.score/elections/election-marius-weber-eclipse-safe-open-vehicle-core
• https://projects.eclipse.org/projects/automotive.score/elections/election-lars-bauhofer-eclipse-safe-open-vehicle-core
• https://projects.eclipse.org/projects/automotive.score/elections/election-frank-scholter-peres-eclipse-safe-open-vehicle-core

FYI, the EMO is aware that our notification system is flawed. If you miss the email amid the noise (or the message gets marked as spam) you won't even know that matters are awaiting your attention.

The PMI has a helpful feature, but it's not especially easy to find: the "Profile" icon in the top-right corner of the PMI includes an option to list notifications. As a PMC member, the list of notifications should include the outstanding elections requiring your attention.

<image.png>

I will connect with the team to see if we can do more to ensure these do not slip through the cracks.

Thanks,

Wayne

-- 

Wayne Beaton (he/him)

Head of Open Source Projects | Eclipse Foundation

_______________________________________________
automotive-pmc mailing list
automotive-pmc@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org

-- 

Wayne Beaton (he/him)

Head of Open Source Projects | Eclipse Foundation

_______________________________________________
automotive-pmc mailing list
automotive-pmc@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org

CONFIDENTIAL