# 2025-08-20 - coreboot Leadership Meetings Minutes
## Open Action Items
* 2024-11-27
* [Open] Send out poll with regards to LLM usage (requested by SFC)
* 2024-10-30
* [Open] Add clarification to docs,“do not use gerrit change-id or CB:
format in reference to already-merged patches.”
* 2024-10-16
* [Open] Matt: Set up a meeting to discuss board status alternatives and
send out invites.
* Decouple data collection with uploading
* Require gerrit credentials or other auth to push
* Json format?
* https://github.com/chrultrabook/linux-tools/blob/main/debugging.sh
* 2024-09-18
* [Open] Jon: Schedule a dedicated meeting to discuss the Coverity defects
and action plan.
* Werner: Send out an invite for the meeting.
Sent out a poll to find a time slot:
https://rallly.co/invite/1c8J3azXAcje
* 2024-05-01
* [Open] Nick Van Der Harst volunteered for Dutch. "gogo gogo" would like
to translate to Russian (?).
* 2024-01-10
* Nico: (https://review.coreboot.org/q/topic:enforce_region_api)
* [Open] Daniel:Look at how we want to localize (non-console) strings
for coreboot. Long-term project.
## Announcements & Events
* OSFC 2025
Dates: October 7–10, 2025
## coreboot Leadership Meeting - Late GMT
## Attendees
Mina Asante, Martin Roth, Alicja Michalska, Maximilian Brune, Matt DeVillier,
Julius Werner, Ziang Wang, Avi Udey, Andy Ebrahiem,
Carl Turner, Jon Murphy.
## Minutes
### [Subrata] Developing a self-test framework in coreboot
* Mailing list:
(https://mail.coreboot.org/archives/list/[email protected]/thread/ZLHWZGWU2PMP5CIHQ7DBM3XSYTAXQPZA/)
* Spec:
(https://drive.google.com/file/d/1TyOxw_acrextI-GVI2IE4omdg0f1evyn/view)
* Nobody was present to present this for a third time in a row. If this is
important and someone wants to do it, they could take the time to show up to
the leadership meeting to discuss the proposal.
* [Max] Not sure why this is needed inside coreboot. What is there that
can’t be done after coreboot ?
* [Martin] The only thing I can think of would be something like PSP
verstage, which runs in coreboot but not on the x86 processor. If we put this
in a payload, if we wanted to run it before the regular payload, we’d need to
handle chain-loaded payloads. I have no objection to putting tests inside
coreboot so long as they’re well separated from the regular code and optional.
I’m not really sure that we need any sort of dispatcher for the tests; we just
need a well-defined set of reporting structures that the tests can each fill
out.
### [Max] Bug in ticket system
* During the build, coreboot reads out ranges of binaries and creates
signatures for ranges. The file is read before it exists. Patch is several
years old. Has this ever worked? (https://ticket.coreboot.org/issues/607)
* Only relevant for Google builds. Julius will look into it.
### [Alicja] What’s the status of FSP on newer Intel chips? There’s no client
computing group FSP.
* No Intel representatives present in the meeting. We should check to see who
is even still at Intel at this point. There are still people at Intel working
on coreboot with Google.
### [Martin] We should keep an eye on the AI coding assistant conversation
going on at the Linux kernel.
* There was a thread about AI coding assistants on the LKML in July. It seems
to have quieted down, but it’s worth paying attention
to:(https://lkml.org/lkml/2025/7/25/988)
* That said, I’m happy with coreboot’s current stance on AI coding
assistants. All patches are submitted by an individual who is responsible for
the patch contents, however it was developed. Reviewers are responsible for
making sure the code is good quality before submission.
## coreboot Leadership Meeting - Early GMT
## Attendees
Mina Asante, Ziang Wang.
## Minutes
### [Ziang] To raise coreboot ACPI support for QEMU RISC-V virt as a project in
RISC-V Software Ecosystem (RISE) community (require RISE membership for link
below):
(https://lf-rise.atlassian.net/wiki/spaces/HOME/pages/8589425/Firmware+Projects)
* Project Update: I am preparing a training for the RISC-V community, and
hopefully we will have more companions in the corporate community from RISC-V.
* [Martin] Please give a link when it’s ready. I think we’d have interest
in the coreboot community.
* The project is scheduled to span across the 2nd half of 2025.
## Completed Action Items
* Martin: Review the list of people with +2 rights and update it before the
next release.
# Next Leadership Meetings Date
* September 2, 2025.
* [coreboot Calendar](https://coreboot.org/calendar.html).
# Notice
Decisions shown here are not necessarily final and are based
on the current information available. If there are questions or comments
about decisions made, or additional information to present, please put
it on the leadership meeting agenda and show up if possible to discuss
it.
Of course items may also be discussed on the mailing list, but as it's
difficult to interpret tone over email, controversial topics frequently
do not have good progress in those discussions. For particularly
difficult issues, it may be best to try to schedule another meeting.
We now host two leadership meetings, one in early GMT and one in late GMT, to
better accommodate
participants from the Asian time zones.
Kindly note that both sessions use the same meeting notes and Google Meet link.
# coreboot Leadership Meeting Notes
https://docs.google.com/document/d/1NRXqXcLBp5pFkHiJbrLdv3Spqh1Hu086HYkKrgKjeDQ
_______________________________________________
coreboot mailing list -- [email protected]
To unsubscribe send an email to [email protected]
