# 2025-01-22 - coreboot Leadership Meeting
## Attendees
Felix Singer, Andre, Mina Asante, Werner Zeh, Felix Held, Jay Talbott, Maximilian Brune, Matt DeVillier, David Hendricks, Julius Werner, Alicja Michalska, Karthik R, Jon Murphy, Jeremy Compostella.
## Open Action Items
* 2024-11-27 * Send out poll with regards to LLM usage (requested by SFC) * 2024-10-30 * Add clarification to docs, “do not use gerrit change-id or CB: format in reference to already-merged patches”. * 2024-10-16 * 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 * 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 * 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) * Daniel: Look at how we want to localize (non console) strings for coreboot. Long term project.
## Minutes
### [Werner] What is the guidance for the length of the first commit line? * We used to have a Wiki entry for that which I have ported over to our new documentation (see [CB:85915](https://review.coreboot.org/c/coreboot/+/85915)). Shall we still stick with 65 (max 75) characters, or shall we adjust? A quick [survey](https://mail.coreboot.org/hyperkitty/list/coreboot@coreboot.org/thread/YR7JU...) on the mailing list did not reveal any path forward. * [FelixH] 72 chars is used to prevent line breaks when the commit is formatted for e-mail. * [David/Matt] Subject lines often have long paths (as mentioned by others). We should have some guidelines and examples on how to keep this small (what part of the path to mention, acceptable abbreviations for "mainboard", "common", etc) so as to avoid over-crowding the subject line.
### [Werner] Our documentation website (doc.coreboot.org) seems still not to be updated periodically. Is there something we need to do? * [FelixS] Documentation is currently built weekly by a cron job. It's a hacky solution intended to help with migration from old server to new one. Future plan is to have documentation built by CI. * [Matt] Can we increase frequency of cron job? * [FelixS] Yes, that should be possible. * We'll increase it to once per day
### [Werner] Intel has some plans around signing their FSP binaries and would like to present details to the community some day. * Can we offer a dedicated call for that with a broader representation of the community? Or shall we just do it in one of the regular Wednesday-Calls? * [Max/Felix] We probably don't need another meeting. Someone from Intel can just bring it to this one. * [FelixH] What validates signatures? Do we not own the reset vector on Intel platforms anymore? * [David] It seems like a good thing if signature validation is optional. If it's mandatory and enforced by ME or something then that will be terrible since it will cripple portability to other platforms. Can't use a validated Intel binary from a BKC in a new product, for example, and people with FSP source code won't be able to build and run it on a validated Intel platform (CRB). * [Alicja] What is the justification? This will negatively impact debuggability. * Alicja: The first answer was "security". The second answer is to reduce the number of issues due to customized FSP binaries out there.
### [Werner] Our last release 24.12 seems stuck (behind schedule). Anything we can do about it? * [FelixS] It's ready, we just need to update the blog. Tag was created. * But there is some issue - `git describe` shows 24.08. Maybe it's not annotated?
# Next Leadership Meeting * February 5, 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.
# coreboot leadership meeting minutes https://docs.google.com/document/d/1NRXqXcLBp5pFkHiJbrLdv3Spqh1Hu086HYkKrgKj...