Hi @germag! 
Thanks for sending along your questions. I am happy to help. I’ll address each one below.
1- One of our projects has a dual license Apache 2.0 AND BDS-3-Clause (both OSI approved), with 2 license files, GitLan shows “Other” in the overview. I unsuccessfully tried different things to make GitLab identify both licenses, so I can take the first screenshot of the project overview, the only workaround I found was to concatenate both files in one LICENSE file but GitLab only identify the Apache 2.0 license, it’s that ok?
Thanks for bringing this to our attention, and for your kind offer to concatenate the files. But that won’t be necessary. When you apply, simply choose either license to screenshot and we’ll take it from there.
2- Also a project in the same namespace, is the website HTML code of the project (using a GitLab Page), its license is CC-BY-SA-4.0, which is not listed as OSI approved.
You’re correct that Creative Commons licenses aren’t OSI-approved; however, as the CC-licensed project is among many other projects in your namespace that are carrying OSI-approved licenses, I feel confident saying this won’t be an issue for your enrollment in the GItLab for Open Source Program. We’ll know for sure when we’re able to review your application.
I hope that helps! Looking forward to seeing your application.