# 2026-09-30 - coreboot Leadership Meeting
## Open Action Items
* 2026-09-30
* [Open] Matt: To review coreboot’s current coding style guidelines, and
clarification where
needed;(https://doc.coreboot.org/contributing/coding_style.html).
* 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
* Next Open System Firmware - OCP Project Meeting
* Date : [October 8, 2026](https://coreboot.org/calendar.html)
* [Dasharo FSP integration
status](https://3mdeb.com/events/#_dasharo-fsp-integration-status)
* Date: 13th October, 2026
## Attendees
Werner Zeh, Jay Talbott, Maximilian Brune, Julius Werner, Ashmita, Piotr Krol,
Mina Asante, David Hendricks, Ingo Reitz, Matt DeVillier, Nuclid, Alicja
Michalska.
## Minutes
### [Information] coreboot 26.09 release has been tagged.
* Official announcement of the release will be published on October 1st.
* Tarballs have been created as part of the tagging, will be available on the
webpage once everything is done.
### [Werner/Matt] Huge patchtrain to change NULL by ‘nullptr’.
* There is no real value in this move, it disturbed readability a lot. We do
have a coding guideline to not push such long patchsets in row.
* [Max] The unit-tests had issues with this change as it is compiled with
host-toolchain which does not always understand most recent features. Major
distributions do not include the newest toolchain versions.
* [Matt] Shall we be more precise about the preferred coding style in our
guidelines?
* [David Hendricks] We generally align with the linux community (first
paragraph of https://doc.coreboot.org/contributing/coding_style.html).
* [Julius Werner] We had this discussion (nullptr) in 2024 already and
decided there already, not to go with. [See 2024-07-24
notes](https://docs.google.com/document/d/1spx5B45u2IymaQitE-Thbqx4e4ykTok6a_g453AvdNE/edit?tab=t.0).
* [Max Brune] The major take away here seems to be that we do not want to
have the full C23 featureset enabled in our tree.
* [Matt]- AI: Let’s review our current guidelines and add clarification if
needed.
### [Max Brune] mecleaner project is searching for a new place to host the
repo. Shall we take it into the coreboot infrastructure?
https://github.com/corna/me_cleaner/issues/441.
* [Matt] We have some other projects (deguard) already in our infra, we can
provide a new home to mecleaner. We just need to know from which commit we will
do that.
* [Max Brune] I reached out to the old maintainer of mecleaner and he is OK
with moving the code to coreboot infra.
* [Werner] Go with a fresh repo for mecleaner in coreboot infra and copy
the current state into it
* [Piotr Krol] mecleander and deguard is not fully comparable judging on
their capabilities. Will the same question arise in future for the psp-tool?
* [Matt] Is psp-tool useful at runtime as part of the coreboot build?
* [Piotr Krol] Yes, absolutely.
* [Matt] If psp-tool run into a situation where it needs a new home, we
can take a look at it, too and host it if needed.
* [David Hendricks] Will figure out what to do, along with Max and Felix.
# Next Leadership Meeting Date
* October 14, 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.
# coreboot Leadership Meeting Notes
https://docs.google.com/document/d/1NRXqXcLBp5pFkHiJbrLdv3Spqh1Hu086HYkKrgKjeDQ.
_______________________________________________
coreboot mailing list -- [email protected]
To unsubscribe send an email to [email protected]
