The EMO is using this issue to track the progress of a project termination review.
The project team has cited lack of development activity as the reason for the termination. 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.
Project: Eclipse Golo
Termination review record: https://projects.eclipse.org/projects/technology.golo/reviews/termination-review
golo-lang.org
domain, and we will continue publishing the website as-is (or under a github.io
subdomain with a banner on each page to let people know that the Eclipse Golo project has been terminated, see https://github.com/golo-lang/golo-lang.github.com/pull/19)To be completed by the Project team
To be completed by EMO
- [ ] Retire Mentor relationships (Database)
To be completed by Webmaster
Shutdown/archive:
Your comments, feedback, and pushback are welcome.
Thanks!
Following http://dev.eclipse.org/ipzilla/show_bug.cgi?id=23977 we would like to proceed and transfer https://github.com/vert-x3/vertx-junit5 (keeping history) to https://github.com/eclipse-vertx/vertx-junit5
I'm not saying it's not working as designed, but this is frankly limitating.
My account was initially at a research institution, then at a company, hence it is primarily linked to a personal email to ensure continuity but I don't see why I couldn't use my current employer email as well.
(In reply to Wayne Beaton from comment #6)
This is not an ECA failure. The infrastructure is working exactly as
designed.
The requirement is the email that you have on file with your Eclipse
Foundation Account is the email address that you need to use as your author
and signed-off-by credentials.
So the two workarounds that you have are to either change your email address
on your EF account, or rewrite these commits to use your current email
address.
The thing is I already have an account with a CLA, and my employer is a foundation member. This could be detected by email suffix.
At least I'd need a way to sign the CLA with another email without having to create another account.
Bugzilla Link | 561456 |
Status | NEW |
Importance | P3 enhancement |
Reported | Mar 25, 2020 12:20 EDT |
Modified | Mar 25, 2020 17:50 EDT |
I've submitted a pull-request and the ECA fails: https://github.com/eclipse-vertx/vert.x/pull/3343
The problem is that I have signed-off all the commits and GPG-signed them as well with my Red Hat email (not GMail that is associated to my Eclipse account), so technically as an employee of Red Hat there is no need for the ECA check to fail.
What should I do?
Hello, is there anything from the project side left to do at this stage?
Thanks for creating the review tracking issue.