Implement a Workflow for ECA Expiry Reminders and Automatic Revocation

Description:

We need to implement a workflow that reminds users to re-sign the Eclipse Contributor Agreement (ECA) before it expires. We also need to implement a process where we automatically revoke an ECA in the FoundationDB if it's expired. The ECA is valid for 3 years, so I propose that we start notifying users 3 months before their ECA is set to expire.

Workflow Steps:

1. Three months before the ECA expiry date, send an initial email to the user informing them of the upcoming expiry and the need to re-sign the ECA.
2. Send a reminder email once a month for the next two months if the user has not yet re-signed the ECA.
3. Automatically revoke the ECA on the expiry date if it has not been re-signed.

Implementation Details:

• Implement automatic email notifications.
• Include clear instructions on how to re-sign the ECA in each email.
• Provide a link to the ECA renewal form for easy access.
• Implement an automatic process to revoke the ECA once it has expired.

Additional Information:

• This workflow aims to ensure that contributors are aware of the need to renew their ECA every 3 years and to revoke ECAs that have expired.
• Failure to re-sign the ECA before the expiry date would result in contributors not being able to contribute to an Eclipse Project.