...
While the fix is being implemented for this, we ask the CLA Managers to set their browser language setting to English. This will allow the "pop-up" window to show correctly.
Installing EasyCLA on GitLab repositories
GitLab changed how they managed their authorization for the EasyCLA integration. It now requires a rotating token rather than a static long-lived token. As a result, the EasyCLA GitLab integration is experiencing token expired errors. This issue was reported and is being tracked at https://github.com/communitybridge/easycla/issues/3537
Some FAQ
Do you need an LFID account to sign the Corporate CLA?
No, only the user that will become the Initial CLA Manager will need to have a LFID account to initiate the signatory process in the Corporate CLA Console at organization.lfx.linuxfoundation.org. That user will be prompted with the question "Are you authorized to sign this CLA on your company's behalf?". Selecting "No", the Initial CLA Manager can add the Name and the Email Address of the person authorized to sign the Corporate CLA. This person will receive a DocuSign email and perform the signature without needing to log into the CLA Corporate Console. Once completed, the Initial CLA Manager will received a confirmation email. For more information, please visit: https://docs.linuxfoundation.org/lfx/easycla/v2-current/corporate-cla-managers/coordinate-signing-cla-and-become-initial-cla-manager.
Why does the Linux Foundation ask contributors to some projects to sign CLAs?
...