Attendees: Janos Fallath, Matteo, Joanna, Don, Glen, Xinyu, Ben C

Minutes:

- Cancel next week instance - folks are out

Platform enablement

- Chromebook: Arthur wrapping up the work, when receive the platforms will be ready. - Cypress: Got the info and moving forward again. - NXP Platform: Some back ground work to see best way to integrate - Focus back in Cypress

Other

- expect scripts. in holding pattern with focus on mbedTLS - MC: Two months away from end a FY. Would like expect scripts are finalized. Would like as a background task when things get blocked - MC: Would like to at a minimum know what needs to be done and what help Leonardo may need. LAVA help for example? Anything that can be done in parallel. So what is left and who needs to do which task? - MBedTLS - JF: Don't have AMI's yet, working to get them out. So blocked. Can't set up environment. - GV: Jumped forward to M3's for now. Will need to get to having this up on a real system. - GV: By end of the week, M3 should be done, having the AMI files will be key at that point to move on. - JF: Originally, scripts / files were to be pulled in. Now thinking of a restricted repo and sharing it - may not have that option. What can be used beyond a public repo? - JF: Can Linaro see the private Arm instance? - Glen: Have to check if can see the private repo *ACTION Glen*. - Glen: Set up a sync to review repo sharing options *ACTION Glen* - Movng to gitlab? - JF: Not at this point - JF: Could move the test repo to gitlab, but same issue. - SC Approved: - Code Coverage tool - Joanna: A new ticket raised TFC-160. Can we disable code coverage for now until the gitlab.arm.com is back up. Without it, jobs are failing. - MC: Should we wait? - Joanna: TF-A has been down since Friday. - MC: Can we see what Dean does to resolve? - Plan to see if can disable code coverage until resolved. - MC: Can we be explicit in the ticket on what Linaro is to do. i.e request disable code coverage on TF-A