Hi all
Attached are 3 slides I prepared on the groups.io topic.
Regards
Dan.
From: TSC <tsc-bounces(a)lists.trustedfirmware.org> On Behalf Of Abhishek Pandit via TSC
Sent: 20 January 2021 19:41
To: tsc(a)lists.trustedfirmware.org
Subject: Re: [TF-TSC] TSC Agenda 21 Jan 2021
Updated agenda:
* Review community guideline draft - https://developer.trustedfirmware.org/w/collaboration/community_guidelines/
* groups.io update from Dan Handley
Thanks,
Abhishek
From: Abhishek Pandit
Sent: 18 January 2021 12:03
To: tsc(a)lists.trustedfirmware.org<mailto:tsc@lists.trustedfirmware.org>
Subject: TSC Agenda 21 Jan 2021
Hi All,
Any agenda items for this week's meeting? Can I please have responses by the end of Tuesday 19th?
Currently on the agenda:
* Review community guideline draft - https://developer.trustedfirmware.org/w/collaboration/community_guidelines/
Thanks,
Abhishek
Hi,
On Tue, 19 Jan 2021 at 23:11, Julius Werner via TSC <
tsc(a)lists.trustedfirmware.org> wrote:
> Hi Abhishek,
>
> > Review community guideline draft -
> https://developer.trustedfirmware.org/w/collaboration/community_guidelines/
>
> Is the intention that we review this draft before the meeting so that
> we can discuss it there? Because all I can access is a stub page that
> links to two other pages (inclusive language and code of conduct),
> both of which I do not have permission to open. Please fix the
> permissions on those if they are ready for review.
>
Same here with the permission and I also wondered the same.
Regards,
Joakim
Hi Abhishek,
> Review community guideline draft - https://developer.trustedfirmware.org/w/collaboration/community_guidelines/
Is the intention that we review this draft before the meeting so that
we can discuss it there? Because all I can access is a stub page that
links to two other pages (inclusive language and code of conduct),
both of which I do not have permission to open. Please fix the
permissions on those if they are ready for review.
Thanks,
Julius
Cancelled. Please note that in cancelling today's meeting I
accidentally cancelled the series, so I had to also send out a new invite
to get those back in your calendar for the upcoming 3rd thursdays of each
month. Sorry about that.
Don
On Thu, 17 Dec 2020 at 05:16, Abhishek Pandit via TSC <
tsc(a)lists.trustedfirmware.org> wrote:
> Hi All,
>
>
>
> There is no agenda for the meeting so I suggest we cancel it.
>
>
>
> Thanks,
>
> Abhishek
>
>
>
> *From:* Abhishek Pandit
> *Sent:* 15 December 2020 17:34
> *To:* tsc(a)lists.trustedfirmware.org
> *Subject:* TSC Agenda 17 Dec 2020
>
>
>
> Hi All,
>
>
>
> Any agenda items for this week’s meeting?
>
>
>
> Thanks,
>
> Abhishek
> --
> TSC mailing list
> TSC(a)lists.trustedfirmware.org
> https://lists.trustedfirmware.org/mailman/listinfo/tsc
>
Dear TSC,
I sent the summary below to the board yesterday and Dan suggested it would
be good to share with the TSC as well.
Let me know if you have any questions. :)
Best regards,
Don
---------- Forwarded message ---------
From: Don Harbin <don.harbin(a)linaro.org>
Date: Wed, 2 Dec 2020 at 16:18
Subject: New Blog posts / website updates FYI
To: <board(a)lists.trustedfirmware.org>
Hi all,
I wanted to make sure you all were aware of some new content on the website
and the Phabricator (wiki). Below are the items of note:
- TF-M 1.2 release blog here:
- https://www.trustedfirmware.org/blog/tfm-v1-2-blog/
- TF-A 2.4 release w/ Secure ELS here:
- https://www.trustedfirmware.org/blog/TF-A-and-Hafnium-v2.4-release/
- You will see the updated TF Member list on the website now including
our newest two members (NXM and OMP - Welcome!).
- https://www.trustedfirmware.org/
- I've had our public meeting calendar integrated into the top of the
meetings page.
- This calendar will improve over time as we get all TF projects
public meetings integrated in. It will also provide a quick way to get
up-to-date dial in info for the meetings (some members have had issues
getting the invites into their corporate email accounts)
- https://www.trustedfirmware.org/meetings/
- Finally, per the last Board meeting, I had an action to provide
Board access to the new Community Development project on Phabricator that
has been proposed. It took me a bit of time to get the content to a place
where it was ready to share; I think it's much closer now. Please take a
look
- Community Development Project Home:
https://developer.trustedfirmware.org/project/profile/24/
- Tasks currently tracking:
https://developer.trustedfirmware.org/maniphest/
- Wiki home page for this with content relevant to submitting and/or
getting involved in TF ecosystem tasks:
https://developer.trustedfirmware.org/w/collaboration/community_development/
NOTE: There were ~5 or so individuals subscribed to the TF Board maillist
that I couldn't map emails to github accounts needed to provide access. So
if you have problems accessing the above, just drop me a note with your
github credentials that you use to log into the phabricator/wiki and I can
add you.
Note also that I gave access to the members of the TSC as requested by Dan
H (again, only for those that I could find github credentials in
phabricator).
Please feel free to send me a note with any questions. We also have the
board meeting Dec 9th, so we can have related discussions at that time as
well (if time allows)
Best regards,
Don
Attendees:
Joakim Bech (Linaro)
Dan Handley (Arm)
Eric Finco (ST)
Abhishek Pandit (Arm)
David Brown (Linaro)
Ashutosh Singh (Arm)
Kevin Townsend (Linaro)
Andrej Butok (NXP)
Dave Cocca (Renesas)
KangKang Shen (FutureWei)
Julius Werner(Google)
Lionel Debieve (ST)
ACTION: AP to propose specific website updates to TSC that incorporates inclusive language text.
ACTION: All to review Joakim's security incident flow diagrams
ACTION: Dan to ask Don about opening up community project items in Phabricator
Minutes:
AP: Light agenda today. Just an update on previous approvals.
AP: Trusted Services project is approved by TSC. There are some pending Arm internal approvals that have nearly completed. Expect to push first patches in the coming week.
AP: Inclusive language proposal is approved by TSC.
AP: Propose to have code of conduct page on website. Could be based on another org's policy. Zephyr looks a good candidate.
AP: Also want to provide a short info about the organization structure on the main website
AP: Inclusive language draft can then be incorporated into those pages.
ACTION: AP to propose specific website updates to TSC that incorporates inclusive language text.
AP: Expectation then will be that project leads will add the text to their own project specific documentation (e.g. coding guidelines).
AP: AOB?
KKS: Was looking for public meeting link for tech forums. Couldn't find them.
AP: We can move the links somewhere more obvious if you want?
KKS: Actually the link in "News & Blogs" is good enough. Just need to get used to the new site.
https://www.trustedfirmware.org/meetings/
JB: We purchased GP test suite a while ago. Since about 3 weeks ago this is now integrated into OP-TEE CI system.
https://optee.readthedocs.io/en/latest/building/gits/optee_test.html#extend…
JB: Have been trying to supplement security incident process with diagrams. Have had early feedback from some (e.g. DH). Now would like to share with TSC for feedback.
https://people.linaro.org/~joakim.bech/tf/
JB: Think this is necessary as the text is quite complex.
https://developer.trustedfirmware.org/w/collaboration/security_center/repor…
DH: Agree. Really useful to show default flow in 1st diagram. Text is complicated due to lots of potential caveats. Each project could show their own specific flow if needed.
DH: Diagrams 2-3 are more linked to the process for security team members so could be added there
https://developer.trustedfirmware.org/w/collaboration/security_center/setup…
AP: Could also write a blog that uses these diagrams and explains the caveats in more detail.
DH/JB: Might need to look at colour scheme before integrating to website
ACTION: All to review Joakim's security incident flow diagrams
AP: 2 other in-progress items: Migration to groups.io and prototyping GitHub/Gerrit integration. Was hoping for update from Don on that.
DH: This and other board/TSC items are captured in Phabricator but visibility is limited at present. We should get those opened up, at least for all board/TSC members
ACTION: Dan to ask Don about opening up community project items in Phabricator
Hi All,
Any agenda items for this week's meeting?
Following are on my list currently
* Inclusive Language guidelines
* Trusted Services project
Thanks
Abhishek
Hi all,
Please find the mInutes from the October 15 TrusteFirmware TSC below.
Best regards,
Don Harbin
TrustedFirmware Community Manager
don.harbin(a)linaro.org
Trusted Firmware TSC 15 October - MinutesAttendees
*Abhishek (Arm)Julian Hall (Arm)Gyorgi Szing (Arm)Dan Handley (Arm)KangKang
(FutureWei)Julius Werner (Google)Joakim Bech (Linaro)David Brown
(Linaro)Don Harbin (Linaro)Andrew Butok (NXP)Dave Cocca (Renesas)Michael
Thomas(Renesas)*Actions:
*Abhishek: Send inclusive language email for voteAbhishek: Check to see if
can share Trusted Service Project use casesAbhishek: Gather vote on Trusted
Services Project request through emailDanH: Talk to Matteo / Shebu about
requirements for continued support of s/w stacks on new h/w (in particular
the 8.4 and beyond). Develop a migration plan.*Minutes:
Trusted Services Project request
-
TSC needs to approve. No budgetary impacts
-
JH: Shared overview slides of Trusted Services Project
-
JH: Ready to re-publish the work. A build system is in place. Tests in
place.
-
Need a public repo
-
Need tf.org front page update
-
Need Mail list
-
CI is a TBD
-
DanH: Plan to go to public CI from the start?
-
Gyorgy - an internal CI first would be easier.
-
DanH: Need to be aware of what upstream CI will require ahead of time
-
DC: How are CI requirements related to other ongoing projects
-
Gyorgy - currently no implementation, would need to do that and implement
-
DC: What about ongoing CI?
-
DanH: Should eventually migrate to TF CI
-
AB: Why not develop as part of TF-A Project?
-
Abhishek: Ideally would migrate TF-A services into this at some point.
-
JH: A stand-alone w/ dependencies makes sense
-
DanH: Within Arm, want to integrate the components in multiple
configurations.
-
Abhishek: Would help if clarify TF-A vs TF-M.
-
JB: Do we have use cases defined on how these will be used
-
JH: For crypto services, yes. Device Identity, Audit Logs, building
blocks to secure an IoT device are some examples.
-
JB: People ready to start using?
-
JH: Yes in the edge space
-
JB: Understanding the use cases on problem solving would be helpful
-
JH: Focus has been on Cortex A use cases
-
Abhishek: Will work to close this vote soon.
Inclusive Language
-
Abhishek: Looks like sufficient support.
-
No budget required, so no formal vote required. Want a vote?
-
DC: Vote here is ok.
-
Don: Destination of wording?
-
JW: Propose into coding style guides
-
Abhishek: Could also be a developer wiki page.
-
I.e. Duplicate in each coding guidelines plus a common section on the
wiki.
-
Maintainers would be asked to add these to the Projects Coding
Guidelines.
-
DanH: Proposing having it in one place and pointing to it.
-
Abhishek: Formalize the decision. Then can decide how to deploy.
-
Don: Where is exact wording?
-
Abhishek: Propose an email vote and the email will include the exact
wording in the email. Also that the maintainer for each project is
responsible to integrate into their coding guidelines
Arm V8 → 8.4 transition
-
JB: Member Companies have expressed concerns about Arm V8 and changes
required to 84.. What should we tell people?
-
DanH: Don’t have to change S/W on 8.4.
-
Abhishek: How does Hafnium leverage it?
-
JB: Don’t want to forget this when making changes. All changes may not
be backward compatible.
-
DanH: Take back to Matteo / Shebu a discussion about a migration plan
-
JB: Impacts to OP TEE components important to this.
<end>
