Hi all,

Notes from today are posted at https://github.com/OpenAMP/openamp-system-reference/wiki/OpenAMP-System-Refe...

* Decisions/conclusions:

* What should we do for GitHub main branch security policies? (TSC topic) i. Disable force push on main branch. If it is ever needed, the repo owner can enable it for making a specific fix & then disable it again. ii. Change main branch via pull requests only iii. We will not restrict rebase of patches (on any branch) b/c GitHub pipeline automatic rebase is useful when you're merging multiple PRs in a row. GitHub will warn you about lexicographical conflicts.

* OpenAMP is no longer just about rpmsg and remoteproc, but our messaging is lacking around the expansion up the stack (Virtualization, Safety) & recent focus on Virtio work. Once we have demos/presentations, we should try to get the word out on OpenAMP's wider scope. * It doesn't make sense to do much work on doc cleanup right now if we're considering bringing in a contractor to make big changes.

* Action items: * Arnaud will check with Ed if it would make more sense to reduce his ownership level to certain repos instead of full GitHub org.

Tammy, Bill: I updated the 2024 task tracking sheethttps://docs.google.com/spreadsheets/d/1J0fRanLA3QXM3lLnigltnPR399dtNoOxoNVUwyzi5vU/edit?usp=sharing to remove the doc cleanup tasks reflect decision/conclusion (c) above.

@Hildebrand, Stewartmailto:Stewart.Hildebrand@amd.com: Sorry, I forgot to add you on the call for agenda.

1. Do you have an update on the action item: Stewart will check w/ Stefano if was already existing or would be new work: app example w/ performance measurement on AMD HW that Linaro can build upon to show real-time capabilities of Xen on generic HW with Zephyr as DomU 2. Please let me know if I should add you to the OpenAMP System Reference mailing list (low traffic).

If anyone on the list is missing the call invitations & wants to attend, please reach out to me directly.

Thanks & regards, Nathalie