# 2026-07-22 - coreboot Leadership Meeting
## Open Action Items
* 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 : [July 30, 2026](https://coreboot.org/calendar.html)
* [OSFC 2026](https://www.osfc.io)
* Date: 15 - 17 September
## Attendees
David Hendricks, Mina Asante, Julius Werner, Matt DeVillier, Werner Zeh,
Ashmita, Felix Singer, Jay Tallbott, Alicja Michalska, Maximilian Brune.
## Minutes
### [Martin] Here's the list of possible candidates for new core developers,
based on work from the last 2 years: Arthur Heymans, Pranava Y N, Jayvik Desai,
Nicholas Chin, Alicja Michalska, Nicholas Sudsgaard.
* Please share any thoughts or concerns before we finalize.
* [Matt] All names look reasonable to be put into the core developers
group, no objections. These people have a strong knowledge of the coreboot code
base.
* [Werner Zeh, Julius] No objections, we can promote the mentioned people.
### [Martin] Inactive Reviewers on Gerrit.
* We currently have 58 people in the reviewers group (people who can +2 or
-1) who haven't had any activity on gerrit in over 2 years.
* How do we handle this issue?
* Should we remove them or leave them?
* [Alicja] Want to make a list of those people and see if they are still
reachable over the e-mail address.
* [Matt] We should reach out to the people and at least send up a heads-up
e-mail. If the e-mail just bounces, we can simply remove them. Based on the
feedback we can then remove the ones that are OK with them.
* [Jay Talbott] I am not that active on Gerrit and would love to stay
in the group. So please ask before removing.
* [Alicja] Will go through the list of people and send out an e-mail.
Martin needs to pass the list of people to Alicja (IRC/Slack/Matrix).
### [Werner] The SuperStack consortium has been accepted by the European
Committee.
* coreboot was a last-minute application into this consortium to strengthen
the European Open Source sovereignty, which now was accepted by the committee.
### [Alicja] I’m currently blocked on Phoenix OpenSIL upstreaming because we
don’t have a local clone. Is there anyone with appropriate permissions who can
do that, so Jenkins won’t start screaming at us when I start publishing the
patches?
* [David] We have an OpenSIL Phoenix PoC repo, does it not help?
* [Alicja] It would but it is empty right now. It should be a clone of
(https://github.com/openSIL/openSIL/tree/phoenix_poc)
* [David] I guess we should delete opensil_phoenix_poc and just have an
openSIL mirror (ask Martin first) (the individual platforms are on branches,
like phoenix_poc, genoa_poc, etc).
* [Felix Singer] Our submodule points to the github repo at the moment
which has multiple branches for different platforms
(https://review.coreboot.org/admin/repos/opensil_phoenix_poc,general). Genoa
and Turin has code in it right now.
* [Werner] We talked about it in the past and back then the statement was
that AMD will not accept any patches to their repo. So we should maintain our
own fork of it. Are we still willing to do so?
* [Matt] Yes, we have to fork it and then maintain it ourselves.
* [Felix Singer] I will take care of forking the repo and setting
it up for us.
# Next Leadership Meeting Date
* August 5, 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]
