Identify projects without Project Leads

The intention of this issue is to centralize our efforts to identify all Eclipse Foundation projects that currently don't have a Project Lead.

The project lead is more of a position of responsibility than one of power. The project lead is immediately responsible for the overall well-being of the project. They own and manage the project's development process, coordinate development, facilitate discussion amongst project committers, ensure that the Eclipse IP policy is being observed by the project and more. If you have questions about your project, the Eclipse Development Process, or anything else, ask your project lead.

Below there is a list of projects that are currently functioning without the PL role. Next step is to get in touch with these projects and ask them to elect a Project Lead as soon as possible. We'll use this issue to track the status of the contact with the projects. An email will be send out using the project-dev mailing list.

Information on how to run a Project Lead election is available in the Eclipse Handbook.

A ticked box indicated the project has successfully elected a Project Lead.

Unresponsive projects will be further considered for termination and their resources archived.

• Jakarta Annotations
• Jakarta Config established during proposal phase.
• Vorto
• GeoTrellis
• Proj4j
• Fundamental Modeling Concepts
• Gendoc
• Model-to-Text Transformation (M2T)
• Model Driven Health Tools
• Mylyn Context --> Archived!
• Mylyn Docs - Election
• Vex
• Eclipse Polarsys 3P --> Archived!
• Eclipse Product Lifecycle Management Platform --> Archived!
• Gemini Enterprise Modules
• Gemini JPA --> Archived!
• Gemini DBAccess PL will retire soon, the project hasn't had a commits in a long time
• Eclipse JWT
• Eclipse LSAT (Project Leads added to correct error when creating the project.)
• openK platform --> Archived!
• Sapphire --> Archived!
• Subversive - Election
• Eclipse TM4E - Election
• WTP Incubator Project--> Archived!
• Eclipse Volttron