Proposal: Consider requiring ECA validation on all commits
We currently only enforce the ECA on an Eclipse Project repo. This is everything under gitlab.eclipse.org/eclipse.
We currently allow contributors to push to their fork without an ECA. At this time, our contributors are only made aware of a validation error when they try to merge their changes to the project repo.
In the short term, we are planning to inform the user with a warning on forks. See #84 (closed)
With this issue, I am proposing that we block contributions if the user does not have an ECA on file when pushing to a non-eclipse project repo.
We did this to make it easy for our users to start contributing on Gitlab but we are now noticing that this is creating some extra confusion with some users when it's time for them to submit a MR and they finally see the ECA error.
We've seen this today via eclipsefdn/helpdesk#2199 (comment 1035535)
I am thinking it would be best to simply enforce the ECA on all commits. This way, our contributors would be informed the second they try to push something to GitLab that they need to sign our ECA if they are offside.
Other things to consider:
- Should we also require the ECA for contributions to project wikis or should we keep our exception for that?
- Should we require the ECA for all contributions made under the eclipse-wg and eclipse-ig group?
- Is there any expectations we should consider?