Re: [disuko-dev] [technology-pmc] Project Lead Election for Karl Piplies

[<christian.wege@xxxxxxxxxxxxxxxxx>]

Karl has been the top contributor since near project inception (PR #15 of 355, spanning the full timeline), with 169 commits, more than any other contributor, and 66 PRs authored (about 19% of all 352 PRs in the repo).

 

Beyond writing code, Karl has actively shaped quality across the team: 62 code reviews on other contributors' PRs, covering UI, analytics, SBOM/component logic, and policy features, not siloed to one area.

 

Karl has also driven architecture and engineering standards: designed core data-layer repositories (analytics, licenses, occurrences, mongo querybuilder), built background job infrastructure (deprovisioning, periodic user deletion, inactive-approval automation), set up the gitleaks secret-scanning hook, and authored both AGENTS.md and backend/frontend developer documentation.

 

Karl's work spans the entire stack, backend infra, domain, server, jobs, and frontend, touching 76 directories and 300+ files. That combination of volume, review authority, and ownership of foundational systems and conventions reflects the responsibility a lead role requires.

 

 

Von: disuko-dev <disuko-dev-bounces@xxxxxxxxxxx> Im Auftrag von Wayne Beaton via disuko-dev
Gesendet: Montag, 17. August 2026 17:53
An: Technology PMC <technology-pmc@xxxxxxxxxxx>
Cc: Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx>; disuko-dev@xxxxxxxxxxx; Eclipse Foundation <emo@xxxxxxxxxxxxxxxxxxxxxx>
Betreff: Re: [disuko-dev] [technology-pmc] Project Lead Election for Karl Piplies on Eclipse Disuko has started

 

[**EXTERNAL E-MAIL**]

The Open Source Rules of Engagement defined in the Eclipse Foundation Development Process (EDP) require that projects operate in an open, transparent, and meritocratic manner. This applies to both committer and project lead elections.

 

In what way has the nominee demonstrated they have gained the trust of the project committers?

 

In what specific, publicly visible manner has the candidate demonstrated they have the trust of the project team and community? Can you point to specific content contributions that demonstrate leadership? Has the candidate authored a road map? Do you have any specific examples of how the candidate has represented the project team in governance matters?

 

The Committer Elections training materials provide some insight into elections (the guidance for project lead elections is similar to what we provide for committer elections). It might also be helpful to review the Eclipse Project Roles training materials to understand the nature of the role. The Eclipse Project Handbook has supporting material.

 

While I have your attention... AFAICT, the project has not yet engaged in the IP Due Diligence Process. I've created an issue to help you get started.

 

Thanks,

 

Wayne

Eclipse Technology PMC Member

EMO

 

On Fri, 14 Aug 2026 at 04:32, Eclipse Foundation via technology-pmc <technology-pmc@xxxxxxxxxxx> wrote:

A Project Lead election for Karl Piplies on project Eclipse Disuko
(technology.disuko) was started by Karl Piplies with this criteria:

Karl Piplies has made an impact on the project.

It is my pleasure to nominate Karl Piplies as a project lead on Eclipse
Disuko.

Eclipse Disuko project committers can click the election link below to vote.

Election: Election for Karl Piplies as Project Lead on Eclipse Disuko [1]

Project: Eclipse Disuko [2]

[1] 
https://projects.eclipse.org/projects/technology.disuko/elections/election-karl-piplies-eclipse-disuko
[2] https://projects.eclipse.org/projects/technology.disuko

_______________________________________________
technology-pmc mailing list
technology-pmc@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/technology-pmc

--

Wayne Beaton (he/him)

Head of Open Source Projects | Eclipse Foundation

If you are not the addressee, please inform us immediately that you have received this e-mail by mistake, and delete it. We thank you for your support.