Eclipse Codewind Termination Review
The EMO is using this issue to track the progress of a project termination review.
Project leads and committers can add more to the review documentation if desired.
The purpose of a Termination Review is to provide a final opportunity for the Committers and/or Eclipse Membership at Large to discuss the proposed archiving of a Project. The desired outcome is to find sufficient evidence of renewed interest and resources in keeping the Project active.
Here is some context:
- Eclipse Codewind is a project started by IBM in 2019.
- Over 2 1/2 years ago there was a change in management and IBM reassigned all of the project team to other teams.
- There hasn't been a code change from a human in over 2 years, the project lead has confirmed IBM has no dependency on it, and given the chance of security vulnerabilities/upkeep/etc it seems like it would be a good time to terminate/archive it.
Project
Project: Eclipse Codewind Termination Review
Pre-Termination Review Checklist
To be completed by the EMO
-
PMC has been notified -
Project team has been notified via dev-list -
Project team has been notified via email
Post-Termination Checklist
To be completed by EMO
-
Archive the project (PMI) -
Archive the project (Database) -
Retire committers and project leads (PMI) -
Retire Mentor relationships (Database)
To be completed by Webmaster
Shutdown/archive:
-
Website -
Git repositories -
Mailing list -
Forum -
Bugzilla product
Your comments, feedback, and pushback are welcome.