| Re: [tractusx-dev] Committer Election additional information |
|
Hi all, I share the pain points of Sebastian. We should avoid introducing double standards in committer elections. In the past we voted -1 when there were no contributions at all to Eclipse-Tractusx.
As a minimal contribution I would have expected at least a subscription to our mailing list, but none of the four has subscribed to our ML. Cheers Carsten Von:
tractusx-dev <tractusx-dev-bounces@xxxxxxxxxxx> im Auftrag von "sebastian.bezold--- via tractusx-dev" <tractusx-dev@xxxxxxxxxxx> [**EXTERNAL E-MAIL**]
Hi all, I think we should discuss all four of the currently open elections:
The contributions that Stefan listed all look promising to me, but non of them are based on Tractus-X infra.
I am not 100% sure, but as I understood the election process, the nomination should show contributions to the automotive.tractusx project. (From EF project handbook # Committer Elections: ‘A
committer nomination should explain the candidate’s contributions to the project‘) Being committer in one project does not automatically qualify for becoming committer in others. Even though the contributions to the other eclipse projects do look good. I would actually appreciate to see some contributions to Tractus-X directly, so that we see not only the general Eclipse Foundation rules, but also for example our Release Guidelines (https://eclipse-tractusx.github.io/docs/release)
are known and understood. If the colleagues mentioned are actively developing in Tractus-X, I guess it should be easy to collect contributions, that could be shared in this Thread here (contricutions = code, PR reviews,
discussions on mailing list, etc.) How do the other committers see these elections? Best regards Sebastian Von:
tractusx-dev <tractusx-dev-bounces@xxxxxxxxxxx> im Auftrag von "Stefan.Ettl@xxxxxx" <Stefan.Ettl@xxxxxx> [**EXTERNAL E-MAIL**]
Hi all, because of the elections for Paul and Enrico, I would like to give you more examples of their work. Both are very experienced in the Eclipse Dataspace Connector Project. Both are very active in
the Eclipse Project in development, issues, validation as well as overall community building. We want to leverage this knowledge now for the TractusX-EDC, as the Eclipse Dataspace Connector project is a huge part of it. Both have already applied their knowledge in the TractusX-EDC from product-edc. Within the EDC Community both are very active and also very well known. For the Eclipse Dataspace Connector this election is very important in order to build up the TractusX-EDC open-source project as fast as possible by meeting all Eclipse rules. Best Regards, Stefan More Examples: Paul Latzelsperger: https://github.com/paullatzelsperger Decision Recors: https://github.com/eclipse-edc/Connector/pull/2577 https://github.com/eclipse-edc/Connector/pull/2540 PR: https://github.com/eclipse-edc/Connector/pull/2558 https://github.com/eclipse-edc/Connector/pull/2553 https://github.com/eclipse-edc/Connector/pull/2516 -------------------------------- Enrico Risa: DataPlane Store https://github.com/eclipse-edc/Connector/pull/2159 https://github.com/eclipse-edc/Connector/pull/2203 Http Dynamic Receiver https://github.com/eclipse-edc/Connector/pull/2276 Callback Data Plane to Control Plane https://github.com/eclipse-edc/Connector/pull/2116 Identity Hub abstraction for VC format https://github.com/eclipse-edc/IdentityHub/pull/76 Registration Service Participant Store https://github.com/eclipse-edc/RegistrationService/pull/43 https://github.com/eclipse-edc/RegistrationService/pull/48
|