2025-12-10 - coreboot Leadership Meetings Minutes

# 2025-12-10 - coreboot Leadership Meetings 


## 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
  * vPub Opensource Firmware Online Party 
    The event schedule and join links are available here: (https://events.dasharo.com/event/9/dasharo-user-group-12)



## Late GMT coreboot Leadership Meeting Minutes


## Attendees
Jay Talbott, Julius Werner, Werner Zeh, Matt DeVillier, Mina Asante, Martin Roth, Alicja Michalska, Karthik R, Christian Walter. 


## Minutes


### coreboot 25.12 release scheduled for next Wednesday, December 17th
  * Please tag patches if needed before the release with ‘coreboot_release_25.12.’
  * If a patch should be held until after the release, tag with ‘post_coreboot_release_25.12.’ 
  * [Matt] Please test as wide as possible current main.
    * [Matt] Intel renamed some folders in the FSP repo (e.g. AlderLake) and now coreboot references files in the wrong directories. We cannot merge the current submodule FSP update because of that. Felix S. submitted a [PR](https://github.com/intel/FSP/pull/122/commits/45e8b958b64eda3703325bc413052fe7d2ea6a04). Shall we fix it in coreboot or wait until Intel fixes it?
      * [Werner] We should wait until Intel fixes it in their repo, I will reach out to them.
      * [Martin] We could fork the repo and fix it on our own. Just an idea.

### [Werner] Revisit coverity request
  * [Martin] I looked into their paid services a while ago, and it was crazy expensive. If they shut down their service now, we could move over to Clang tooling, though its frontend is not super user-friendly. We can support them with some money if the amount is reasonable.
    * [Werner] I asked for the amount and the answer was “...if there are only 10 projects funding, it may reach 100,000 $/year.”
    * [Martin] We should look into alternatives, as we will never be able to spend that amount of money.

### [Werner] Status of the meeting with Intel regarding signed FSP
  * Signed FSP will only apply to FSP in dispatch mode and will be bound to Boot Guard. API-Mode will continue to exist without the signed boot flow. If Boot Guard is enabled, one can still opt-out of using signed FSP mode in the descriptor (BPM-Bit).

### [Martin] What is the current status of the ETSI bootloader standard (EU-CRA context)?
  * [Werner] There was an update of the spec, see (https://docbox.etsi.org/CYBER/EUSR/Open/) 
    Feel free to review and provide comments, the time schedule is tight.
 
### 2025-12-24 coreboot leadership meetings canceled.
  * It falls within Christmas break.


## Early GMT coreboot Leadership Meeting Canceled 
  * No issues on the agenda.



# Next Leadership Meetings Date
  * January 7, 2026.
  * [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]