Skip to content

ADORe project restructuring (https://github.com/eclipse/adore)

Summary

I’ve recently been assigned by my organization as the new project lead (pending official election) for Eclipse ADORe. There are several unresolved issues related to the project’s governance and structure that I would like to address in this issue.

If this is not the correct location to address this issue please direct me to a more appropriate location. Up until now, I’ve contributed to the project in a developer role and have had limited contact with the Eclipse Foundation’s project governance, so I appreciate your patience as I get up to speed.

Background

  • Due to user demand, Eclipse ADORe for ROS1 has been deprecated in favor of a complete reimplementation for ROS2.
  • At the time of project inception, my understanding was that only one repository was permitted per Eclipse project. However, ADORe ROS2 relies heavily on submodules.
  • Our intention was to maintain the ROS1 version while beginning active development of the ROS2 version in parallel.
  • Due to various technical and organizational limitations, active development was moved to DLR-TS GitHub.

Open Issues

  • Elections have been initiated for the project lead role, but from the Eclipse Foundation's perspective, it appears that development has ceased.
  • The ROS2 version of ADORe (DLR-TS/adore) is still under active development and in active use not on the eclipse-adore org.
    • All recent issues, pull requests, and community activity have occurred there.
  • Many researchers/contributors from DLR-TS who are actively maintaining the project may not recognized as official Eclipse committers.
  • The original ROS1 version of ADORe hosted at eclipse/adore is now completely deprecated.

Goals and Proposal

  • Archive or move the ROS1 version of ADORe to a separate repository within the eclipse-adore organization (e.g., eclipse-adore/adore_ros1).

  • Update(13.8.2025) completed

  • Transfer the actively developed ROS2 version (and its submodules) from github.com/DLR-TS to the eclipse-adore GitHub organization.

  • Update(13.8.2025) completed

  • Initiate due diligence review of repository
    Currently in process, I am doing a manual due diligence audit of the repository and looking into adding automated eclipse tooling to do this before requesting a formal review.

  • Establish proper Eclipse committer status for active contributors from DLR-TS.

    • Update (24.10.2025) awaiting adjudication and path forward from eclipse foundation
    • Update (14.10.2025) Elections declined on the grounds on the following grounds: 1) application was insufficient, 2) there is insufficient eclipse foundation activity (PRs) from the nominees
    • Update (08.10.2025) Elections initiated for 3 group members

Please advise on how best to proceed to resolve these issues.

Priority

  • Urgent
  • High
  • Medium
  • Low

Severity

  • Blocker
  • Major
  • Normal
  • Low

Impact

Potentially blocking project lead elections due to no recent activity/history on https://github.com/eclipse/adore

Edited by Andrew Koerner

Copyright © Eclipse Foundation, Inc. All Rights Reserved.     Privacy Policy | Terms of Use | Copyright Agent