Hi all
I've sent this to what I hope is a representative subset of TrustedFirmware.org project maintainers. Feel free to forward to others you think should be included.
I'm writing to gather maintainer feedback on a proposal for TrustedFirmware.org to have a policy on the use of AI-assistants in code contributions. Several other open-source organizations already have their own policies. Attached is the current draft of that policy, which is based on the Linux Foundation and Apache Software Foundation guidance. This has been discussed at the TF.org board and more recently, the TSC (see minutes here<https://lists.trustedfirmware.org/archives/list/tsc@lists.trustedfirmware.o…>). Eric Finco @ ST had 2 pieces of feedback to this, the 2nd of which prompted me to seek this wider input. To summarize that feedback:
1. Eric would like all contributions that use AI assistants to explicitly attribute the tool(s) used in the contribution for transparency reasons. The counter feedback is that this might be onerous to generate (especially if a tool has a complex backend) and there is no clear use for that information.
2. Eric would like the policy to apply to all TrustedFirmware.org projects, rather allowing projects to develop their own project-specific guidance (as per the current draft).
Some of this might require more interaction discussion. My plan was to invite you all to a future TSC meeting (perhaps in September) to discuss further. I'm happy to take feedback on the policy, Eric's feedback or the process to handle this. Feel free to reply to this email (to all or just to me), or just wait for that TSC meeting.
Best regards
Dan.
Hi all
Apologies for the delay, but here are the minutes from the last TSC:
Present:
Dan Handley (Arm)
Antonio DeAngelis (Arm)
Bharath Subramanian (Arm)
Eric Finco (ST)
Kangkang Shen (FutureWei)
David Brown (Linaro)
Julius Werner (Google)
Dominik Ermel (Nordic)
Michael Thomas (Renesas)
Bharath presented the TF-A roadmap (attached)
This is mainly about enablement of the 2023-2024 architecture extensions
Eric: Is Rust SPMC something new for the Rust project?
Dan: No, we're just taking the previous Rust SPMC prototype project and turning it into a library for reuse in RF-A and potentially other projects too.
Bharath: Dan - do you want to say something about TF-RMM?
Dan: Just that TF-RMM (and Linux kernel guest) has CCA 1.0 support upstream, but Linux host upstreaming has been delayed a long time.
Dan: Due to this and KVM maintainer feedback, we're planning some significant changes to the CCA roadmap.
Dan: This requires some replanning - we'll give a more comprehensive CCA update in a future session.
KK: I went to OSFC conference
KK: It was a good 1 week conference. The presentations are online
KK: We are sponsors so I got a ticket!
Dan: Any particularly interesting sessions?
KK: One from Microsoft about TF enablement but you have to be UEFI member to see it.
KK: Also asked Microsoft guy if he would present this at TF.
KK: I will send contact details.
Dan: Also, note there will be an update on some important changes at Linaro at the next board meeting.
Julius: Is that board meeting the earlier one?
Bharath: Yes
Julius: Will it be recorded?
Bharath: We can ask for that bit at least to be recorded. Will also ask Bill to distribute the slides.
Bharath: There's a TF budget surplus so we're asking if there are any suggestions on how to spend this?
(no response)
