# 2025-05-28 - coreboot Leadership Meeting
## Attendees
Mina Asante, Jon Murphy, David Hendricks, Martin Roth, Werner Zeh, Julius
Werner, Alicja Michalska,
Matt DeVillier, Ziang Wang, Jay Talbott, Maximilian Brune.
## Open Action Items
* 2025-05-28
* [Open] Martin: Create DevBD branch
* 2025-05-14
* [Open] Martin: Review the list of people with +2 rights and update it
before the next release.
* 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] We need a name for the coreboot rabbit logo
* Currently, we typically refer to it as "the coreboot logo," and I think it
would be great to assign it a unique name to make it stand out. Here are a few
suggested names Rabbot, Harry, Rabby,
Harry Hare.
* Suggested names from the mailing list: Corebunny, Corry, Peter, The Rabbit
of Corebannog, Peter
Rabbit, Speedy The Rabbit, Speedy.
* [David] Perplexity suggests "Blitz" which translates well between English
and German.
* Put up a poll - Should we name the coreboot rabbit, what’s a good name?
### [Martin] I’d like to propose setting up a dedicated google chat group for
everyone attending
the leadership meetings. This group would be used to share updates, important
info, and reminders
before and during the meetings.
* [martin] Does this split the discussion even further?
* We have discord, irc, slack, mailing list already.
* Julius: Make this a general chat for coreboot?
* Set up matrix with bridges to various services? Is there a bridge to
google chat?
* [Werner] Promote one of the existing channels to be the “official”
channel. Educate people to report issues here.
Which channel? Slack, discord, irc?
* Let’s look at solutions to bridge the services and join the community
again.
### [Ziang] Leadership meeting in Asia time
* Greetings, everyone! not sure if it’s appropriate for me to show up here,
but FWIW I’d like to run
the Asia leadership meeting if it is still on track. We could gather companies
in the APAC area and
schedule a bi-weekly call. Project sync or upstream plan would have a right
place to be carried out
in this way.
* This sounds great. What time?
* Maybe afternoon in China so people in India can attend?
* Probably want to do the meeting in English?
* 7:00-7:30AM GMT+2 can work for Werner (Germany)
* 2pm China time.
* Need to formalize way to set up branches and repos
* Create DevBD branch [martin]
### [Max] GCC 15 is still causing issues. As more distributions are now moving
to GCC 15, this is
getting to be an increasingly annoying problem.
* In order to build the toolchain again:
(https://review.coreboot.org/c/coreboot/+/87650)
* In order to build coreboot again:
(https://review.coreboot.org/c/coreboot/+/87656)
* compiling clang is still a problem
* Can we make a macro to handle the differences between gcc 14 & 15
* Can’t build clang when gcc15 is the system toolchain
* Need to figure out how to use other toolchains to build clang.
* Publish a document on how to use older system toolchains to build the
coreboot toolchain.
### Information
* The mailing list software has been upgraded and we've got a new set of
build servers to lower the cost.
* The next release is scheduled for just over 3 weeks - June 20th.
# Next Leadership Meeting
* June 11, 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/1NRXqXcLBp5pFkHiJbrLdv3Spqh1Hu086HYkKrgKjeDQ
_______________________________________________
coreboot mailing list -- [email protected]
To unsubscribe send an email to [email protected]
