# 2025-04-16 - coreboot Leadership Meeting
## Attendees
Felix Singer, Werner Zeh, Julius Werner, Maximilian Brune, Jay Talbott, Alicja Michalska, Matt DeVellier, Mina Asante, Martin Roth, Felix Held, Jon Murphy, Marshall Dawson, Jeremy Compostella, Paul Menzel.
## 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.
## Minutes
### [Martin] Here is a blog post of things we are putting in place to have better engagement with companies: (https://docs.google.com/document/d/1lFUm4A-8F6J0acVbFkE_N_OY6PQcEup0lLPXAe3k...) * This collaboration gives room for companies or entities to enjoy the following benefits: * Private development repos * Public branches in the coreboot repo * ongoing or one-off meetings with companies * official company reps for the leadership meetings * blog posts from companies * FelixS: Why would someone need a private repo? * [Alicja] The current coreboot leadership meeting schedule is not favorable for participants in the Asian time zones, and there are companies here that are interested in coreboot. Is it possible to schedule the meeting in a way that makes it possible for everyone to attend? * [Martin] If there's interest in scheduling another meeting, I’m personally fine with it. However, I can’t guarantee that the leadership team will be able to attend. * [Werner] People are always welcome to update the agenda with their issues even if they cant make it to the meeting or reach out directly to any member of the leadership team at any time, and we will be happy to help. * [Felix H] We should put this on the mailing list to see if there’s a demand for a second leadership meeting.
### [Martin] This is a task from a while back to create a questionnaire poll about the concerns surrounding the use of AI tools in open source development [Possible AI poll questions](https://docs.google.com/document/d/1s__V82xvvojpSuI9fEVD3YwND5_HC26yQyGRXvPp...) * Could I get some review?
# Next Leadership Meeting * April 30, 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...