March 15
Attendees: Don, Joanna, Dave R, Anton, Glen, Shebu
Minutes:
-
Boards - Theo worked with Google and now has the Lazor’s flashing and running -
System Down? -
Ben mentioned a network error -
Joanna: Jobs seem to be running again -
mbedTLS -
Meeting with the team weekly. Code reviews have been happening and PullRequest jobs started last week on production. -
Next is start setup of FreeBSD -
Joanna - resourcing challenges, some of the CI work they have been relying on Linaro to do, there still are some gaps. Docs are user specific, vs developer specific. Would be good to have some sessions and some knowledge transfer. -
Anton - Would be good to understand what the roles and responsibilities are for people. When an issue occurs, who do they contact.
-
Joanna - have some of the general knowledge, but some of the details. -
Shebu - balance the day to day tactical and put the documentation over time. -
There was an openCI R&R that Ryan Harkin ryan.harkin@arm.com
*Don post-meeting comment*: ^^^ we've attempted to put a process in place wherein for any and all issues found, step 1 is to <Create> a ticket from the TFC Dashboard https://linaro.atlassian.net/jira/software/c/projects/TFC/boards/70 with Labels == TrustedFirmware, setting the Priority appropriately, and including a description. The whole team watches this project, so this _should_ be a dependable way to submit issues. Then Glen/team assign the issue to the right person and you(customers) can be abstracted.
The above said, we also have the shared slack channel now, and if we're online we can help answer questions/escalate issues/etc. We can discuss/optimize/agree on/document the above more formally if it needs to be.
-
Shebu - Mid March, ARM would like to extend the two engineers. Update? Don has met with Tim Benton so he is updated and understands the request. Glen has spoken to the engineers. Expecting follow-up from Engineering soon.
To help facilitate
Joanna - resourcing challenges, some of the CI work they have been relying on Linaro to do, there still are some gaps. Docs are user specific, vs developer specific. Would be good to have some sessions and some knowledge transfer.
I have created a TFC epic https://linaro.atlassian.net/browse/TFC-242?atlOrigin=eyJpIjoiZThjNWRjZGE2MD... to contain requests for help developers.
Contains the first request for help https://linaro.atlassian.net/browse/TFC-243?atlOrigin=eyJpIjoiMTk3ZTk2NDhjND... around updating OpenSSL version in docker images to run TF-A tests.
Joanna
From: Don Harbin via Tf-openci-triage tf-openci-triage@lists.trustedfirmware.org Date: Tuesday, 15 March 2022 at 23:43 To: tf-openci-triage@lists.trustedfirmware.org tf-openci-triage@lists.trustedfirmware.org Subject: [Tf-openci-triage] TFC Triage Minutes March 15 March 15
Attendees: Don, Joanna, Dave R, Anton, Glen, Shebu
Minutes:
-
Boards - Theo worked with Google and now has the Lazor’s flashing and running -
System Down? -
Ben mentioned a network error -
Joanna: Jobs seem to be running again -
mbedTLS -
Meeting with the team weekly. Code reviews have been happening and PullRequest jobs started last week on production. -
Next is start setup of FreeBSD -
Joanna - resourcing challenges, some of the CI work they have been relying on Linaro to do, there still are some gaps. Docs are user specific, vs developer specific. Would be good to have some sessions and some knowledge transfer. -
Anton - Would be good to understand what the roles and responsibilities are for people. When an issue occurs, who do they contact.
-
Joanna - have some of the general knowledge, but some of the details. -
Shebu - balance the day to day tactical and put the documentation over time. -
There was an openCI R&R that Ryan Harkin ryan.harkin@arm.com
*Don post-meeting comment*: ^^^ we've attempted to put a process in place wherein for any and all issues found, step 1 is to <Create> a ticket from the TFC Dashboard https://linaro.atlassian.net/jira/software/c/projects/TFC/boards/70 with Labels == TrustedFirmware, setting the Priority appropriately, and including a description. The whole team watches this project, so this _should_ be a dependable way to submit issues. Then Glen/team assign the issue to the right person and you(customers) can be abstracted.
The above said, we also have the shared slack channel now, and if we're online we can help answer questions/escalate issues/etc. We can discuss/optimize/agree on/document the above more formally if it needs to be.
-
Shebu - Mid March, ARM would like to extend the two engineers. Update? Don has met with Tim Benton so he is updated and understands the request. Glen has spoken to the engineers. Expecting follow-up from Engineering soon. -- Tf-openci-triage mailing list -- tf-openci-triage@lists.trustedfirmware.org To unsubscribe send an email to tf-openci-triage-leave@lists.trustedfirmware.org 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.
tf-openci-triage@lists.trustedfirmware.org