**Collection of the Governing Board meeting minutes** **28th November 2018** The Trusted Firmware Board met again on Wednesday 28th November 2018. Project Charter changes review and discussion on the possibility of making it publicly available. Charter will need to be updated, then published to website. Proposal to form a Technical Steering Committee which will be self-organized 4+1 charter changes proposed. Will be voted offline via email. Licensing clarification - does this apply to binary components? Do we approve them individually? Do we need separate repositories? This will be discussed in the next meeting. Project budget review, approval & ideas: discussed various ideas on investing project budget: sponsored talk/session at Linaro Connect? Additional CI systems? What’s included in the initial scope of work? One or two boards and maintenance ‘within reason’ Cortex-A migration will be covered by Arm - FVP + one or two Juno boards. Overall agreement that CI improvements are a good way to spend the budget. Discussion on the opportunity of spending on engineering effort for accelerating development (especially on TF-M). It's going to be difficult due to the expertise needed. Platform porting can be a self-contained activity that doesn’t impact core maintainers. BUT platform porting is contentious if to a competitor. It should be company members boards. The Board should probably define Project Goals first and then directions from there. Project Contributions Ideas/Plans from members Next meeting proposal: Wed 30th Jan **31st October 2018** The Trusted Firmware project held its own first Board meeting on Wednesday 31st October 2018. Representatives from all the six founding members were present and everyone gave a brief overview of its involvement into the project. The Board discussed the possibility of defining metrics for the project success, such as adoption, deliverables, milestones. TF-A and TF-M are likely to start with different tracks and metrics, due to the different maturity level, but the end goal would be to harmonise them. The project outbound licensing terms need to take into account the existing inclusion of code from 3rd party projects that are released with a different license with respect to the one covering Trusted Firmware (BSD 3-Clause). Any new addition of external code from projects that use a license other than the BSD 3-Clause license will need to be fully understood in context and approved by the Board. The Board agreed to have public summary of meeting minutes to be shared on a dedicated wiki section. TF-A and TF-M are currently providing monthly status reports publicly available on the blog. Feedbacks to the board on the usefulness of those are welcome. The formation of a Technical Steering Committee ("TSC") was also discussed and the Board agreed to have one common TSC for both TF-A and TF-M that can have two separate TF-A/TF-M sections during TSC public meetings. Trusted Firmware already has public mailing lists to discuss project technical topics: https://lists.trustedfirmware.org/mailman/listinfo/tsc https://lists.trustedfirmware.org/mailman/listinfo/tf-m https://lists.trustedfirmware.org/mailman/listinfo/tf-a https://lists.trustedfirmware.org/mailman/listinfo/tf-a-tests The Board agreed to reconvene on a monthly basis with the next meeting planned by Wednesday 28th November.

**Collection of the Governing Board meeting minutes** **28th November 2018** The Trusted Firmware Board met again on Wednesday 28th November 2018. Project Charter changes review and discussion on the possibility of making it publicly available. Charter will need to be updated, then published to website. Proposal to form a Technical Steering Committee which will be self-organized 4+1 charter changes proposed. Will be voted offline via email. Licensing clarification - does this apply to binary components? Do we approve them individually? Do we need separate repositories? This will be discussed in the next meeting. Project budget review, approval & ideas: discussed various ideas on investing project budget: sponsored talk/session at Linaro Connect? Additional CI systems? What’s included in the initial scope of work? One or two boards and maintenance ‘within reason’ Cortex-A migration will be covered by Arm - FVP + one or two Juno boards. Overall agreement that CI improvements are a good way to spend the budget. Discussion on the opportunity of spending on engineering effort for accelerating development (especially on TF-M). It's going to be difficult due to the expertise needed. Platform porting can be a self-contained activity that doesn’t impact core maintainers. BUT platform porting is contentious if to a competitor. It should be company members boards. The Board should probably define Project Goals first and then directions from there. Project Contributions Ideas/Plans from members: topic to be evaluate from members for next Board meeting. The Board agrees to reconvene on Wed 30th Jan. **31st October 2018** The Trusted Firmware project held its own first Board meeting on Wednesday 31st October 2018. Representatives from all the six founding members were present and everyone gave a brief overview of its involvement into the project. The Board discussed the possibility of defining metrics for the project success, such as adoption, deliverables, milestones. TF-A and TF-M are likely to start with different tracks and metrics, due to the different maturity level, but the end goal would be to harmonise them. The project outbound licensing terms need to take into account the existing inclusion of code from 3rd party projects that are released with a different license with respect to the one covering Trusted Firmware (BSD 3-Clause). Any new addition of external code from projects that use a license other than the BSD 3-Clause license will need to be fully understood in context and approved by the Board. The Board agreed to have public summary of meeting minutes to be shared on a dedicated wiki section. TF-A and TF-M are currently providing monthly status reports publicly available on the blog. Feedbacks to the board on the usefulness of those are welcome. The formation of a Technical Steering Committee ("TSC") was also discussed and the Board agreed to have one common TSC for both TF-A and TF-M that can have two separate TF-A/TF-M sections during TSC public meetings. Trusted Firmware already has public mailing lists to discuss project technical topics: https://lists.trustedfirmware.org/mailman/listinfo/tsc https://lists.trustedfirmware.org/mailman/listinfo/tf-m https://lists.trustedfirmware.org/mailman/listinfo/tf-a https://lists.trustedfirmware.org/mailman/listinfo/tf-a-tests The Board agreed to reconvene on a monthly basis with the next meeting planned by Wednesday 28th November.

**Collection of the Governing Board meeting minutes** **28th November 2018** The Trusted Firmware Board met again on Wednesday 28th November 2018. Project Charter changes review and discussion on the possibility of making it publicly available. Charter will need to be updated, then published to website. Proposal to form a Technical Steering Committee which will be self-organized 4+1 charter changes proposed. Will be voted offline via email. Licensing clarification - does this apply to binary components? Do we approve them individually? Do we need separate repositories? This will be discussed in the next meeting. Project budget review, approval & ideas: discussed various ideas on investing project budget: sponsored talk/session at Linaro Connect? Additional CI systems? What’s included in the initial scope of work? One or two boards and maintenance ‘within reason’ Cortex-A migration will be covered by Arm - FVP + one or two Juno boards. Overall agreement that CI improvements are a good way to spend the budget. Discussion on the opportunity of spending on engineering effort for accelerating development (especially on TF-M). It's going to be difficult due to the expertise needed. Platform porting can be a self-contained activity that doesn’t impact core maintainers. BUT platform porting is contentious if to a competitor. It should be company members boards. The Board should probably define Project Goals first and then directions from there. Project Contributions Ideas/Plans from members: topic to be evaluate from members for next Board meeting. Next meeting proposal:The Board agrees to reconvene on Wed 30th Jan. **31st October 2018** The Trusted Firmware project held its own first Board meeting on Wednesday 31st October 2018. Representatives from all the six founding members were present and everyone gave a brief overview of its involvement into the project. The Board discussed the possibility of defining metrics for the project success, such as adoption, deliverables, milestones. TF-A and TF-M are likely to start with different tracks and metrics, due to the different maturity level, but the end goal would be to harmonise them. The project outbound licensing terms need to take into account the existing inclusion of code from 3rd party projects that are released with a different license with respect to the one covering Trusted Firmware (BSD 3-Clause). Any new addition of external code from projects that use a license other than the BSD 3-Clause license will need to be fully understood in context and approved by the Board. The Board agreed to have public summary of meeting minutes to be shared on a dedicated wiki section. TF-A and TF-M are currently providing monthly status reports publicly available on the blog. Feedbacks to the board on the usefulness of those are welcome. The formation of a Technical Steering Committee ("TSC") was also discussed and the Board agreed to have one common TSC for both TF-A and TF-M that can have two separate TF-A/TF-M sections during TSC public meetings. Trusted Firmware already has public mailing lists to discuss project technical topics: https://lists.trustedfirmware.org/mailman/listinfo/tsc https://lists.trustedfirmware.org/mailman/listinfo/tf-m https://lists.trustedfirmware.org/mailman/listinfo/tf-a https://lists.trustedfirmware.org/mailman/listinfo/tf-a-tests The Board agreed to reconvene on a monthly basis with the next meeting planned by Wednesday 28th November.