To make it easier for our community to maintain an active contributor status, we’re introducing a new notification service for the Eclipse Contributor Agreement (ECA).
Starting June 11, 2025, we will begin sending email reminders before a standalone ECA is set to expire. For those who need to take action, the email will have a subject line of “Action Required: Your Eclipse Contributor Agreement (ECA) is Expiring Soon” and will contain a link to renew the agreement.
If you are an Eclipse committer who has signed an Individual Committer Agreement (ICA), or an employee of a member organization that has signed the Member Company Committer Agreement (MCCA), you do not need to renew the standalone ECA, as both agreements already include it. If you are covered by one of these agreements, an expiring standalone ECA will not affect your ability to contribute. In this case, you will receive a separate informational email with the subject: “No Action Required: Your Eclipse Contributor Agreement (ECA) is Expiring Soon” to confirm your status.
For those covered only by a standalone ECA, if it expires, you won’t be allowed to contribute to open source projects at Eclipse until you sign it again. Specifically:
- You will no longer be able to submit a merge request to an Eclipse project repositories hosted on Eclipse Foundation GitLab.
- Your commits included in a GitHub Pull Request will fail our automated ECA validation check.
If this happens, you can always restore your ability to contribute by visiting https://accounts.eclipse.org/user/eca and signing the ECA. Your contributor status will be restored once the new agreement is processed, which may take 5 to 15 minutes for our system caches to update.
For any questions or feedback, please join the discussion on our HelpDesk issue.
