I am also just a Project lead who had to use CQs quite a lot (e.g. resolve License issues with JCP licenses, etc.) but I don’t think a CQ would be necessary for some commits. If his contribution introduced a new external dependency that is not yet under Eclipse Orbit (aka has a CQ) then it might be necessary, just to have him commit, I don’t recall adding a new committer or contributor after they signed their Agreement also requires a CQ.
Werner
Sent from Mail for Windows 10
Greetings esteemed members of the EMO and the Technology PMC,
we have a pending pull-request for jdt.ls [1], contributed by Valerii Svydenko, a Red Hat employee (so same employer as the Submitting Committer where the employer has signed a Member Committer Agreement). The contribution is ~18.5kLOC but mostly consists in copied jdt.ui bits.
It's unclear to us whether we should engage in the CQ process or not, this case doesn't seem covered in the legal poster[2] (or maybe I'm dumb).
Fred
--
"Have you tried turning it off and on again" - The IT Crowd
And if that fails, then http://goo.gl/tnBgH5