Hi All,
Please find the minutes from the last TSC below.
Attachments to be sent separately.

Best regards,
Don Harbin - sent on behalf of the TSC chair

Attendees: Dave Cocca, Lionel Debieve, Eric Finco, Kangkan Shen, Miklos Balint, David Brown, Kevin Townsend, Abhishek Pandit, Joakim Bech, Don Harbin

Minutes:

  • Dan: Groups.io update.  David B learned that Zephyr used it, but a different migration source (Google groups).  More straightforward than ours. So would expect a rough transition. Could make it work if we started over without promising a seamless migration.  

    • David B: Adding user names should be straightforward.

    • Dan: Yes. Major concerns are live migration to TrustedFirwmare.org domain and archive migration.  Three ways to proceed: 1) Manage disruption as we go and hope for the best, 2) Go for a clean setup,  3) Drop for now 

    • A wider tooling issue for TF.org.  Github/Gerrit and things like Slack are under consideration.

    • AP: Not sure how much more we should invest on this. If we had a communication channel like Slack, there would be less need for mailing lists.  

    • DB: Groups.io may also remove ongoing headache from managing mailman. 

    • Dan/Joakim: Mailman not much of a burden these days.

    • DB: Spam rules can cause issues.  List clients can often look like spam.  Email providers may then start to reject folks on the list.  Groups.io would be motivated to fix such things.

    • AP: Groups.io not even responding to support queries. 

    • Dan H: Linaro IT is resistant.If we can’t get them onside  then who will push this through?

    • Linaro IT is currently managing mailman OK, so should we just leave it?

    • JB: Proceed or not?

    • DB: Perhaps pursue Slack as chat platform? It’s free if you don’t want history archived. Can be expensive if you need other features as there’s a per-user cost.

    • Is Mailman a big issue?

    • At this point, not so much.

    • AP: Perhaps table this for now and if we decide to move from Phabricator handle this at this time.

    • AP: With no volunteers to champion, close this and re-open if something changes.

  • Lionel: FF-A coming into OP TEE and PSA certs. 

    • Miklos: Presented attached FF-A enablement slides

    • Eric: How backward compatible are the proposed changes?

    • Miklos: They can be made backwards compatible if configured accordingly. Existing services can continue to be supported with GP APIs and new services can use FF-A.

    • Joakim: Is FF-A expected to replace GP APIs?

    • Miklos: GP is widely used. Both are likely to co-exist. On a particular segment/configuration, one may be more relevant than the other.

<end>