Hi Lionel,

 

The TF-A team including myself don’t normally attend the TSC meeting unless we are needed for a particular issue. The discussion about your RFC is primarily with elements of the TF-A team and seems TF-A specific rather than cross project so I don’t see the TSC needs to get involved. I see dialogue in the patch stack with 3 or 4 of the TF-A team and also I see replies today on the TF-A ML discussion so hopefully it will start moving again although most folks our side start disappearing next week for the end of year holidays. Because this is a fairly large patch stack covering 18 patches over many files we will nominate somebody our side to help coordinate with you which will default to me.

 

I think regarding the dashboard we need to adjust the TF-A contribution guidelines that when large features are proposed as well as any patch stack in gerrit being submitted we would request a posting on the TF-A ML to introduce the work and create an entry in the proposed RFC dashboard so contributors more easily see what RFC’s are being discussed. I think smaller changes need only the gerrit review requests as happens today as we don’t want to be too bureaucratic.

 

Regarding the request for direction of TF-A development I’ll rather defer to Matteo on how to respond to that.

 

Thanks

 

Joanna

 

 

 

Hi Joanna,

 

Thanks for your feedback.

 

There is no priority on the current review on going, I’d just point out that, if required, it is possible to make a short explanation about this MTD framework on going. No apologies needed as I know that there is a lot of review to be done.

 

For the second point, it’s fine for me, there is no absolute needs for the coming TSC meeting, the sharing proposal over a first table on the wiki is okay. I’m wondering that it could help to understand the direction of TF-A development and maybe discuss other topics or discuss RFC during this meeting.

 

Regards,

Lionel

 

 

Hi Lionel,

 

For this MTD framework RFC although there is no progression in Gerrit I see there has been some discussion on the TF-A ML https://lists.trustedfirmware.org/pipermail/tf-a/2019-November/000125.html .

 

Apologies this seems to have stalled our side. We have a little bit of a patch backlog issue and we are working to unblock this will look to continue the discussion in Gerrit and the ML thread. This may well be January now so apologies on that as the patchset is quite significant.

 

On the subject of TF-A feature dashboard I’m not aware of anything beyond the material Matteo shares periodically. We in the Arm TF-A Eng team have been trying to engage more on the TF-A ML by sharing designs for upcoming feature as RFC’s rather than just springing them as patchset reviews but today we don’t have a list of forthcoming RFC’s. I’m afraid as things look to be ready to our end we will share. A dashboard though sounds like a sensible thing as we can all track RFC’s submitted from ourselves and others. I’ll take an AI to set something up on the wiki in the first instance maybe as a table. It may need to wait though until January now. Any suggestions welcome on content and format.

 

Thanks

 

Joanna

 

Hi Abhishek,

From a TF-A concern, I'm wondering to know if there is any feedback of a MTD framework already under review (till October).

https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/2284

I'd like also to know if there is a kind of dashboard about the feature development, I've seen that some encryption, key split that have been recently pushed.

Is there any sharable dashboard on the feature development on going for TF-A?

BR,

Lionel

Hi All,

 

Any topics for this week’s meeting?

 

Thanks,

Abhishek

 

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.