2025-06-25 - coreboot Leadership Late GMT Meeting Minutes

mina--- via coreboot <[email protected]>
Newsgroups gmane.linux.bios
Message-ID <[email protected]>
# 2025-06-25 - coreboot Leadership Meeting late GMT



## Attendees

Mina Asante, Werner Zeh, Kilian Krause, Ziang Wang, Alicja Michalska, Jay Talbott, Maximilian
Brune, Martin Roth, Julius Werner, David Hendricks.



## Open Action Items

  * 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] Which one of the existing channels are we using as the “official” coreboot channel.
Slack, discord, irc?
  * This discussion came up at the 05-28 - coreboot Leadership Meeting where we all seemed to agree
with Werner’s suggestion to use one of our existing communities rather than creating a new one. But
we couldn’t decide which of the existing channels to use so I thought to bring it up again.
    * Max: Do we need anything official
      * Werner/martin: The issue is that people mention things in whichever they use. We’re missing
issues because communication is split across the various communication channels.
    * Set up a poll to see what people use.
      * IRC/Slack/Discord/Google chat/Mailing list/Matrix
    * Wermer: When we make the poll - please describe the issue we’re trying to solve

### [Martin] Asia Meeting Time Again
  * What we have figured out and what we are still working on.
    * Picked a time: 2:00 pm china time, 7:00 am Germany, and 5:00 am GMT
    * Keep meeting minutes in this document 
    * Create AM/PM meeting - label with gmt time zones.
    * Send out invitation
    * Set up meeting with coreboot accounts
    * Start 4 weeks from now.
    * Same day and week as the current meeting.

### [David] Vendor branches/repos
  * Did we have a doc about this? Paul was asking recently.
    * Martin will write a doc

**Information:**
  * Release was delayed due to travel. Should be done this friday (June 27)



# Next Leadership Meeting
  * July 9, 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]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.